Skip to content
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

Merged
merged 5 commits into from
Sep 25, 2024

Conversation

rachel-feinberg
Copy link
Contributor

@rachel-feinberg rachel-feinberg commented Sep 23, 2024

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)

  • N/A

Contributor checklist

  • I confirm that my PR meets the following:
    • I signed the Contribution License Agreement (CLA).
    • My style and voice follows the Braze Style Guide.
    • My content contains correct spelling and grammar.
    • All links are working correctly.
    • If I renamed or moved a file or directory, I set up URL redirects for each file.
    • If I updated or replaced an image, I did not remove the original image file from the repository. (For more information, see Updating an image).
    • If my PR is related to a paid SKU, third party, SMS, AI, or privacy, I have received written approval from Braze Legal.

Submitting for review

If your PR meets the above requirements, select Ready for review, then add a reviewer:

  • Non-Braze contributors: Add braze-inc/docs-team as the reviewer.
  • Braze employees: Have any relevant subject matter experts (like engineers or product managers) review your work first, then add the tech writer assigned to your specific vertical. If you're not sure which tech writer to add, you can add braze-inc/docs-team instead.

Thanks for contributing! We look forward to reading your work.

Copy link
Collaborator

@bre-fitzgerald bre-fitzgerald left a 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.
Copy link
Collaborator

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.

Copy link
Collaborator

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)

Co-authored-by: Bre Fitzgerald <82903296+bre-fitzgerald@users.noreply.github.com>
Copy link

vercel bot commented Sep 25, 2024

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

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
braze-docs-ko ⬜️ Ignored (Inspect) Visit Preview Sep 25, 2024 6:34pm

Copy link
Collaborator

@bre-fitzgerald bre-fitzgerald left a 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 😎

@bre-fitzgerald
Copy link
Collaborator

@cla-bot check

Copy link

cla-bot bot commented Sep 25, 2024

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

@bre-fitzgerald bre-fitzgerald merged commit e99865d into develop Sep 25, 2024
4 of 5 checks passed
@bre-fitzgerald bre-fitzgerald deleted the bd-3508 branch September 25, 2024 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants