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
Streaks

A run of days on which a customer did what you asked.

A streak counts consecutive days on which a customer did what you asked, whether that is opening the app, spending 20 euros, or finishing a lesson. One missed day restarts the run at 1. Their best run ever is kept for good, so you can build a campaign around beating it.

How conditions work
How a streak is counted

Two numbers are kept: the run they are on, and their best ever.

The run they are on drops back to zero the day they miss. Their best ever never drops. So a customer who reaches day 7, misses a day, then starts again is back on day 1 with a best of 7 still on the record and something to beat.

one customer, twelve days of a daily visit streak
Twelve calendar days of one streak: seven qualifying days with milestones paid at day 3 and day 7, one missed day, then a new run that reaches day 3 again, while the longest-ever count of 7 stays where it is. a day that counted a reward was paid their best ever best ever · 7 1 2 3 day 3 paid 4 5 6 7 day 7 paid 1 2 3 day 3 paid again 4 1 2 3 4 5 6 7 8 9 10 11 12 first run, seven days missed second run, back to day 1
  • You pick which days pay. Here it is day 3 and day 7, paid the moment the run reaches them.
  • Their best stays at 7. A reset never lowers it, so there is always something to beat.
  • A day counts once. The same event sent twice never double-pays.
What counts as a day

Opening the app can count. So can spending 20 euros.

A day counts when the rule you wrote is true on that day, and you write that rule in the same editor as everything else. Set the bar low to build a habit, or high to make the run worth something. You can move it whenever you want.

  • Built from anything you track. A number your product counts, or something you already know about the customer.
  • Counted, added up or averaged. One order, three lessons, twenty euros of spending in a day.

At the end of the day the answer is yes or no. There is no half a day. See how conditions are written.

how this is set up
Match all of the 3 rules below
Count of visits ≥ 1 this calendar day
Sum of money spent ≥ €20 this calendar day
Attribute tier in silver, gold
The day qualifies: the run advances by one, and any milestone it crosses settles with it.
What a streak will not do

There is no freeze and no way to buy a missed day back.

Some products let a customer pay to protect a run or skip a day. This one does not. Miss a day and the run restarts at 1. We would rather tell you that now than have you discover it after launch.

You cannot buy the day back

Miss a day and the run restarts at 1. What survives is their best-ever count, so "beat your own record" is the campaign to build here.

A run is counted in days, never weeks

A run counts consecutive days. The daily test can look back over a week, but the run is always in days.

If your business needs forgiveness, use a repeating mission instead. A weekly one forgives by design.

Watch a run advance, pay out, then reset.

Tell us the habit you want customers to build. We will set it up in a test account and carry a run all the way to a paying milestone while you watch.

Contact sales