Overview Architecture Flexible data model Real-time engine Security & data control
All features Missions Recurring missions Streaks Collections Rules engine Points & loyalty Rewards & catalog Marketplace Segmentation
All solutions Customer activation Customer retention Customer reactivation Loyalty programs VIP engagement Personalized campaigns
All industries iGaming E-commerce Crypto Games Fintech Food Delivery Fitness Streaming Travel Mobility EdTech Telecom
About Contact FAQ Use cases
Why us Easy integration
Developers
Talk to sales
Use cases

Campaigns, written out as configuration.

What each one is trying to fix, the rule behind it, and what it pays. The caveats are the part worth reading.

How the rules engine works
Worked examples

Onboarding, a daily habit, and a points shop.

One-time Sequential

Mission welcome first week

Two steps, worked in order. Step two can only be ticked off after step one, and its all time total still counts earlier purchases, so the first purchase clears it the moment onboarding lands.

how this is set up
Objective 1
Count of signed up ≥ 1 all time
how this is set up
Objective 2
Sum of money spent ≥ 25 all time
500 points, and a welcome voucher recorded as owed for your platform to honour.
Streak Endless

Streak daily visit

The day counts on the customer's own midnight, not a server's. Send their time zone once and it holds.

how this is set up
Daily condition
Count of visits ≥ 1 this calendar day
The run advances by one, and milestones settle with it: day 3 → 100 points, day 7 → a voucher, day 30 → 2,500 points.
Gated 25,000 pts

Marketplace item hospitality invite

Gated on tier, and shown locked rather than hidden, so everyone can see what it takes. Hidden is the same setting, switched.

how this is set up
Eligibility
Attribute tier in Gold, Platinum
Points are spent, stock drops by one, and the grant goes to your platform to fulfil.
Ten calendar days of one streak: seven qualifying days with milestones paid at day three and day seven, one missed day, then a new run that restarts at one while the longest run ever stays at seven daily visit · local calendar day longest ever · 7 1 2 3 +100 4 5 6 7 voucher 1 2 1 Aug 7 Aug 8 Aug 10 Aug run one, reached 7 run two, restarted at 1 8 Aug: no visit was recorded, so the day did not qualify and the counter reset.
  • Streaks have no grace period. One missed day restarts the run at 1, so a day 30 milestone is genuinely rare. Price it that way.
  • An availability window is absolute UTC. It is the same seven days for everyone, not a countdown that starts when each customer arrives.
  • A key is kept for life. Run two campaigns rather than editing one halfway through, or Tuesday stops being comparable to Thursday.
  • You fulfil the reward. We record that a voucher is owed. Your platform hands it over, and your records stay the real account of what went out.
Measuring it

We show programme numbers. Business numbers stay yours.

The dashboard shows active customers, the mission funnel from offered to opted in to finished, points in and out, live streaks and how runs ended, and marketplace sales. It cannot tell you what that did to revenue, because we only hold the events you send, not your sales ledger.

Send each event to your own warehouse at the same moment, carrying the same reference. That reference is the join between your reporting and what we acted on, so nothing has to be exported from us.

Tell us what you want customers to do.

We will configure it in a sandbox and send the event that completes it, live, while you watch.

Contact sales