> ## Documentation Index
> Fetch the complete documentation index at: https://help.getvero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Send in user's timezone

> Schedule a broadcast so each recipient receives it at the same local time, wherever they are in the world.

By default, a scheduled broadcast sends to everyone at the same moment e.g. 9:00 AM Sydney. With **Send in user's timezone** enabled, Vero instead sends at 9:00 AM in each recipient's own timezone, so someone in Sydney and someone in London both get the message at 9:00 AM local time.

## Prerequisites

1. **Track a timezone on your user profiles** – Vero reads the `ianaTimezone` or `timezone` property on each profile. The Vero JavaScript library tracks both automatically. If you send data from your backend, include one of these properties yourself. [Learn how to add or update user profiles](https://help.getvero.com/vero-2/user-profiles/how-to-add-or-update-user-profiles.md)
2. **Set your project timezone** – recipients without a timezone receive the message at the scheduled time in your project's timezone. [Learn how to set your project timezone](https://help.getvero.com/vero-2/account-settings/setting-the-timezone-on-your-account.md)

## Scheduling a broadcast in each user's timezone

1. In your broadcast's trigger settings, select **Specific Date & Time**.
2. Check **Send in user's timezone**.
3. Choose the date and time you want each recipient to receive the message, in their local time.
4. Click **Save**, then [review and launch your campaign](https://help.getvero.com/vero-2/campaigns/broadcasts/send-or-schedule-a-broadcast.md#review-and-launch).

![Send In Timezone](https://mintcdn.com/vero-c561507b/ThhWePu-xxHaHDFu/images/send-in-timezone.png?fit=max\&auto=format\&n=ThhWePu-xxHaHDFu\&q=85\&s=d288e1b0b538165cf9c69db229b1a781)

When the option is enabled, the timezone selector is replaced with a label such as **In the user's timezone or UTC+11 (Canberra, Melbourne, Sydney)**. The timezone shown is your project timezone — the fallback for recipients without one.

> [!NOTE]
>
> Vero won't let you pick a date and time that has already passed in any timezone. Because the earliest timezone (UTC+14) reaches each time of day first, you need to schedule a send far enough ahead that the chosen time hasn't arrived there yet.

## How it works

When the send starts, Vero works out each recipient's timezone and groups recipients who share the same local send time. Each group is sent when the chosen time arrives in its timezone.

Sending starts when the chosen time first arrives in the earliest timezone (UTC+14) and finishes when it arrives in the latest. For a worldwide audience, this means a single broadcast can take more than a day to finish sending.

### How Vero picks each recipient's timezone

Vero checks the following, in order, and uses the first valid value:

1. `ianaTimezone` from your campaign audience (for example, a column in a CSV or SQL audience)
2. `timezone` from your campaign audience
3. `ianaTimezone` on the user's profile
4. `timezone` on the user's profile
5. Your project timezone

Blank or invalid values are skipped.

| Property | Accepted format | Example |
| - | - | - |
| `ianaTimezone` | An IANA timezone name | `Australia/Sydney` |
| `timezone` | An IANA timezone name, or a UTC offset in hours | `America/New_York` or `-5` |

UTC offsets between -12 and +14 are rounded to the nearest supported offset. Values outside that range are ignored, and Vero moves on to the next source in the list.

> [!TIP]
>
> Use IANA timezone names where possible. They include daylight saving rules, so recipients keep receiving messages at the right local time when clocks change. A fixed UTC offset doesn't adjust for daylight saving.

### Who receives the message

Vero decides who receives the message, and in which timezone, when the send starts. Changes to your user data after that point don't affect the send. For example, a user who starts matching your segment's conditions won't receive the message, and a user whose `timezone` property changes still receives it at the time worked out from their original timezone.

### Recurring schedules

**Send in user's timezone** also works with [recurring schedules](https://help.getvero.com/vero-2/campaigns/broadcasts/recurring-schedule-trigger-automation.md). Each time the schedule runs, Vero refreshes the audience, regroups recipients by timezone, and sends to each group at the chosen local time.

### Batch sending

You can combine **Send in user's timezone** with [batch sending](https://help.getvero.com/vero-2/campaigns/broadcasts/send-or-schedule-a-broadcast.md#batch-sending). Batch settings apply within each timezone group, so each group is split into batches starting at its local send time.

## Limitations

* **Send in user's timezone** can't be used with [A/B testing](https://help.getvero.com/vero-2/campaigns/broadcasts/ab-testing-single-message.md). Enabling one disables the other.
* The option is available for scheduled broadcasts only. To send at a set local time in a Journey, use a [Delay node](https://help.getvero.com/vero-2/campaigns/journeys/delay-node.md) with a time of day.

> [!NOTE]
>
> In Vero 1.0, timezone sends only read a numeric `timezone` offset. Vero 2.0 also reads IANA timezone names from `ianaTimezone` and `timezone`, so daylight saving is handled per recipient.

## Next steps

* [Send or schedule a broadcast](https://help.getvero.com/vero-2/campaigns/broadcasts/send-or-schedule-a-broadcast.md)
* [Recurring schedules](https://help.getvero.com/vero-2/campaigns/broadcasts/recurring-schedule-trigger-automation.md)
* [Project timezone](https://help.getvero.com/vero-2/account-settings/setting-the-timezone-on-your-account.md)

## Need Help?

If you have any questions, reach out to us at [support@getvero.com](mailto:support@getvero.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.