Skip to main content

​
Marketing hub overview

The Marketing hub holds the four consoles that launch and run growth programs on your contact base: Referrals, Loyalty, Incentives, and Wallet Passes. This is the retention and acquisition stack — how members earn, share, and carry your brand — separate from campaign sends. Nothing here transmits a message by itself; a referral link or a wallet pass traveling over SMS, WhatsApp, or email just borrows the channel for delivery. Every console is a tenant-owned control: programs, balances, rewards, and passes live in your workspace only, and nothing applies until you create it. Each console maps to one route under /marketing in the dashboard. This page is the map — it tells you what each tile answers and which one to open first. The deep, task-by-task walkthroughs live in the guides each console links to.

​
1. The four consoles at a glance

Referrals — /marketing/referrals. The member-get-member loop. The console holds the reward definition, a share code per contact, funnel KPIs (visits, signups, paid out), the referrer leaderboard, and the pending-reward queue you approve payouts from. A spreading program shows up here first, in the funnel and the leaderboard, before it shows up anywhere else. Loyalty — /marketing/loyalty. The standing membership. The console holds the earn rules and tiers, and per member the point balance with adjust and redeem actions — adjust applies an explicit credit or debit with a reason; redeem burns points through the incentives engine and blocks overspend. A sticky balance shows up as members earning, climbing tiers, and redeeming without you prompting them. Incentives — /marketing/incentives. The shared reward ledger. Every issued reward — referral payouts, loyalty redemptions, survey thank-yous, and one-off promos you mint directly — lands here as a single record with a lifecycle: issued, then redeemed or voided. Sort or filter by a promo and this console tells you which offers convert and which sit issued forever. The one-off import path — mint a support credit or win-back reward without a program rule — lives here too. Wallet Passes — /marketing/wallet-passes. The artifact on the holder’s phone. The console lists issued Apple Wallet and Google Wallet passes — loyalty cards, coupons, event tickets — and drives their issue → update → void lifecycle. The generation counter on each pass is the holder-refresh signal: bump it and every device holding that pass refreshes its content without a re-save.

​
2. When which console

Start from the goal, not the tile: Two fall out of this table naturally: Incentives is the engine the other three ride (it is where referral payouts and loyalty redemptions post), and Wallet Passes is the display surface (it is where balances and coupons show up on the holder’s phone).

​
3. Route guards and access

Each console renders for the operators whose workspace role can act there:
  • Referrals — program creation, code issuance, and payout approval are gated to the owner, admin, and developer roles; reads — list, leaderboard, totals — need only authentication.
  • Loyalty — program configuration (earn rules, tiers, adjust, redeem) follows dashboard workspace-role rules; member balances are read-only to roles without configuration access.
  • Incentives — issuing, redeeming, and voiding follow the same workspace-role rules as configuration; the ledger itself reads with authentication.
  • Wallet Passes — API keys with contacts:write issue and void passes; reads accept contacts:read.
The underlying models live in the concept pages: Referral program model, Loyalty program model, Incentives, and Wallet pass lifecycle. For programmatic access, see the Referrals API reference and the Loyalty API reference.

​
4. Quick start per console

Pick your entry tile and take the guide that owns it:

​
5. How the four compose

The consoles are one system, not four products. They share members and rewards, and each fills a different seat:
  • A referral can credit a loyalty balance. Set the referral reward to loyalty points and approved payouts post directly into the member’s standing balance instead of a one-off promo.
  • An incentive can issue a wallet pass. A coupon offer redeemed in the incentives ledger can carry a pass, so the reward lives on the holder’s phone instead of a code in an email.
  • A loyalty card is the holder artifact. Issue the wallet pass first; the earn rules the Loyalty console defines later target that pass, and the generation counter tells holder wallets to refresh without a re-save.
  • The ledger is shared. Referral payouts, loyalty redemptions, and standalone promos all flow into the incentives ledger, tagged by source — so one place audits everything a program ever handed out.
The shortest path to a working program: Wallet Passes (the artifact), then Loyalty (earn rules on that artifact), then Referrals (the acquisition loop, optionally paying out in points), with Incentives auditing every reward the other three hand out.