Campaigns

Campaigns

A campaign sends one or more messages to an audience over Email, SMS, or WhatsApp. Each campaign has an ordered set of steps — a step is a channel plus a template, sent at a particular time. ZingaConnect offers three campaign types, distinguished by how the timing of their steps is decided.

The three campaign types

Drip campaigns

Each step fires a set offset after the contact was enrolled. Offsets can be expressed in minutes, hours, days, weeks, months, or years (month and year offsets are calendar-correct). Two contacts enrolled on different days progress through the same relative schedule from their own start point.

Calendar campaigns

Steps are tied to absolute dates. When you build a calendar campaign you can pick occasions from a dated calendar — Zingasuite provides ready-made occasion calendars, and you can create your own. Selecting an occasion copies its date onto the step as a snapshot, so later edits to the calendar do not silently change a campaign you have already built. A dated step whose moment has already passed for a late-joining contact is skipped rather than back-fired, so a stale occasion never sends.

Broadcast campaigns

A broadcast is a single message to the audience, sent immediately or scheduled for one date. It is the quickest way to send a one-off message to a list.

Enrolling contacts

A campaign targets one or more lists; its audience is the de-duplicated union of them (a contact in two of the campaign's lists is enrolled only once). There are two enrolment modes:

• Static enrolment enrols the current audience once, when the campaign is activated.
• Continuous enrolment keeps enrolling new members as they join the targeted list. Paired with a dynamic list, this turns a campaign into an always-on flow that picks up new contacts as they qualify.

A contact is never enrolled in the same campaign twice.

Timezone-aware preferred send time

You can set a preferred local time of day for a campaign (and override it per step) — for example "8 PM". ZingaConnect delivers to each contact at that wall-clock time in the contact's own timezone. 8 PM for a contact in India and 8 PM for a contact in the United States resolve to different actual moments, so everyone receives the message at a sensible local hour.

The timezone ZingaConnect uses for a contact is resolved in order:

1. The contact's own timezone, if known.
2. The campaign's default timezone.
3. Your account's timezone.
4. UTC as a final fallback.

If a preferred time has already passed on the target day (for a drip step), delivery rolls to the next occurrence.

How sending works

Once you activate a campaign, ZingaConnect enrols the audience and schedules each contact's steps at their due moments. From then on it works automatically and continuously:

• Due steps are sent on a rolling basis; there is nothing to trigger by hand.
• Consent and suppression are checked at the moment of sending, per recipient. A contact who opted out after being enrolled is skipped, not sent — enrolment does not lock in consent.
• Sends respect the rate limit and daily quota on the channel you are using (see Channels).
• If a contact cannot be reached on a step's channel (no address, no consent, or suppressed), that step is skipped for them, and the rest of their sequence continues.
• Each contact's enrolment completes once all their steps have fired.

You can pause and resume a campaign, and re-run steps that were skipped (for example after granting consent) — when re-running a drip, the original spacing between steps is preserved rather than firing everything at once.

Reporting

Every campaign has an engagement report showing how far each channel got — targeted, sent, delivered, opened or read, clicked, plus skipped, failed, and bounced. See Message Tracking & Reports.