-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BD-3508 Add note about hourly Segment Extension refreshes #8137
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for tackling this @rachel-feinberg !! Left a few comments and suggestions for you.
@@ -88,11 +88,11 @@ Your segment will always begin processing after the initial save. Whenever your | |||
|
|||
### Saving a snapshot in time | |||
|
|||
If you don't need your segment to refresh on a regular schedule, you can save it without using any refresh settings, and Braze will generate your segment based on your user membership at that moment. | |||
You can specify whether you want this extension to represent a single snapshot in time, or whether you want this extension to refresh on a recurring schedule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use this section to explain what saving a snapshot in time means rather than repeating the line from the previous section? (I will also say the phrase "snapshot in time" sounds like an idiom. We might want to say something more plain-language.)
It would also be a good place to provide some strategic guidance—why would they want a snapshot vs refreshing?
For example, I could see that in industries with strict regulations (like, finance or healthcare), marketers may opt for a snapshot to ensure compliance with data usage policies and to avoid any changes that could lead to unintended targeting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should also note that this option is the default (they don't technically have to choose this)
_docs/_user_guide/engagement_tools/segments/segment_extension.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Bre Fitzgerald <82903296+bre-fitzgerald@users.noreply.github.com>
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
_docs/_user_guide/engagement_tools/segments/segment_extension.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm! Thanks @rachel-feinberg 😎
@cla-bot check |
The cla-bot has been summoned, and re-checked this pull request! |
Why are you making this change? (required)
Add note that hourly refreshes aren't available for form-based Segment Extensions
Related PRs, issues, or features (optional)
BD-3508
Feature release date (optional)
Contributor checklist
Submitting for review
If your PR meets the above requirements, select Ready for review, then add a reviewer:
braze-inc/docs-team
as the reviewer.braze-inc/docs-team
instead.Thanks for contributing! We look forward to reading your work.