Skip to contentSkip to main content

Campaigns

Activate the right customers with full control

For an account with a verified worker and delivery adapter, OfferAgent CampaignEngine builds a controlled campaign from account-scoped segments, explicit exclusions and a frozen audience snapshot. The team previews recipients, consent and frequency limits before approval, then schedules delivery through CommunicationHub. Every member keeps an individual status so results reflect actual eligibility, delivery and response.

A campaign needs a controlled audience

Exported lists become stale and make consent, exclusions and duplicate protection difficult to verify.

How it works

  1. 01

    Define the goal

    Choose a measurable purpose and account-scoped segment.

  2. 02

    Preview eligibility

    Inspect included customers and every exclusion reason.

  3. 03

    Approve the snapshot

    Freeze recipients and reviewed content before launch.

  4. 04

    Deliver and measure

    Send through CommunicationHub and follow member-level outcomes.

Product proof: audience before send

The campaign workspace exposes eligibility, approval and delivery at member level.

Prerequisite: Requires Campaign access, customer consent data and a configured delivery channel.

Campaign workspaceProduct flow
  1. 1Audience previewed
  2. 2Snapshot approved
  3. 3Member outcomes tracked
Open the signed-in product workspace

Sign-in and the correct plan are required. This link is not a public demo.

What this capability supports

Segment rules

Build audiences from governed customer attributes and linked activity.

Explicit exclusions

Show why a customer is suppressed before launch.

Frozen audience

Preserve who was approved even when customer data later changes.

Member-level results

Separate eligible, suppressed, queued, delivered and failed states.

Prerequisites and clear boundaries

OfferAgent states what the capability does and what still requires configuration, permission or a human decision.

  • A campaign is not sent without approval.
  • Consent and suppression are rechecked according to channel policy.
  • Delivery remains fail-closed until the worker, verified adapter, public unsubscribe origin and signing secret are configured.
  • Campaign attribution does not claim revenue without a defined evidence model.

Frequently asked questions

Can we send to every customer?

Only customers who match the segment and pass consent, suppression and frequency checks are eligible.

Can we see exclusions?

Yes. Preview lists excluded members and their reason before approval.

Can an active campaign be paused?

Yes, within the guarded lifecycle exposed by CampaignEngine.

Is a campaign the same as an automation?

No. A campaign starts from an approved audience; an automation starts from individual events.