Add note about order of ops to Braze Cohorts docs #7234
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stayseesong
previously approved these changes
Nov 18, 2024
src/connections/destinations/catalog/actions-braze-cohorts/index.md
Outdated
Show resolved
Hide resolved
…ex.md Co-authored-by: stayseesong <[email protected]>
stayseesong
approved these changes
Nov 19, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
A customer raised a docs issue asserting that the Braze Cohorts destination doesn't create a cohort in Braze automatically. I confirmed with customer success that the destination will create a cohort in Braze, if you haven't already created a cohort, and that it is optional for customers to create a cohort before they implement the destination.
Merge timing
ASAP!
Related issues (optional)
Closes #7213