Integrate once. Then stop waiting for developers.
Your developers spend an afternoon connecting your app and marking the moments that matter. After that, every mission, reward, streak and marketplace item is something you set up yourself.
Only one of the five steps needs no developer at all.
Everything inside the two lanes happens once. The band underneath is what your own team does every week after that, without opening a code editor.
Reading the diagram: the top lane is the work your developers do once, connecting your app, optionally sending your history, and marking the places in your code where each event fires. The lower lane is the work you do yourself in the dashboard, deciding what counts and what it earns. The band underneath is every campaign after that, which needs neither lane again.
New campaign Tuesday afternoon. Live Tuesday afternoon.
Once the five steps are done, the programme belongs to you. Configuration is not a release, so nobody has to size it and nobody has to schedule it.
| The change you want to make | Who does it | Needs a release? |
|---|---|---|
| Launch a new mission | You | No |
| Change what it pays, or who is eligible | You | No |
| Add a marketplace item, or reprice one | You | No |
| Track something you have never sent us | You declare it; a developer sends it once | One small change |
| Redesign the missions page | Your design team | Yes: it is your app |
Connect your app.
You create a project, then create a key on each side: one for a private sandbox, one for live customers. Your systems then talk to us over ordinary web requests.
Decide what counts.
In the dashboard you name what you track: money spent, visits, signed up, tier, country, and you decide what each one earns.
History, or today.
Send the past across, so a customer of five years does not start at zero. Or switch on and count from today.
Mark the moments.
Your code says where each event fires, and what your platform does when a reward is earned. It never says what anything is worth.
Build your own screens.
A missions page, a streak counter, a points balance, a shop. We hand back the data; how it looks is entirely yours.
Then it is yours
Steps 1, 3 and 4 are the only engineering here, and none of them repeats when a campaign changes.