Create a Targeted Delivery
Targeted Delivery lets you explicitly send a promotional mechanic to a specific audience. Unlike promotions that fire automatically for all qualifying Customers, targeted delivery is a deliberate send: you choose the audience, choose what to deliver, and decide whether to send immediately or schedule it.
Go to Campaign Personalization → Targeted Delivery → New targeted delivery.
Configuration
Step 1: General Settings
| Field | Description |
|---|---|
| Name | Internal campaign name |
| Description | Optional internal explanation of the campaign's purpose |
| Category | Optional label used to classify and organize campaigns |
Targeted Delivery campaigns do not define the redemption validity of a discount. They define the campaign identity and, later in the flow, the send date or schedule. The validity of a discount benefit is controlled by the selected Discount, Coupon, or Voucher configuration.
Step 2: Audience
Select a saved Audience (Customer segment) or upload a custom list via CSV. All Customers in the audience at the time of sending receive the selected mechanic, message, or reminder.
If the campaign should measure incremental impact, enable Apply to control group. The platform keeps part of the selected audience as non-impacted Customers, so reporting can compare Customers who received the campaign against Customers who qualified but were intentionally held out.
Use a control group for campaigns where business impact matters, such as product reactivation, CPG/supplier-funded activations, win-back campaigns, and ROI measurement. Do not use it when every Customer must receive the benefit, such as service communications, mandatory notices, or operational messages.
Step 3: Promotional Mechanic
Choose what the campaign delivers. The available options depend on the modules enabled for the company and, for discounts and points, whether the company uses the new promotional engine or the legacy engine:
| Mechanic | What it delivers | Notes |
|---|---|---|
| Discount | A coupon or discount campaign assigned to the audience | In the legacy engine this sends a coupon; in the new promotional engine this can deliver a targeted discount campaign. |
| Fixed points injection | A fixed amount of points credited directly to each Customer's wallet | Use this when the campaign should grant the same balance amount to every selected Customer. |
| Points campaign | A pre-created targeted Points & Wallet campaign | Use this when the campaign should apply the configured points campaign logic instead of a flat points amount. |
| Reward | A reward from the catalog granted to the audience | Use this for gift-led campaigns or member recognition without requiring points redemption. |
| Game | A Scratch & Win or Spin the Wheel campaign | The play outcome determines whether the Customer receives a Voucher or reward. |
| Challenge | A challenge assigned to the audience | The Customer receives or joins the challenge and completes its conditions later. |
| Instant Win | A Targeted Instant Win ("Give customers a chance to win instant prizes triggered by their actions.") | The selector lists only Instant Wins created as Targeted. A Voucher is generated per impacted Customer; each qualifying cart, trigger, or custom event then runs the prize draw. In carts, the POS must send the Voucher code or ["all"] in coupons_desired. See Instant Win in Targeted Delivery. |
In addition to promotional mechanics, you can also select:
| Option | Use |
|---|---|
| Promo reminder | Send a reminder to an audience that already received a coupon to improve redemption |
| No promotion | Send an informative message (email, push, SMS, or printed message) without attaching any offer |
The mechanic you select must have been previously created and marked as "Targeted" when the mechanic requires audience delivery. Contact your Customer Success Manager if you are unsure which engine or modules your company uses.
Step 4: Scheduling
Configure when the campaign sends:
| Option | Description |
|---|---|
| Immediate | Sends as soon as you confirm |
| Scheduled | Sends at a specific future date and time |
| Recurrent | Repeats on a configured interval; optionally set an end date |
Scheduling controls when the campaign is delivered, not when the discount can be redeemed. For discount sends:
| Discount model | What controls redemption validity |
|---|---|
| New engine Discount | The Discount active dates, Coupon/Voucher configuration, limits, and redemption method configured in the Discounts module |
| Legacy Coupon | The Coupon availability fields: fixed availability dates or relative days after emission |
| Promo reminder | The original Voucher, Coupon, reward, game, or challenge validity; the reminder does not create a new benefit |
Use case — Scheduled points grant to a segment
To grant points to a specific group of Customers on a future date (e.g. a loyalty bonus for VIP members at the start of a campaign):
- Create a Points & Wallet points campaign marked as Targeted
- Go to Campaign Personalization → Targeted Delivery → New targeted delivery
- Select the audience (e.g. "Gold members" or a custom CSV list)
- Choose Points & Wallet as the promotional mechanic
- In Step 4, select Scheduled and set the exact date and time
- Confirm — each Customer in the segment will receive the points at the scheduled time
For recurring grants (e.g. monthly loyalty bonus), use Recurrent instead of Scheduled and set the interval and end date.
Step 5: Channel
Select the delivery channel. Channel-specific message templates must be created beforehand.
| Channel | Requirements |
|---|---|
| In-app | No credits required — offer appears in the Customer's loyalty interface |
| Email credits required (Configuration → Company → Credits) + a pre-created email template | |
| SMS | SMS credits required + a pre-created SMS template |
| Push notification | App with push permissions configured + a pre-created push template |
| Printed message | A printed message template pre-configured in the system; prints on the receipt at POS |
When using email, SMS, or push channels, you can send a test message to verify the template renders correctly before launching to the full audience.
Step 6: Review and Send
Review the configuration and audience size estimate, then confirm the send. If the control group is enabled, validate that the expected impacted and non-impacted volumes are acceptable before launching. Each send creates a Campaign History record that preserves the exact execution snapshot independently of any future edits.
Send History
From the campaign detail page, click Send History to see all past sends. Each send creates a Campaign History record. If the send delivers a legacy Coupon, it also points to the Coupon History used for that send.
The history record is the operational snapshot of the execution. It preserves what was sent, to whom, through which channel, and with which Coupon or mechanic configuration at that time.
| History field | Meaning |
|---|---|
| History ID | Unique ID of the send execution |
| Campaign ID / name | Campaign definition that generated the send |
| Via | Delivery channel: in-app coupon, email, SMS, push, printed message, or message-only send |
| Status | Execution status, such as checking, sending, delivered, delivered with errors, or error |
| Sent at | Date and time when the send was executed |
| Sent number / impacted | Number of Customers impacted by the send |
| Audience | Historical Audience snapshot used for that send; opening it shows the Customers calculated for that execution |
| Coupon / mechanic | Coupon, targeted discount campaign, points campaign, reward, game, challenge, Instant Win, or message attached to the send |
| Distribution | Coupon distribution type when relevant, such as normal, multiple, or periodic |
Can I Modify a Sent Targeted Delivery?
Once a Targeted Delivery has been sent, do not treat it as an editable draft. The sent execution is preserved as Campaign History so support, reporting, and voucher operations can always reconstruct what happened.
| Need | What to do |
|---|---|
| Change the audience, channel, schedule, or message for a future send | Use Reuse from the Sent tab. This creates a new pending Targeted Delivery based on the previous setup. |
| Correct or change the benefit for future use | Edit the underlying Discount, points campaign, reward, game, challenge, Instant Win, or legacy Coupon only if the change should affect future evaluations or future sends. |
| Cancel a benefit already assigned to Customers | Use the History tools to cancel issued Vouchers when permissions and volume limits allow. |
| Reprint assigned Vouchers | Use Reprint Vouchers from the Histories tab. |
| Audit what was sent | Open the Campaign History record; it keeps the execution snapshot and historical Audience. |
Editing a sent Targeted Delivery directly would make support and reporting ambiguous. If the business wants to run the same idea again with changes, create a new pending send through Reuse.
If the delivery uses a static coupon code, remember that the same static code cannot be reused to create a different campaign/coupon. A static code can be shared by multiple assignments inside its original campaign, but a new campaign/coupon needs its own static code.
New Engine Discount Sends: What Changes After Sending
For new-engine discounts, Targeted Delivery assigns the selected Discount to the impacted Customers by creating Vouchers or coupon-gated relationships, depending on the Discount's redemption configuration. The send history preserves the execution context, while the Discount remains the source of truth for future evaluations.
| Area | After sending |
|---|---|
| Targeted Delivery campaign | Sent campaigns are no longer edited in place. Use Reuse to create a new pending campaign from the previous setup. |
| Campaign History | Preserves who was impacted, the channel, send status, Audience snapshot, and selected mechanic at execution time. |
| Original Discount | Can be edited from the Discounts module for future use, subject to permissions. Changes do not rewrite old send history records. |
| Existing Vouchers | Already issued Vouchers keep their ownership and operational status. They can be canceled or reprinted from history when permissions allow. |
| Discount validity | Controlled by the Discount/Coupon/Voucher configuration, not by the Targeted Delivery send date. |
| Fields to avoid changing after send | Be careful with changes that affect customer-facing promises, such as discount value, validity, product scope, limits, or redemption behavior. Prefer creating/reusing a new campaign when the business wants a different offer. |
Legacy Coupon History: What Changes After Sending
For legacy Coupon sends, the campaign does not keep pointing only to the latest editable Coupon. It references a Coupon History: the version of the Coupon used by that send. This matters because future edits to the original Coupon should not silently rewrite what was already sent.
| Area | After sending |
|---|---|
| Original Coupon | Can be edited for future sends. Changes affect new campaigns or new histories, not past send records. |
| Coupon History | Can be opened from the historical send or coupon history list. It represents the Coupon version used in that execution. |
| Editable on Coupon History | Limited fields that the Owner App allows to patch on the historical version, such as descriptive/configuration fields still exposed in the history edit form. |
| Not editable on Coupon History | Core execution/financial fields that are not patched on history updates: discount value, auto-select/auto-redeem behavior, maximum redemptions, forecast estimation fields, and internal IDs. |
| Audience snapshot | Historical Audience membership is preserved for the send. Reusing or editing the campaign recalculates the Audience for the new execution. |
| Vouchers already issued | Managed from the history record: they can be canceled or reprinted when permissions allow, but they are not replaced by editing the base campaign. |
Use Reuse from the Sent tab when the business wants to run a similar campaign again. Reuse creates a new pending campaign from the previous configuration; it does not modify the old Campaign History or Coupon History.
Budget and Limits Per Send
Budget and per-transaction limits apply per send record, not across all sends of the same campaign. Increasing the budget for a new send does not affect previous sends' accounting.
How It Works
- You create a campaign with a name, select an Audience, and choose a promotional mechanic (or a reminder / informative send).
- You enable a control group when the campaign needs incremental lift or ROI measurement.
- You configure the schedule (immediate, scheduled, or recurrent) and select a delivery channel with its message template.
- You confirm and validate the send.
- Each impacted Customer in the audience receives a unique voucher code tied to their identity (for promotional sends).
- The send is recorded as a history entry with an immutable snapshot of the configuration.