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 · Fintech

Build habits around the month between paydays.

Money arrives on one day, the direct debits clear behind it, and the last week before the next payday is the tightest. We turn that cycle into activation missions, savings runs and tracks that get a customer using a product they have never tried.

See monthly missions
The rhythm

A customer's month starts on payday, not on the 1st.

A banking customer's month is not flat, and it does not start when the calendar says. Somebody paid on the 25th is flush on the 26th and careful on the 20th. Anchor the cycle on their payday and the campaign lands when they can act on it.

one customer · one cycle
One customer's pay cycle, week by week. Four bars, one per week of a single pay cycle. Spending is highest in the week just after payday and falls in each week after it. A band across all four weeks marks one monthly mission that opens on this customer's payday and closes on the next one. how much they spend that week one monthly mission: payday to the next payday week 1 week 2 week 3 week 4 Spending is highest just after payday and thins out before the next one.

Reading the chart: each bar is one week of a pay cycle. The week straight after payday is tallest, because that is when the direct debits clear. Each week after it is shorter. The band is one monthly mission, opening on this customer's payday and closing on the next.

Mechanics that fit

Reward saving and good habits, never spending more.

An activation track for the first cycle

The first month decides whether an account becomes the account. Three objectives in Sequential order, gated on an attribute you already hold.

how this is set up
Match all of the 3 rules below
Count of card payment ≥ 1 all time
Count of direct debit setup ≥ 1 all time
Sum of savings transfer ≥ 25 all time
Then: award 500 Gems

A savings run counted in days

A streak counts strictly consecutive calendar days; there is no monthly step. Make the daily condition a rolling window: one transfer on payday keeps it true for thirty-one days.

how this is set up
Sum of savings transfer where channel in transfer, standing order rolling 31 days
Then: milestones at 30, 90, 180, 365 days, paid on the crossing only

A wellness track for product adoption

Each step is one mission gated on product_activated with a product_code filter. Gemifier never computes budget adherence; your side sends the verdict as a number.

how this is set up
Match all of the 2 rules below
Count of product activated where product code in pot, roundup, standing order all time
Sum of budget kept ≥ 1 this occurrence
Then: award 150 Gems
Keep reading

The same engine, set up for another industry.

Crypto

Activity in bursts, and a stricter line on inducement.

Read the page

Telecom

A billing month, long tenure, and churn at contract end.

Read the page

Streaks

How a run is counted, and what breaks it.

Read the page

Send us one real event.

Send us the shape of a card payment event. We will build the activation track and the savings run in a test account while you watch.

Read the developer docs