Incentives
The Incentives console at/marketing/incentives is the shared reward ledger. Every reward your workspace hands out — referral payouts, loyalty redemptions, and one-off promos you mint directly — lands here as one record with a lifecycle of issued, then redeemed or voided. The marketing hub overview positions this console against the other three; the Incentives ledger guide covers standalone promos and auditing in depth.
Incentives is a tenant-owned control. The ledger only contains rewards someone in your workspace issued, and the one-off issue path exists precisely so you can mint a reward with no program rule behind it.
What you see on the page
Issued incentives. One table, newest first:
Filters. A Status filter (All, Issued, Redeemed, Voided) and a Contact ID input with Apply, to audit everything one member has been handed. The table pages 25 rows at a time with Previous and Next.
Issue incentive. The header button opens the issue dialog:
- Reward type — Discount code, Gift card, Custom / manual, or Account credit
- Reward source — where a code-backed reward draws its code from, or automatic
- Contact ID or Recipient email — one of the two identifies the recipient
- Amount and Currency for value-bearing types
- Reference (optional) — an order id, ticket id, or campaign to attach to the record
Who can read and who can act
The dashboard matches the API’s write gate, so a role that can see the ledger in the console can also act on it, while a plain authenticated API key can read the ledger and receives a
403 on writes.
Worked examples
Mint a one-off support credit
- Choose Issue incentive.
- Set Reward type to Account credit, enter the amount and currency, and set the member’s Contact ID.
- Put the ticket number in Reference so the ledger row is traceable later.
- Confirm. The row appears with status
issuedand source marking the standalone path.
Redeem versus void a standing reward
- Choose Redeem on an
issuedrow to mark the reward used. The confirmation warns this cannot be undone. - Choose Void to cancel a reward you no longer want redeemable, for example a credit issued to the wrong contact. Voided rows stay in the ledger so the audit trail holds.
Audit one member’s rewards
- Put the member’s id in Contact ID and choose Apply.
- Switch Status to Issued to see what they still hold, or to Redeemed to see what they actually used.
- A promotion that shows many
issuedand fewredeemedrows is an offer that did not convert; the source column tells you which program or one-off mint produced it.
API pairing
The issue dialog writesPOST /api/v1/incentives/issue:
idempotency_key makes a retry of the same mint safe. Redeem and void map to POST /api/v1/incentives/:id/redeem and POST /api/v1/incentives/:id/void, the same calls the row buttons make.