Updates to audience run behavior #7901
Open
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
requested changes
Sep 9, 2025
| @@ -218,7 +218,7 @@ The Event content drop-down shows you a preview of what the data sent to your de | |||
|
|
|||
| ## Step 4: Enable your Linked Audience | |||
|
|
|||
| After building your Linked Audience, choose **Save and Enable**. You'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically disables your audience so that it doesn't start computing until you're ready. A run is when Segment runs the audience conditions on your data warehouse and sends events downstream. | |||
| After enabling your activation, you'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically creates your audience in a disabled state so that it doesn't start running until you're ready. A run is when Segment runs the audience conditions on your data warehouse and sends events downstream. Segment will automatially trigger a run when you enable your audience. The next run time will be dictated by your configured run schedule. | |||
There was a problem hiding this comment.
Suggested change
| After enabling your activation, you'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically creates your audience in a disabled state so that it doesn't start running until you're ready. A run is when Segment runs the audience conditions on your data warehouse and sends events downstream. Segment will automatially trigger a run when you enable your audience. The next run time will be dictated by your configured run schedule. | |
| After turning on your activation, you'll be redirected to the Audience Overview page, where you can view the audience you created. Segment automatically creates your audience in a disabled state so that it doesn't start running until you're ready. A run is when Segment runs the audience conditions on your data warehouse and sends events downstream. Segment automatically triggers a run when you enable your audience. The next run time will be dictated by your configured run schedule. |
There was a problem hiding this comment.
@wilwong-twilio shouldn't it read, "After turning on your Linked Audience" instead of activation?
| @@ -241,6 +241,10 @@ You can also click **Run Now** on the Audience Overview page at any time (even i | |||
|
|
|||
| There may be up to a 5 minute delay from the configured start time for audiences that are configured with the **Interval** and **Day and time** run schedules. For example, if you configured an audience with the **Day and time** compute schedule to run on Mondays at 8am, it can compute as late as Monday at 8:05am. This is to help us better manage our system load. | |||
|
|
|||
| > info "" | |||
| > When configuring an interval run schedule, the system uses a cron-based mechanism anchored to UTC, meaning the next run time aligns with the nearest UTC-based interval cycle, which may shift the schedule relative to your local time zone. | |||
| > When you set a 24-hour interval run schedule at, for example, 4 PM PST, the cron-based system using UTC schedules the next run for 5 PM PST the same day, as it aligns with 12 AM UTC; however, if set after 5 PM PST, like 6 PM PST, the next run will be at 5 PM PST the following day. | |||
There was a problem hiding this comment.
Suggested change
| > When you set a 24-hour interval run schedule at, for example, 4 PM PST, the cron-based system using UTC schedules the next run for 5 PM PST the same day, as it aligns with 12 AM UTC; however, if set after 5 PM PST, like 6 PM PST, the next run will be at 5 PM PST the following day. | |
| > When you set a 24-hour interval run schedule at, for example, 4 PM PST, the cron-based system using UTC schedules the next run for 5 PM PST the same day, as it aligns with 12 AM UTC; however, if set after 5 PM PST, the next run will be at 5 PM PST the following day. |
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
Updated content to be more detailed about how audience runs when it is enabled, and how the audience interval schedule is based on UTC time.
Merge timing
After reviewed and approved.
Related issues (optional)