Segment Time Zone

The Salesforce org time zone still applies to other segmentation behavior, such as date-based operators like Last 'n' Days.

Updates made to your Salesforce org's time zone aren't reflected in existing segments.

How Time Zone Changes Apply to Segments

Newly created segments follow the updated time zone. To update the time zone of an existing segment, resave the segment.

Note The save action is triggered only when specific payload fields change. A change to any one of these fields triggers a segment update request: Name, Description, Include Criteria, Exclude Criteria, Publish Schedule Start Date and Time, Publish Schedule Interval, Publish Schedule End Date, Publish Schedule Info, or Lookback Period. A change to the time zone alone doesn't trigger an update.

How Daylight Saving Time Affects Publish Schedules

Scheduled segment publishes preserve the local wall-clock time that you chose, even when the clocks change for daylight saving time (DST). Your segment continues to publish at the same local time before, during, and after the clock change. You don't need to adjust your schedule when the clocks change. This behavior applies to any time zone that observes DST, including US, European, and Southern Hemisphere zones. If your time zone doesn't observe DST, your segment runs at the same time every day.

Publish Behavior When Clocks Spring Forward

On the spring-forward day, one hour is skipped and doesn't exist in local time. If a scheduled run lands inside that missing hour, that single run is skipped and publishing resumes at the next scheduled time.

• Daily schedules: If your chosen time falls in the missing hour, that day's run is skipped and the next day's run occurs at your chosen time.
• Hourly or every-few-hours schedules: Only the run in the missing hour is skipped. Other runs that day aren't affected.
• Weekly and monthly schedules: A run that lands in the missing hour is skipped. The next scheduled run occurs in the following week or month at the same local time.

Publish Behavior When Clocks Fall Back

On the fall-back day, one hour occurs twice in local time. To prevent duplicate publishes, a run that lands in the repeated hour runs only once.

• Hourly or every-few-hours schedules: The run in the repeated hour publishes once, not twice. Publishing continues normally afterward.
• Weekly and monthly schedules: A run that lands in the repeated hour publishes once.

Daylight Saving Time Behavior by Schedule Type