Customer Campaigns binds an audience, channel, message template, execution contract, risk policy, and optional reward. Creating a campaign does not deliver anything by itself. Verify segment membership, consent, provider execution, lifecycle status, and delivery results separately.
Create the campaign record
Open Admin → Customers & CRM → Campaigns. Enter Campaign name, then choose Campaign channel, Campaign type, Campaign segment, Campaign message template, Execution contract, and Campaign risk tier. Select Create campaign.
You can create a draft with No segment (bind later) or No template (bind later), but it is not ready for customer delivery. Use the campaign card to complete missing metadata before starting.
Choose the execution contract deliberately. A non-delivering contract can support planning or in-app behavior but is not evidence of outbound email or SMS delivery. A webhook callback contract requires the configured outbound dispatch destination and delivery callback security.
Prepare the audience and consent
Open the attached segment and confirm its Current members. Preview and rebuild executable membership when required, then return to the campaign and select Resync audience.
The sync result separates new pending rows, recipients skipped for missing consent, previously skipped rows promoted after consent, unchanged rows, segment members, and total delivery rows. Outbound email, SMS, or push requires marketing consent plus the matching channel consent. In-app campaigns require marketing consent.
Do not interpret the segment member count as the final deliverable audience.
Start and control the lifecycle
- Draft or scheduled campaigns can be Started or Cancelled.
- Active campaigns can be Paused, Completed, or Cancelled.
- Paused campaigns can be Resumed, Completed, or Cancelled.
- Only draft or cancelled campaigns can be permanently deleted from the campaign card.
When tenant governance requires approval for a high-risk campaign, select Sign off (high risk) before activation. Do not lower the risk tier merely to bypass required review.
Process and verify outbound delivery
For a webhook callback campaign, review Outbound dispatch queue counts for queued, dispatching, dispatched, and failed jobs. Select Process queue batch only when the outbound destination or approved simulation mode is configured. Then refresh the queue and review delivery status counts and errors.
Starting a campaign, producing pending rows, or processing a queue is not proof that the recipient received the message. Confirm the external provider result and the campaign delivery outcome. Use the outbound email settings and recent email activity when the channel is email.
Publish a customer app event
The Customer app event is separate from the internal campaign name and message template. Choose Hidden from customer app or Published to customer app, select Update or Offer, enter the reviewed customer-facing title and message, and optionally set an action label and expiration. Select Publish customer event only after reviewing the guest-facing copy.
Linking a reward template is also separate from delivery. After binding a reward, verify issuance against an authorized test customer and the reward lifecycle rather than assuming every campaign member received it.