Skip to content
WeZend

Campaigns & content

Local-time sending and contact time zones

Send at 10:00 where each person is. How a contact's time zone is found, and how campaigns and journeys use it.

Local-time sending delivers a message at a time of day that is right where each person is, for example "10:00 their time".

A contact's time zone

WeZend uses, in this order:

  1. the contact's own timezone (an IANA name such as Europe/Copenhagen),
  2. the country of their phone number, only for countries with a single zone (for example +45, +46, +358, +49). Countries with several zones, such as +1, +61, +55, +7 or +52, are not guessed,
  3. the fallback you name: the campaign's own, otherwise Europe/Copenhagen.

Set it with POST /v1/contacts, PATCH /v1/contacts/:id or POST /v1/contacts/upsert (an invalid zone is a 400 and nothing is written; null clears it; an upsert that sends none leaves it alone), in the contact forms, with an optional timezone column in a CSV import (a bad name rejects that row with invalid_timezone), or filter on it with the Time zone field in segments.

Tracking events from the web tracker and the SDKs carry the device's zone. The server uses it only to fill an empty zone, never to replace one you saved.

Campaigns

Set local_time_send: true and local_send_time: "10:00", with an optional local_send_fallback_tz. Each recipient is scheduled for the next 10:00 in their zone after the campaign starts, which is at most a day and a bit ahead.

  • It cannot be combined with smart send time (400 local_time_conflict).
  • A campaign with a backup channel does not send the backup in this mode.
  • Quiet hours do not defer a locally scheduled message a second time.
  • To aim at a date, schedule the campaign itself (scheduled_at) for the day before.

Journeys

  • A wait_until step with local: true waits for the contact's own time of day (the step's tz is the fallback).
  • settings.quiet_hours.local: true makes quiet hours the contact's own, so 21:00 to 08:00 means night where they are.

See also smart send time.

One platform. Every customer interaction.

Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.

No credit card required · EU data residency · 99.99% uptime SLA