The clocks changed. Did your campaign schedule change with them?

A campaign scheduled for 8:00 a.m. in New York should still start at 8:00 a.m. there after the clocks change. A job fixed at 12:00 UTC will not. The difference is easy to miss when a spreadsheet says only “Eastern.”

In 2026, daylight saving time ends in New York on November 1. At 8:00 a.m. that day, the corresponding UTC time is 13:00, rather than the 12:00 used in October. NIST’s daylight saving time guidance explains the transition and the repeated hour.

Identify which clock controls each action

A campaign can involve several independent clocks: the advertiser account, publisher, website, feed, reporting export, and automation service. Changing one does not necessarily change the others.

Record the intended local time and named zone, such as America/New_York, alongside the saved setting in each system. A named zone can describe seasonal changes; a fixed offset such as UTC−5 describes only an offset.

Use a short schedule record:

Action	Intended time	System setting to confirm
Promotion begins	8:00 a.m. New York	Campaign and destination activation
Daily report runs	After the completed reporting day	Account zone and processing delay
Overnight job executes	Once per business date	Scheduler zone and retry behavior

The correct answer depends on the business requirement. A worldwide release at one instant may intentionally use UTC. A local store promotion may intentionally follow the store’s wall clock.

Inspect the repeated hour

When clocks move back, an hour occurs twice. A log containing only “01:30” cannot distinguish the two occurrences without an offset or equivalent timestamp.

Ask the owner of any job running in that interval how the scheduler handles it. Do not assume it runs exactly once. Check the execution history and confirm that retries cannot duplicate an import or repeat a budget change.

For reports, preserve the original timestamp and zone before converting them. Removing the offset to make a spreadsheet look cleaner can erase information needed for reconciliation.

Review hourly comparisons carefully

The local day containing the autumn transition has an extra hour. A comparison of raw hourly or daily delivery needs to account for that boundary.

Do not force the repeated hour into a single row without explaining the aggregation. Nor should an unusual daily total automatically trigger a pacing correction. Check the approved delivery plan and the platform’s handling of the transition first.

The campaign pacing calculator can support the arithmetic, but the dates and budget assumptions must match the actual plan.

Verify one real execution

Read back the next scheduled action, observe it at the intended local time, and record the result. Check the destination and reporting job as well as the ad platform.

Keep the zone in the permanent handoff rather than adding a temporary seasonal note. The next person should be able to tell whether “8:00” means a local customer experience or a fixed global instant without reconstructing the original conversation.