The platform pulls timezone data from the system settings of the device. This happens when a user opens the app. The system does not use GPS data or IP addresses to find this information. If a user travels to a different country, their timezone updates only if their device settings change and they open the app in the new location.
You can also set the timezone yourself through the API by sending the UTC offset in seconds: the timezone field in /registerDevice, or tz_offset in the user-centric API (for example 3600 for UTC+1).
If a subscriber has no timezone at all, the message is not silently sent in UTC. When a Customer Journey entry or a scheduled push is set to Subscriber's device timezone, those users are delivered according to the campaign's Fallback timezone — click Change fallback next to the timezone selector to set it. Whatever you pick there is the time these users receive the message, regardless of where they actually are.
Comments
0 comments
Please sign in to leave a comment.