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. For users who have never opened the app, the timezone stays as UTC by default. You can set a specific timezone for these users through the API by sending the offset in seconds, or by including it during a CSV import.
Have a question?
Submit a requestArticles in this section
- How does the system determine a user's timezone for journeys and scheduled messages?
- How do I make a customer journey repeat or loop?
- How do session limits and segment entry rules work in a customer journey?
- How do I check for two different events in a specific timeframe using a Wait for Trigger element?
- How do I move message presets when cloning a customer journey to another app?
- How do I stop a journey when a customer starts a different campaign?
- Does the webhook node track message opens and clicks?
- Can I duplicate a Customer Journey to another project?
- How do I configure different frequency caps for Push and In-App messages within the same recurring Customer Journey?
- How are push notifications delivered to users with an undefined timezone in Customer Journey?
Comments
0 comments
Please sign in to leave a comment.