Configuration
Configuration
Targeted Delivery needs more than a campaign form. Before a team can send reliably, the company must have the right promotional mechanics, audiences, channels, templates, credits, and permissions configured.
Use this page as the checklist for everything that must exist before launching a Targeted Delivery campaign.
Prerequisites
| Area | What must be ready |
|---|---|
| Company modules | The company must have the modules enabled for the mechanics it wants to send: Discounts, Points & Wallet, Rewards, Games, Challenges, or Instant Win |
| Promotional engine | For discounts and points, confirm whether the company uses the legacy engine or the new promotional engine, because available mechanics differ. Instant Win requires the new promotional engine |
| Targeted mechanics | The discount, points campaign, reward, game, challenge, or Instant Win must already exist and be available for targeted delivery when the mechanic requires it |
| Audiences | Use a saved Audience or upload a CSV with the Customers to receive the campaign |
| Channels | Email, SMS, push, in-app, or printed message channels must be enabled before they can be selected |
| Templates | Email, SMS, push, and printed message sends require a pre-created message template |
| Credits | Email and SMS sends require available credits in the company account |
| Control group | If measurement is required, the company must have a control group percentage configured before enabling control group on the campaign |
| Permissions | Users need permission to view, create, edit, clone, delete, and send Targeted Delivery campaigns according to their role |
Campaign Settings
| Setting | Purpose |
|---|---|
| Name | Internal campaign name used in lists, history, and reporting |
| Description | Optional internal note explaining the campaign purpose |
| Category | Optional classification label for organizing campaigns |
| Audience | Defines which Customers receive the send |
| Mechanic | Defines what is delivered: discount, fixed points injection, points campaign, reward, game, challenge, Instant Win, promo reminder, or no promotion |
| Control group | Keeps part of the selected Audience unimpacted so reporting can compare impacted vs. non-impacted Customers |
| Schedule | Sends immediately, on a future date, or recurrently. It controls delivery timing only, not discount redemption validity |
| End date | Optional stop date for recurrent sends |
| Channel | Defines how Customers are contacted |
| Template | Defines the message content and dynamic variables for each channel |
| History behavior | Each send creates a Campaign History record; legacy Coupon sends also reference a Coupon History snapshot |
Discount validity is not configured in Targeted Delivery
For discount sends, Targeted Delivery decides who receives the benefit and when the communication/send happens. The redemption window comes from the selected Discount, Coupon, or Voucher:
- New engine Discount: active dates, Coupon/Voucher configuration, limits, and redemption method are configured in the Discounts module.
- Legacy Coupon: availability can be fixed dates or relative days after emission.
- Promo reminder: the reminder points to an existing benefit and does not extend or replace its validity.
Mechanic Availability
| Mechanic | Configuration dependency |
|---|---|
| Discount | Active discount entity. Legacy engine sends a coupon; new promotional engine can deliver a targeted discount campaign |
| Fixed points injection | Active loyalty program and a flat points amount to credit |
| Points campaign | A pre-created targeted Points & Wallet campaign |
| Reward | Active reward in the catalog |
| Game | Active Scratch & Win or Spin the Wheel campaign |
| Challenge | Active challenge in Gamified Campaigns |
| Instant Win | Active Instant Win created with Select customers → Targeted (new promotional engine). In carts, the POS must send the Voucher code or ["all"] in coupons_desired for it to be evaluated |
| Promo reminder | Previous coupon, Voucher, reward, game, or challenge delivery to remind |
| No promotion | Message template only; no benefit is attached |
Channel Configuration
| Channel | Requirement |
|---|---|
| In-app | Customer loyalty interface or app integration |
| Email channel enabled, available credits, and an email template | |
| SMS | SMS channel enabled, available credits, and an SMS template |
| Push notification | App push integration and a push template |
| Printed message | POS receipt integration and a printed message template |
When using email, SMS, or push, send a test message before launching to the full audience.
Validation Before Sending
Before confirming the send, validate:
- The selected audience is correct and consent filters are applied for opt-in channels.
- The selected mechanic is active and compatible with Targeted Delivery.
- The control group setting matches the measurement goal: enabled for lift/ROI measurement, disabled when every Customer must receive the campaign.
- The schedule is correct, especially for recurrent sends and end dates.
- Every selected channel has a valid template.
- Email and SMS credits are available if those channels are used.
- The campaign history should preserve the intended snapshot of audience, mechanic, control group, schedule, channel, and template.
Post-Send Operations
After a campaign is sent, operators should work from the correct tab:
| Operation | Where | Notes |
|---|---|---|
| Reuse a sent campaign | Sent tab | Creates a new pending campaign from the previous configuration; old histories remain unchanged |
| Review send details | Histories tab or campaign detail → history | Shows channel, status, sent date, impacted Customers, Audience snapshot, and attached Coupon/mechanic |
| Open historical Audience | Histories tab → Audience link | Shows the Audience snapshot used for that execution |
| Cancel Vouchers | Histories tab | Cancels issued Vouchers when permissions allow and the impact volume is within platform limits |
| Reprint Vouchers | Histories tab | Reprints Vouchers for selected send histories when permissions allow |
| View statistics | Sent or Histories tabs | Opens campaign/customer statistics for delivered sends |
| Edit future sends | Pending campaign or reused campaign | Do this on a new/pending campaign, not by changing an old send history |
For new-engine Discount sends, edit the original Discount only when the change should affect future evaluations or future sends. Existing Campaign History records are not rewritten, and already issued Vouchers should be managed from the history tools when cancellation or reprint is needed.
For legacy Coupon sends, editing the original Coupon after delivery does not rewrite past Campaign History records. The send keeps its Coupon History snapshot. Only limited history-edit fields are patchable; core fields such as discount value, auto-select behavior, maximum redemptions, forecast estimation fields, and internal IDs are not changed through Coupon History updates.