--- schema_version: "1" id: 6eb92a462eae177137d6bd1241b386c76d0f3d042839310444e120168e7112ef title: Segment Time Zone collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/data/264-0-0/c360_a_update_segment_time_zone.md canonical_url: https://help.salesforce.com/s/articleView?id=data.c360_a_update_segment_time_zone.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 59523bd54d0e583d7eb5ed759b562973513e33ded3db2286c64035f7bd0be90a description: Segment publish schedules are interpreted in the user's time zone. Your Data 360 org sets the publish time zones on the initial segment save and segment canvas. Segment and activation fields display the Publish Schedule Start Date and Time in the user's time zone. products: - Data 360 release: "264" --- # Segment Time Zone Segment publish schedules are interpreted in the user's time zone. Your Data 360 org sets the publish time zones on the initial segment save and segment canvas. Segment and activation fields display the Publish Schedule Start Date and Time in the user's 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_note.png) 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 | Schedule Type | Spring Forward | Fall Back | | --- | --- | --- | | Daily | Skips the run if the scheduled time is in the missing hour. | Runs once at the scheduled local time. | | Every 12 hours | Skips a run in the missing hour. The interval continues. | Runs once for a run in the repeated hour. | | Hourly or every few hours | Skips a run in the missing hour. The interval continues. | Runs once for a run in the repeated hour. | | Weekly | Keeps the same day and local time each week. Skips a run in the missing hour. | Keeps the same day and local time each week. Runs once for a run in the repeated hour. | | Monthly | Keeps the same local time each month. Skips a run in the missing hour. | Keeps the same local time each month. Runs once for a run in the repeated hour. | ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-data-data_cloud-264-0-0-production-enus/f3569962-3c9b-4f83-9d0c-b6a574e785da/images/icon_example.png) Example You schedule the segment publish start time for 1:00 PM EST (UTC-5) with a 24-hour interval. That same absolute time is 10:00 AM PST (UTC-8). If the Salesforce org time zone is later changed from EST to PST, the publish still occurs at the same absolute instant, so it appears as 10:00 AM PST, not 1:00 PM PST. For a DST example, you schedule a daily publish for 3:00 AM in a time zone that observes DST. On the spring-forward day, 3:00 AM exists as normal because the missing hour is typically 2:00 AM to 3:00 AM, so the run happens at 3:00 AM. If you had instead scheduled the publish for 2:30 AM, that run is skipped on the spring-forward day because 2:30 AM doesn't exist that day. Publishing resumes at 2:30 AM the following day. On the fall-back day, your 3:00 AM run publishes once. #### See Also - [_Salesforce Help_: Change Time Zones](https://help.salesforce.com/s/articleView?id=data.c360_a_time_zones.htm&release=264.0.0&type=5 "Data 360 uses the time zone set in Salesforce when publishing and refreshing segments and activations. The dates and times added to a segment in the segment canvas also use the Salesforce time zone. To change the time zone for Data 360, change the time zone in Salesforce.")