Offers API

The Offers API does not currently follow the standardized timezone model. Existing timezone behaviour remains unchanged. Standardization is planned as part of an ongoing revamp initiative.

v1 and v1.1 APIs

v1 and v1.1 APIs retain legacy timezone behaviour. Timezone standardization is not applied to these API versions.

These API versions are not being deprecated. They will adopt the standardized model in a future release.

Multi-timezone promotion applicability

Currently, promotions are scheduled and evaluated based on the organization's central timezone. For example, if a promotion expires at midnight Central Time, the window closes for all users at that moment, even if it is still the previous day in their local timezone. Full support for local timezone evaluation of promotion applicability is not yet implemented and is part of the planned evolution of the standardization initiative.

DST fall-back handling

The system does not handle the repeated 01:00–01:59 hour during a DST fall-back. This is a deliberate trade-off to avoid large-scale changes to legacy servers and data types.

Offset preservation scope

Offset preservation is currently available for transactions and behavioural events. It is not yet extended to all API types. Support for offset preservation in other areas (such as customer-level data and rewards) will be added in future releases.

Insights: no platform-wide timezone standardization

The Insights module is not included in the current platform-wide timezone standardization rollout. See Timezone Handling in Databricks Tables for details on how Insights handles timestamps independently.