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
Industries · E-commerce

Get customers ordering again sooner.

A customer orders, goes quiet for weeks, then arrives with everyone else in a season. Daily mechanics are wrong for that shape. What works is a mission aimed at the second order, a collection that walks them into a category they have never bought from, and status earned on what they spent recently rather than ever.

See how collections work
The rhythm

The problem is the weeks of silence between orders.

A retail year is a handful of orders separated by weeks of silence, then a season that squeezes months of demand into three weeks. A daily mission would sit unfinished almost every day of that year.

one customer · one year
Twelve months of one shopper. Twelve bars, one per month. There is a first order in February, then months with nothing at all, a second order in June, quiet again through the summer, and a cluster of larger orders in November and December. A band over the months between the first and second order marks the gap a second-order mission is aimed at. orders that month a second-order mission works here Jan Feb Jun Nov Dec Two orders all year, then a season that carries the rest.

Reading the chart: each bar is one month. A first order in February, nothing until a second in June, then a cluster in November and December. Two orders carry most of the year. The band covers the gap between the first and second order, which is what a second-order mission is aimed at.

Mechanics that fit

Build a second-order mission, a category collection and status on spend.

First order to second order

A mission with no recurrence opens when the customer joins and stays open until the objectives are met. The discount_code filter means an order already bought on a code never earns the reward twice.

how this is set up
Match all of the 2 rules below
Count of product views events ≥ 5 this occurrence
Sum of order value where discount code does not exist ≥ 35.00 this occurrence
Then: award 400 points and record a grant against free delivery 30d

A category collection

One mission per department, listed inside the collection only. The department is a property on the event, so adding one is a rule change.

how this is set up
Match all of the 2 rules below
Count of product views where category = homeware · ≥ 3 all time
Count of order value where category = homeware · ≥ 1 all time
Then: award 150 points · collection at 3 of 6

Status on trailing spend

A tier is a condition you attach to what it unlocks. Trailing twelve months survives the seasonal spike. The second branch lets frequency qualify.

how this is set up
Match any of the 2 rules below
Sum of order value ≥ 600.00 rolling 365 days
Count of order value events ≥ 6 rolling 365 days
Keep reading

The same engine, set up for another industry.

Food delivery

Frequent and habitual, on a weekly rhythm.

Read the page

Travel

Gaps measured in seasons, not weeks.

Read the page

Collections

How a themed set is assembled from missions.

Read the page

Send us one order event.

Send us the shape of a single order event. We will build the second-order mission and a category collection in a test account while you watch.

Read the developer docs