From 5f513f0e0eb5a41dcac677c0e9ec9ee160cf0d47 Mon Sep 17 00:00:00 2001 From: wilwong-twilio <109997887+wilwong-twilio@users.noreply.github.com> Date: Fri, 5 Sep 2025 16:32:32 -0700 Subject: [PATCH 1/3] Update linked-audiences.md --- src/engage/audiences/linked-audiences.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/engage/audiences/linked-audiences.md b/src/engage/audiences/linked-audiences.md index ded99e8ce7..c3569f4b9f 100644 --- a/src/engage/audiences/linked-audiences.md +++ b/src/engage/audiences/linked-audiences.md @@ -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. To enable your audience, select the **Enabled** toggle, then select **Enable audience**. @@ -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. +When configuring an interval run schedule, the system uses a cron-based mechanism anchored to GMT, meaning the next run time aligns with the nearest GMT-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 GMT schedules the next run for 5 PM PST the same day, as it aligns with 12 AM GMT; however, if set after 5 PM PST, like 6 PM PST, the next run will be at 5 PM PST the following day. + ## Step 5: Monitor your activation With your Linked Audience activated, follow these steps to monitor your activation: From 614ff2f63a05d8f47f727ef2534b6aa38b60f74e Mon Sep 17 00:00:00 2001 From: wilwong-twilio <109997887+wilwong-twilio@users.noreply.github.com> Date: Fri, 5 Sep 2025 17:57:26 -0700 Subject: [PATCH 2/3] Update linked-audiences.md --- src/engage/audiences/linked-audiences.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/engage/audiences/linked-audiences.md b/src/engage/audiences/linked-audiences.md index c3569f4b9f..171d713363 100644 --- a/src/engage/audiences/linked-audiences.md +++ b/src/engage/audiences/linked-audiences.md @@ -241,9 +241,9 @@ 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. -When configuring an interval run schedule, the system uses a cron-based mechanism anchored to GMT, meaning the next run time aligns with the nearest GMT-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 GMT schedules the next run for 5 PM PST the same day, as it aligns with 12 AM GMT; however, if set after 5 PM PST, like 6 PM PST, the next run will be at 5 PM PST the following day. +> 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. ## Step 5: Monitor your activation From 38a06062ea213132f89764c9ffcc218b06b5265d Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 25 Sep 2025 13:51:21 -0700 Subject: [PATCH 3/3] Apply suggestions from code review --- src/engage/audiences/linked-audiences.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/engage/audiences/linked-audiences.md b/src/engage/audiences/linked-audiences.md index 171d713363..fc661b92a4 100644 --- a/src/engage/audiences/linked-audiences.md +++ b/src/engage/audiences/linked-audiences.md @@ -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 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. To enable your audience, select the **Enabled** toggle, then select **Enable audience**. @@ -243,7 +243,7 @@ There may be up to a 5 minute delay from the configured start time for audiences > 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. +> 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. ## Step 5: Monitor your activation