Activation
Coupon Code Lifecycle
The platform generates, assigns and delivers unique coupon codes across every messaging channel, including tappable codes in WhatsApp, preserving uniqueness at the point of assignment. Redemption and purchase events are ingested back to drive follow-up targeting and measurement, while redemption status and fraud controls run in the connected coupon or POS platform.
This page answers
- How are coupon codes generated and delivered?
- What happens after a code is redeemed?
- Who tracks redemption status and fraud?
- How are redemptions linked to transactions?
Two concerns, one deliberate split
A coupon program spans two concerns: getting a valid, unique code in front of the right customer on the right channel, and tracking what happens to that code afterwards, whether it is redeemed once, redeemed fraudulently, or tied back to an actual transaction.
The platform natively owns the first half. The second half, redemption status, multi-use and fraud detection and POS-level transaction linking, is owned by the connected coupon or POS platform, with the platform ingesting the resulting events to close the loop on targeting and measurement.
Code generation and cross-channel delivery
| Capability | Detail |
|---|---|
| Cross-channel injection | Codes are dynamically inserted into email, SMS, push and WhatsApp messages at send time. |
| Tappable WhatsApp coupons | Codes are delivered as a tappable element within WhatsApp, not plain text a customer has to copy. |
| Uniqueness at assignment | Each single-use code's uniqueness is preserved at the moment it is assigned to a customer, before it is ever sent. |
| Coupon platform integration | Code generation (GS1-compliant formats, bulk generation) integrates with a connected coupon platform such as Eagle Eye or an equivalent provider. |
The lifecycle, lane by lane
- Connected partnerGenerateThe code pool is generated in the coupon platform: format requirements, bulk volumes, uniqueness validation against the wider pool.
- PlatformAssignA unique code is assigned to one customer at the moment of sending; a shared static code where the offer design allows it.
- PlatformDeliverThe code is injected into the email, SMS, push or WhatsApp message; tappable in WhatsApp.
- Connected partnerRedeemThe POS or checkout processes the redemption: real-time status, multi-use detection, velocity rules, fraud-pattern reporting.
- Connected partnerLinkThe redemption is linked to the POS, e-commerce or app transaction it was used on.
- PlatformIngestRedemption and purchase events, with any fraud flags, are ingested back into the platform.
- PlatformActFollow-up targeting, journey entry or exit on redemption, and measurement tying the code back to revenue.
Who owns what
The platform owns
- Storing, assigning and injecting unique static codes into every channel it sends.
- Individual assignment for single-use scenarios or a shared universal code.
- Ingesting redemption and purchase events to trigger the next journey step, progress journeys and feed reporting.
The coupon or POS platform owns
- Code-format requirements, bulk generation volumes and generation-time uniqueness validation.
- Real-time redemption status, multi-use detection on single-use codes, velocity rules and fraud-pattern reporting.
- Linking each redemption to the POS, e-commerce or app transaction, for measurement and fraud investigation.
Why the split
This is a deliberate split, not a gap; it keeps redemption and fraud logic co-located with the system that holds the authoritative, real-time transaction record. The platform is the assignment, delivery and activation layer; the coupon or POS platform is the system of record for redemption status and fraud detection.
In TemasCRM
Every claim is compared with this product: what is live, what is partial, what is planned and what is not applicable by this product's design.
4 Planned1 Not applicable
- Coupon pools assigned inside campaignsPlanned
Coupon codes are rows of the workspace, read and written through the coupon routes; no route binds a list to a campaign or a message, and no code is handed to a person by a send, so the issue ledger stays empty.
Coupon lists - Cross-channel injection at send timePlanned
A template renders three variables, the first name, the last name and the preference link, and none is a coupon; no code is injected at send time, and push channels are closed here.
Campaigns - Tappable WhatsApp couponsPlanned
WhatsApp templates send the code as text; a tappable coupon element needs a template type the API does not define yet.
- Redemption and purchase event ingestionPlanned
No POS or coupon platform is connected; a redemption cannot enter a journey or a report yet.
- Redemption status, multi-use detection and fraudNot applicable
By design these live in the POS or coupon platform, and none is connected here; the product does not pretend to track them.