OneTrace.pro Help center

Campaigns

A campaign is a bulk send to segment members at a set time, either one-off or recurring. For example, a sale announcement for "VIP customers" or a weekly digest. Journeys react to an individual customer's behavior, while a campaign goes out to the whole audience at once.

The section is in the menu under Engagement → Campaigns. All roles can view campaigns and reports. Manager and above can create, launch, and stop them. You can see all campaigns on one grid with journeys and holidays in the marketing calendar.

Create a campaign

  1. Enter a name in the Campaign name field and click Create. The campaign opens on the Settings tab.

  2. Audience. Choose Recipient segments and, if needed, Exclude segments, up to 10 in each field. The campaign goes to everyone who is in at least one selected segment and not in any excluded one. Below the fields you'll see an estimate: Audience now: N. If the campaign channel is email, an Email address check block appears below: how many audience addresses are already on the suppression list and how many the pre-send check will filter out, by reason and with the offending domains. The check runs in the background for a few seconds; the Check again button refreshes the report.

  3. Channel and content. Choose a Channel (integration) and a Message template. The list only shows templates for that channel.

  4. When to send. Choose one option:

    • Now;
    • At a set time: a date and time;
    • Recurring: Daily, Weekly (choose the days of the week), or Monthly (a day of the month from 1 to 28). Set the time and the start and end dates.
  5. Delivery and goal. Rate, messages per minute limits the flow to protect your sender reputation and your website from traffic spikes. If you leave the field empty, there's no limit. Campaign goal (conversion) is an event, such as order_completed, and the window after sending in which it counts.

    Below the rate is the Sending limits block: what is holding the campaign back right now and why (integration speed, campaign speed, domain warm-up, trial daily limit, monthly plan quota) and the estimated sending time for the current audience. With a campaign rate set, emails go out evenly across each minute rather than in a burst at its start.

  6. Click Save, then Test to check the message. After that, click Launch or Schedule.

Times are in the project's time zone. If you turn on In each recipient's local time, each recipient gets the message at the set time in their own time zone. The time zone comes from the timezone trait; for profiles without it, from the project settings. Such a campaign starts with the easternmost time zone and can take up to a day.

At each recipient’s best time sends to each recipient within a day of launch, at their best hour based on the best_send_hour trait. If that hour is already under way, the message goes out right away; if it has already passed today, the message goes out the next day. Recipients without their own hour get the message at the project's best hour, or right away if there isn't one yet. With an A/B test, the remaining recipients also get the winner, each at their own hour. This setting is available on plans with predictions and can't be combined with local time.

Campaign settings with two variants and an A/B test

Variants and A/B tests

The Add variant button adds a variant with its own template and share, up to 5 variants (A–E). Variant shares must add up to 100%.

  • If the A/B test is off, the audience is simply split between the variants by share.
  • If you turn on A/B test with a winner, only the Test share of the audience (5–50%) gets the message first. It's split between the variants. After the set Wait, the variant with the best rate for the selected metric (Opens, Clicks, or Campaign goal) goes to all remaining recipients.

A winner is always chosen, even if the difference isn't proven: the remaining recipients need to get something. The report shows whether the result was significant. To use the Campaign goal metric, set a goal first.

Automatic variant selection

In a recurring campaign, the switch is called A/B test of variants, with a Mode next to it. Test and winner works as described above, in every run. Automatic learns from past runs: there is no test share and no wait, every run goes to the whole audience at once, and the variant shares are calculated from the last 10 runs of this campaign by the Best by metric: Opens, Clicks, or Campaign goal.

Until a variant has 100 sent messages, the shares are equal. After that, the best variant gets more, and the others get at least 10%, so the estimate can correct itself. Variant percentages aren't set in this mode. A run's shares are calculated once, when it starts, and don't change afterwards. The mode is only available for a recurring campaign and on a plan with the Automatic variant selection feature, available from the Growth plan.

Campaign variants in Automatic mode

AI variants

The AI variants button next to "Add variant" creates email variants for an A/B test. It's available for an email campaign when a template is chosen for variant A and there are fewer than five variants. In the window, choose How many variants to add (1–3). Turn on Also change the heading and intro if the email is built in the builder and not only the subject and preheader should change. Click Add variants.

The campaign is saved first. Then AI writes the variants on all language versions of the template, each with its own approach: curiosity, benefit, urgency (only if the email has a deadline), or a personal touch. Each variant is saved as a separate template "… — variant B (AI)" and added to the campaign as the next letter. The variant shares become equal and the A/B test turns on. You can open the variant templates, edit them, and check them before launch. It's charged to the project balance by usage, the same as AI in the email editor.

The "Email variants with AI" window

What happens at launch

  • The recipient list is fixed at launch. Anyone who joins the segment later only gets the message on the next run of a recurring campaign.
  • Before each message is sent, subscription, frequency limits, quiet hours, and plan quota are checked (messaging rules). If a check fails, the message goes to Skipped.
  • Changes made after the start don't affect a run in progress.
  • If the project has a control group turned on, its profiles stay in the audience, but the message isn't sent to them. To send the campaign to them too, for example about changed terms, turn on Send to the control group too in the Audience block.
Status What you can do
Draft Change settings, delete, launch
Scheduled Edit (the launch time is recalculated), pause, cancel
Sending Pause or cancel
Paused Edit, resume, cancel, delete
Sent View the report, delete
Cancelled View the report, delete

After each run, a recurring campaign returns to the Scheduled status with the next run time. Cancel campaign cancels all messages not yet sent and stops recurring runs. You can't delete a scheduled or sending campaign: cancel it first. If a run fails, for example because the integration was deleted, the campaign is paused and the error appears in the report.

An email campaign is also paused automatically when mailbox providers return too many emails or recipients complain about spam (automatic pause). The reason appears above the tabs: the bounce and complaint rates and the limits. Bounced addresses are already on the suppression list. After Resume, the rates are counted again from new emails.

Test send

The Test button opens the Send a test of the campaign dialog. Choose a profile whose data will be filled into the message and, optionally, your own address. You'll get one message per variant. Subscription, frequency, and quiet hours aren't checked, and the test doesn't appear in the report.

Pre-launch check

Launch and Schedule first save the campaign and check that it's ready. If everything is fine, the campaign is launched or scheduled right away. If there are issues, the "Pre-launch check" dialog opens with a list:

  • Blocks the launch: the launch won't go through until you fix it (no enabled integration, variant template, segment, or launch date);
  • Worth checking: you can launch, but some messages won't arrive or won't go out as intended (a marketing email has no unsubscribe link, a template failed to render, there's no version in one of the project languages, the sending domain isn't verified, the integration has an error, the deliverability check rated an email Poor, the segment is empty or contains almost all profiles of the project, the goal event hasn't arrived for a long time);
  • Notes: for example, no goal is set, so conversions won't be counted.

With warnings, you can launch the campaign with the button in the dialog; the decision is yours. The assistant launches a campaign only if the check has neither errors nor warnings. The same check is available in the API (GET /api/v1/campaigns/{id}/readiness).

Checking emails before launch

If a campaign is sent by email, the Channel and content block has an Email deliverability section. The Check emails button checks the email of each variant through the selected integration: the sender, the content, and the spam filter score, like the check in a template. You don't need to save the campaign for this. For each variant you can see the rating and the main notes, and the Details in the template link opens the full report.

Checking the emails of campaign variants

When you launch or schedule the campaign, the emails are checked again if the integration or templates have changed since the last check. If any variant is rated Poor, the "The email may land in spam" dialog appears. You can still launch the campaign, but it is better to fix the template first.

Approval

If Launch campaigns and journeys only after approval is turned on in the messaging rules, a campaign can be launched or scheduled only once it has been approved. This suits teams and agencies where one person writes the campaign and another reviews it and allows the launch.

  1. The author builds the campaign and clicks Submit for review in the campaign header. You can add a comment for the reviewer. Unsaved changes are saved.
  2. Members with the Approve campaigns permission get an email with a link to the campaign. By default, Owner and Administrator have this permission, and in custom roles you can grant it to anyone.
  3. The reviewer clicks Approve or Return. A campaign can only be returned with a comment saying what to fix. The author gets an email with the decision and the comment.
  4. Once approved, the campaign can be launched or scheduled.

Campaign on review: status and approval buttons

The status is shown next to the buttons: "On review", "Approved", "Returned", or "Changed after approval". Hover over "Approved" to see who approved the campaign and when. The clock button opens Approval history: who submitted the campaign for review, approved it, or returned it, when, and with what comment.

Campaign approval history

An approval applies to the campaign as it was when reviewed. Any change after that (to the name, audience, channel, variants, A/B test, schedule, speed, or goal, including moving it in the calendar) sends the campaign back to review, and approvers get an email. A scheduled campaign also goes back to draft. If the template of one of the variants was changed after approval, this is detected at launch: the campaign goes back to review, and the launch doesn't go through. Until the campaign is approved, the pre-launch check shows this under Blocks the launch.

Campaigns scheduled before approval was turned on keep going out on schedule until they are changed. In the API, submit a campaign for review with POST /api/v1/campaigns/{id}/approval/request (the key needs the campaigns.write permission), and decide with …/approval/approve and …/approval/return (the campaigns.approve permission). The status is in the approval_status field.

Report

On the Report tab, choose a run from the Run … list (the last 10 are shown) and refresh the data with the refresh button.

  • Cards: Audience, Queued, Sent, Delivered, Opened, Clicked, Unsubscribed, Converted. Rates are calculated from sent messages.
  • A table by variant. The A/B test winner is marked with a Winner label.
  • The table by language, if messages went out in several language versions of templates.
  • The Significance by … block shows whether the variants differ statistically, with the rate, a 95% interval, and the probability of being the best. It also shows whether the difference was significant when the winner was chosen.
  • For a run with automatic selection, above the table you'll see how many past runs the shares were calculated from. The table has a Share column, and below it is the Variant shares by run table.
  • The Control group block, if the campaign has a goal and part of the audience was in the control group: goal conversion of the recipients and of the group that didn't get the campaign, and whether the difference is significant.

Campaign run report

Campaign report with automatic selection: run shares and shares by run

Skipped messages are recipients without a subscription, those filtered out by a frequency limit, or those without an address. Overall statistics for all channels are in the channel report.

History

The History tab lists everything that happened to the campaign, newest first: who created, changed, scheduled, paused, resumed or cancelled it, and when each run started and finished. Automatic actions are signed «System»: an automatic pause shows the bounce and complaint rates and the limits, a pause after an approved template was changed shows the template name, and a failed run shows the error. Actions through the API show the key name. Several saves in a row by the same member are combined into one line.