Run a campaign

GuidesUpdated 2026-08-05
Walkthrough: building a segment, selecting a template and sending a campaign in Arino One.

A campaign in Arino One is a segmented, template-based send with a consent filter applied at the moment it actually sends, not when you built the audience. That distinction matters in practice: a contact who withdraws consent between building the segment and the scheduled send time is excluded automatically, so the delivered count can differ from the reviewed count.

Step 1 — Plan before opening the builder

Decide the goal, the channel, and roughly who the audience is before touching the campaign builder. Confirm which template category fits — marketing templates go through Meta's stricter review and are the ones consent rules apply to most strictly; utility templates (order updates, appointment reminders) have looser consent requirements but stricter content rules about staying transactional.

Step 2 — Build the segment

In the CDP (Contacts → Segments), filter on attributes, events and consent state to define the audience — for example, "market = UK" AND "no purchase in 90 days" AND "WhatsApp marketing consent = granted". See cdp-contacts-and-segments for how segments stay accurate as data changes.

Step 3 — Select an approved template

Only templates already approved for the destination channel are selectable for a live send. If the content you need doesn't exist as a template yet, submit it for approval first — see whatsapp-message-templates — and plan the campaign timeline around approval turnaround, which is usually fast once the account is verified but is not instant.

Step 4 — Send a test message

Before scheduling, send the exact template with real variable data to an internal test contact. This catches broken variables, malformed links or truncated text that template approval itself doesn't check, since approval reviews the template shape, not every possible rendered value.

Step 5 — Schedule the send

Choose a send window. The scheduler can respect each recipient's local time zone and any quiet-hours configuration, so a global audience isn't all sent at one fixed UTC time regardless of local hour.

Step 6 — Review and launch

Before launching, check three things together: the final audience count, the estimated cost of the send, and the consent filter that will apply. If any of the three looks wrong — audience larger than expected, cost higher than budgeted, filter not matching the intended purpose — fix it before launch rather than after.

Step 7 — Read results and handle opt-outs

After the send completes, review delivery rate, read rate and reply rate in the campaign report. Opt-out replies (e.g. STOP) are processed automatically: consent for that channel and purpose is withdrawn on the contact record, and they're excluded from that send's remaining batches and all future campaigns on the same channel.

Before a large send

Warn support at least three business days ahead of a large marketing send so account throughput can be raised if needed. Check your account's quality tier first — a marginal rating combined with a large send is one of the most common ways an account ends up restricted mid-campaign.

Connected vs unconnected

Every client owns and runs campaigns against their own Infobip account and quality tier, regardless of connection status.

StatusWho runs campaignsNotes
Connected ($50/month Arino Core connection)Your team, with Arino support availableArino can advise or step in if a send is throttled or an account is restricted
UnconnectedYour team, entirelyNo Arino support if a send is throttled or an account is restricted

Costs to expect

Building segments and running the campaign tooling is included with the optional $50/month Arino Core connection. Every message the campaign sends is a metered message/conversation cost billed by Meta/Infobip directly to your own account and is not included in that $50 — see billing-and-plans for current figures. Unconnected instances have no Arino billing; usage is billed directly by Infobip and Meta.

Steps at a glance

  1. Plan the campaignDefine the goal, the channel and the audience before opening the campaign builder, and confirm the template category you'll need (marketing, utility) matches the content.
  2. Build the segmentIn the CDP, filter contacts on attributes, events and consent state to define the audience the campaign will send to.
  3. Select an approved templateChoose a message template that has already been approved for the channel; marketing sends cannot use an unapproved or pending template.
  4. Send a test messageSend the exact template and content to an internal test contact or number to check rendering, variables and links before scheduling.
  5. Schedule the sendPick a send window that respects recipient time zones and any configured quiet hours.
  6. Review and launchCheck the final audience count, the estimated cost and the consent filter applied at send time, then launch.
  7. Read results and handle opt-outsReview delivery, read and reply rates after the send completes, and confirm opt-out replies are processed automatically and removed from future sends.

Frequently asked

When is the consent filter actually applied — at build time or send time?

At send (execution) time, not when the segment was built. A contact who opts out or has consent expire between building the segment and the scheduled send is excluded automatically, so the delivered audience can be smaller than the count you reviewed earlier.

Why do I need a test send if the template is already approved?

Template approval checks the wording and category with Meta; it doesn't check that your variables (name, order number, link) render correctly for real contact data. A test send to an internal number catches broken variables before thousands of contacts see them.

What happens when someone replies STOP or opts out?

The reply is processed automatically, the contact's consent for that channel/purpose is withdrawn, and they are excluded from that send and all future campaign sends to the same channel until they opt back in.

How far ahead should I plan a large send?

Warn support at least three business days ahead of a large send so account throughput can be raised if needed, and check your account's quality tier beforehand — a marginal rating combined with a large marketing send is a common cause of account restrictions.

Can I schedule a campaign across multiple time zones?

Yes, the scheduler can respect each recipient's local time zone and quiet-hours setting rather than sending everyone at one fixed clock time, which keeps a global campaign from landing in the middle of the night for some recipients.

Does a failed or undelivered message still count as a cost?

Billing follows the channel's own metering rules — WhatsApp, for example, bills on conversation open, not strictly per attempted send — so check usage-and-message-costs and billing-and-plans for how failed deliveries are treated on your channel.

Next step

Apply this to your own deployment

This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.