Why us Easy integration
Developers
Talk to sales
Capability map

Every mechanic here is built with the same rule builder.

Missions, streaks, points, rewards and the shop are all ways of asking questions about the numbers you track, or want to start tracking. The question is written in the same builder every time, so learning to build one campaign teaches you how to build any of them, with no release.

How they fit together

Build one campaign and you know how to build all of them.

Each mechanic sits on the one below it. A streak is a mission that repeats and counts days. The shop spends the points that missions pay out. So your first campaign is most of the learning you will ever do here.

capability stack
The Gemifier capability stack: your data model at the base, the conditions engine above it, then the mechanics, then rewards and points, with collections on top for presentation. Collections Ordered sets and themed tracks, for presentation only how it is shown Rewards & points Points credited · your prize recorded for fulfilment what it pays Mechanics Missions · Streaks · Marketplace items what customers do Conditions engine 13 operators · nested AND / OR · 5 time windows shared by all Your data model The numbers and customer details you already have you define it

Read it from the bottom. You name what your product already counts, then say what has to be true about it. The same builder writes a mission objective, a streak's daily test and a marketplace item's rule.

  • Add a new number to track and every mechanic can use it the same day
  • One setup, then unlimited campaigns, no release, no engineering ticket
  • Create it in Sandbox and Live in one go, then test in Sandbox. Nothing goes out until it validates
  • You own the rules. No database access, no personal data required, your app fulfils

Tell us what you want customers to do.

Describe the behaviour you want to encourage. We will build the rule for it in a test account and send the event that completes it, while you watch.