Tellius Partnership Docs

[jdTellius]

Pull Request/Issue Resolution

Description of Change:

I'm changing..... (could be a link, a new image, a new section, etc.)... because...

Closes #ISSUE_NUMBER_HERE

Is this change associated with a Braze feature/product release?

• Yes (Insert Feature Release Date Here)
• No

---

✔️ Pull Request Checklist

• Check that all links work.
• Ensure you have completed our Contributors License Agreement.
• Tag @timothy-kim and @KellieHawks as a reviewer when your work is done and ready to be reviewed for merge. Are you an internal product manager? Reference the internal reviewing chart to tag the appropriate reviewer.
• Tag others as reviewers as necessary.
• If you have modified any links, be sure to add redirects to assets > js > broken_redirect_list.js

⭐ Helpful Wiki Shortcuts

• Writing Style Guide
• Image Style Guide
• Styling Test Page

❗ ATTN: For PR Reviewers

• Read our Reviewing a PR page for more on our reviewing suggestions.
• Read our Previewing Documentation page to see how to check the deployment.
  • Preview all changes in the linked Vercel environment by clicking the preview link in the vercel-bot comment in your PR.

❗ ATTN: Internal Reviewing Chart

Work at Braze and not sure who to tag for review?
Before tagging @timothy-kim or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.

Reviewer	Product Vertical
@timothy-kim	Data Infrastructure Platform Infrastructure Quality Infrastructure
@KellieHawks	Internal Tools Product Partnerships SDKs SMS
@bre-fitzgerald	Channels FIX Intelligence Reporting SMB
@lydia-xie	Email (Composition and Infrastructure) Ingestion Messaging

[vercel]

@jdTellius is attempting to deploy a commit to the Braze Team on Vercel.

A member of the Team first needs to authorize it.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[jdTellius]

@KellieHawks @timothy-kim submitting partner docs for Braze-Tellius partnership. Thank you for reviewing and getting our partnership started!

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[cla-bot]

We require contributors to sign our Contributor License Agreement, and we don't have you on file. In order for us to review and merge your code, please fill out the information here. To re-call the cla-bot, comment @cla-bot check.

[KellieHawks]

@jdTellius When you get a chance, can you sign our contributor's license agreement? This allows us to use your contributions in the Braze docs.

[jdTellius]

@KellieHawks I did complete the agreement and submitted. Let me know if you are not seeing the same on your end and I can complete it again. I received two emails asking me to complete it and just followed the link from the first email

[KellieHawks]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
braze-docs-en	✅ Ready (Inspect)	Visit Preview	Nov 17, 2022 at 3:24PM (UTC)

1 Ignored Deployment

Name	Status	Preview	Updated
braze-docs-fr	⬜️ Ignored (Inspect)		Nov 17, 2022 at 3:24PM (UTC)