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
Resources

Everything we have written down.

What setup involves, the questions we get before every integration, worked examples, the reference pages and a glossary. Nothing here is behind a form.

Read the FAQ
The reading list

Every page here explains how something actually works.

Start here

Easy integration

The five steps between signing and a live campaign, and who does each one.

See what setup involves
Answers

FAQ

Effort, customer data, keys, rewards, price, and what the engine does not do.

Read the FAQ
Worked examples

Use cases

Campaigns written out properly: the problem, the rule behind it, and what it pays.

Read the use cases
Reference

Platform overview

The whole engine in one page, and where the line between us and you sits.

Read the overview
Reference

Developer overview

Every endpoint, every field on an event, the key model and the error shape.

Read the developer overview
Reference

Security & data control

Tenant separation, what a customer record holds, key storage, permissions.

Read the security page
Reference

Feature map

One page per mechanic, to check a requirement against what exists.

Open the feature map
That is the complete list. A blog and a public changelog are {coming soon}. If you need something that is not here, ask us and we will write it.
Vocabulary

The words we use, defined once.

This site, the dashboard and the API use the same nouns for the same things. On the wire, your end user is spelled externalPlayerId on the two ingest endpoints and playerExternalId everywhere else, whatever your industry calls them.

how the nouns connect
Something a customer did arrives, and sets off the work that follows. That work reads the conditions you wrote, which are built from what a customer has done, how it is counted and over what period. A satisfied objective inside the current cycle produces a reward, and a points reward is written into the customer's history. Event one thing a customer did Reaction the work that follows Condition tree AND · OR · nestable Objective satisfied or not Grant points, or a prize of yours you send it you configure it the engine records it Environment Sandbox or Live every comparison says what to look at how to count it over what period Occurrence one cycle's window Points history every credit, with its reason
TermWhat it meansWhere you meet it
Metric A number you already track, such as purchase_amount or visits. Number or Currency. ingest · rules
Condition tree Nested AND/OR groups of comparisons. The same shape drives objectives, eligibility, streak days and purchase rules. everywhere
Objective One condition tree inside a mission. It is either satisfied or it is not. missions
Grant The record that a reward is owed. Points, or a catalog item your platform hands over. rewards
Ledger entry One line in a customer's points history, kept with the reason. A balance can never go below zero. points
Idempotency key Your own reference on a request. Sending the same thing twice is safe. ingest
Deactivate is the only removal path, so finished history stays valid. Lock-in means eligibility is checked once, when a customer first qualifies, so a later change never takes away a mission they had started.

Watch it run on your own data.

Bring one mechanic you have been asked to launch. We will configure it in a sandbox and send the event that completes it, live, while you watch.

Contact sales