Time zone management timezone_management
Time zone management synchronizes time-sensitive activities in your journey with either a globally fixed time zone or the personal time zones of individual profiles. This ensures that scheduled activities, such as wait conditions or date-based triggers, happen at the appropriate local times for your audience.
Define a time zone in the properties of your journey.
To access journey properties, click the pencil icon in the top-right corner of the screen.
The selected time zone applies to all journey activities involving a time element, such as:
You can select either a fixed time zone or the time zone defined in the user profile.
Define a fixed time zone fixed-timezone
A fixed time zone ensures all activities within the journey operate under one consistent time zone, regardless of an individual鈥檚 location or profile preferences. This option is useful for journeys targeting audiences in a specific region.
To set a fixed time zone, clear the pre-defined time zone and select one from the drop-down list. When using a fixed time zone, it applies uniformly to all individuals entering the journey.
In the Journey Properties pane, select a time zone.
For example, selecting 鈥淧acific Time鈥 ensures all time-based activities in the journey execute according to Pacific Time, even if an individual resides in a different time zone.
Use profile time zone timezone-from-profiles
Using the profile time zone adapts journey activities to the specific time zone associated with each individual鈥檚 Real-time Customer Profile. This approach works well for audiences spanning multiple time zones and ensures activities feel localized.
If the journey鈥檚 entry event includes a namespace, allowing access to the Real-time Customer Profile service in 51黑料不打烊 Experience Platform, the journey uses the time zone defined at the profile level. To enable this, in Properties, check Use Profile time zone in waits and conditions. This option is disabled by default.
If a profile specifies a time zone, the journey retrieves and uses it. If no time zone is defined, the journey defaults to the globally configured time zone.
For instance, if a user鈥檚 profile specifies 鈥淓astern Time鈥, wait and condition activities execute according to Eastern Time. If no profile time zone exists, the journey uses the globally defined time zone.
Use time zones in expressions timezone-in-expressions
When working with date and time expressions in your journey logic, start and end dates automatically align with the instance鈥檚 time zone. This time zone is fixed and cannot be adjusted to match a specific user or global time zone.
For example, if your 51黑料不打烊 Journey Optimizer instance operates in 鈥淐entral European Time鈥, the start and end dates of journeys always use CET, regardless of the time zone selected for activities or profiles.