Skip to content
Optima docs
ConsoleCampaigns

Consent purpose

Choose which consent purpose a campaign checks before every send, including per-channel purposes and the explicit opt-out.

A consent purpose is the reason a campaign contacts someone, such as marketing. Before every send, the campaign checks that the customer has granted that purpose. If they have not, the message is not sent. You choose the purpose in the Delivery block of the campaign page, and an offer can carry its own purpose that overrides the campaign's. Purposes and consent records themselves are explained in Consent and purposes.

Who uses it

Campaign managers choose the purpose; privacy officers decide which purposes exist and what lawful basis each relies on. Choosing needs campaign_editor, or another role your administrator has given access to this area — see Licences and roles.

Fields

Consent purpose is one choice in the Delivery form. It is also on each offer.

ChoiceMeaning
NoneNo purpose is set. A batch campaign cannot be activated like this.
No consent gate (explicit opt-out)Send without a consent check. Use it only for messages that do not need consent, such as a required service message. It is a deliberate choice, and it appears in the change history like any other edit.
A named purposeEvery send checks that the profile granted this purpose. The list shows active purposes from your consent catalogue.
A channel family under Per-channelA purpose written with a channel placeholder, such as marketing_{channel}. Each send checks the purpose of the channel it actually uses.

Batch campaigns (one-off and recurring) need a purpose, or the explicit opt-out, before they can be activated. Journey-based and inbound-offer campaigns can carry one too, and offers carry their own.

How the check works

The check is made live for each send, not once when you activate, so a customer who withdraws consent is skipped from that moment. How a missing consent record is read depends on the purpose's lawful basis; see Consent and purposes.

Channel placeholders. If your purposes are channel-specific, for example marketing_email, marketing_sms and marketing_push, the form offers the family marketing_{channel}. A campaign on the Auto (best channel) channel checks the purpose of the channel the message really goes on. For an inbound-offer decision, an offer is decided if any channel is permitted. Activation checks that the purposes for the channels the campaign can actually send on exist in the catalogue.

Offers. An offer's own purpose overrides the campaign's. Activation checks offers too.

Examples

One purpose for everything. Choose marketing. Every send, on every channel, requires the customer to have granted marketing.

Per-channel purposes. Create marketing_email and marketing_sms (the New purpose family action under Settings → Workspace → Privacy creates them together), then choose marketing_{channel}. An email send checks marketing_email.

A service message. Choose No consent gate (explicit opt-out) for a campaign that tells customers about a change to their account. The choice is visible in the campaign's change history.

Common problems

  • Activation says the campaign needs a consent purpose. Batch campaigns must choose a purpose or the explicit opt-out.
  • Activation says a purpose does not exist in the catalogue. The name is misspelled, or it was removed. Create the purpose, fix the name, or choose the opt-out.
  • A channel family reports missing purposes. One of the expansions, such as marketing_sms, is not in the catalogue. Create it.
  • Fewer people receive the campaign than the audience size. The consent step removed those who have not granted the purpose. Run Pre-flight to see how many.

On this page