Skip to content
CountdownFlow Help Sign in

Fixed dates, timezones and daylight-saving changes

Set one reliable deadline for everyone without confusing local time and UTC.

3 min read

Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.

Set the timezone before the date

A Fixed date campaign ends at one absolute moment. The date/time field is interpreted in the campaign timezone, then stored as an equivalent UTC instant. Choose a named region such as America/Toronto when your deadline follows that location’s clock. Do not assume that your browser location or a viewer’s location sets the campaign timezone.

Example: a Toronto deadline of 18:00 is not an 18:00 deadline in every customer’s city. Customers see the remaining time toward the same moment. Mention the timezone in the offer copy when a specific local closing time matters.

  1. 1Open the campaign timing settings and select Fixed date.
  2. 2Choose the campaign timezone, then enter the end date and local time.
  3. 3If there is a start date, ensure it precedes the deadline. Save and confirm the formatted deadline on the campaign screen.
  4. 4Preview the waiting and expired states and publish only after the deadline is correct.
Fixed-date campaign editor showing timing configuration
In the application Choose the timer type and timezone, then set the deadline and expiration action. Save these settings separately from the visual design. View full-size screenshot (opens in a new tab)

Optional start dates

A future start date lets an offer wait before its active period. Test what the waiting state displays and where a click goes before the start. Do not interpret a waiting timer as evidence that your offer is already open. If you leave the start blank, the campaign is not given that future-start condition.

Daylight-saving time

Some locations skip a local hour when daylight saving begins. A time that does not exist is rejected rather than silently shifted. Choose a valid local time and recheck the displayed deadline.

When a local hour repeats in autumn, make your intended instant unambiguous and verify the saved result. For API timestamps, use an explicit timezone offset or Z rather than a timezone-free date. UTC is useful when your team needs an unambiguous technical reference.

Changing a deadline after launch

Updating the end date can affect new requests to the existing campaign URLs. Cached email images may still show an earlier response. Re-test the website, smart link and an uncached image request; do not announce a changed deadline based only on an editor preview.

Related articles