Mobile loyalty is the same psychology as a card programme, with a screen and a server attached. The app can know what you did yesterday, remind you about it at the right minute, and change the offer before you get bored. That capability is what turns a points balance from a novelty into a routine - and it is also what makes it very easy to annoy people.
Loyalty on a phone is a different animal
On a card, a loyalty programme had one channel: the till. The customer came to shop, the points were stamped, and the reward came later. The relationship was real but episodic. On a phone, the relationship has a channel that never closes, which is a genuine advantage and a genuine risk.
The advantage is frequency of contact. The EY 2025 US Loyalty Market Study found that more than half of shoppers engage with their loyalty programmes weekly, and that 18-to-24-year-olds are the most likely to use a loyalty mobile app once or twice a week - 53% against 41% overall. More than half of customers in the study said they frequently use mobile apps for their loyalty programmes. That is a channel a publisher can use daily without asking for anything new.
The risk is that a channel which never closes is a channel which can be closed by the customer in one tap. The same permission that lets an app remind someone about a streak lets someone uninstall the app that was nagging them. Mobile loyalty is therefore a notification discipline problem more than a features problem.
The retention loop, in four moves
A retention loop has four parts and every one of them can be the weak link: a trigger, an action, a reward and a reason to come back before the loop closes.
The trigger is what starts the session. It is usually a notification, sometimes a badge on a home screen icon, occasionally a genuine need. The action is what the person does once inside. The reward is what they receive for it - a balance, a tier, a streak increment, a task credit. The reason to come back is the promise that tomorrow will be worth slightly more than today, which is the only part that compounds.
The loop tightens when the four are close together in time and the reward is immediate. It loosens when the reward arrives a day later, because the connection between the action and the credit has been broken by an unrelated evening. A publisher who can only change one thing should change the reward latency first.
Notification strategy
Notifications are the highest-leverage and highest-risured element of a mobile loyalty programme. The reward for getting them right is a returning user; the cost of getting them wrong is an uninstall and a one-star review.
The rule that keeps working is that a notification has to carry information the person cannot get by opening the app. A badge saying there are three offers available is not a reason to open the app - the person can see the offers when they open it. A notification saying a streak expires tonight, or that a mission is nearly complete, is a reason, because the cost of not acting is specific and the action is one tap.
Frequency is the second rule, and it is about the person rather than the average. Opt-in rates vary by category and by platform, so a publisher should read its own numbers rather than assume the benchmark. What is universal is the shape of the curve: push permission is granted generously at install and withdrawn quickly once notifications feel like noise, so a programme that spends that permission on generic reminders has spent the only asset it had.
Timing is the third. Loyalty notifications are time-sensitive by definition - a streak that expires at midnight, a mission that ends at midnight - and the hours around waking and around the evening commute reliably carry more engagement than the middle of the working day. The right time is a per-person question, and the only honest way to answer it is to test it against your own retention rather than copy a published hour.
Lifetime value, calculated properly
Lifetime value is the number of days a user generates value for, multiplied by the value they generate per day. Publishers usually know the second number and guess the first, which is why their forecasts are wrong.
The first number is not a projection, it is a measurement of the shape of the curve. Take your day-one, day-seven and day-thirty retention numbers, and look at how the ratio between them behaves as the cohort ages. If day-seven is half of day-one and day-thirty is a fifth of day-seven, the shape is steep and the lifetime is short. If day-thirty holds at a third of day-seven, the shape is shallow and the same cohort is worth several times as much.
On the earnings side, a mobile loyalty programme usually has two revenue lines: what the person spends in the app, and what the rewarded activity earns. They behave differently and they should not be averaged. Spend-driven revenue scales with the value of the app's own catalogue. Rewarded revenue scales with how much attention the person is willing to give, which is exactly the thing loyalty mechanics are there to increase. A publisher whose lifetime value calculation adds the two together can hide a broken retention loop behind a strong catalogue, and vice versa.
The most useful number is not LTV at all. It is the payback period: how long until the revenue from a user covers the cost of acquiring and keeping them. On mobile, a day-30 retention figure that looks acceptable can still hide a six-month payback, which is longer than most of these apps exist.
What mobile loyalty needs from the publisher
It needs somewhere to spend the points. A balance that cannot be spent on anything real is a receipt, and receipts do not build habits.
It needs the app to be worth opening on the days there is no mission. Players notice the empty days, and those are the days a streak is decided.
It needs its notifications to be worth receiving. If the app is genuinely useful between missions, the permission it spends is being spent on something real.
And it needs the reward to arrive on time, every time. Everything above depends on that one thing, which is why the fastest way to lose a loyalty programme is to let a payout slip.
Related reading
Run rewards in your app
Tell us the platform and roughly how many daily active users you have, and we will tell you whether rewarded games, surveys or both are the better fit.
Questions
What is a retention loop in a mobile app?
A retention loop is the cycle that brings a person back: something triggers them to open the app, they do an action, they get a reward, and they have a reason to return before the cycle closes. The four parts - trigger, action, reward, reason to return - each weaken the loop in a different way, so diagnosing a retention problem usually means finding which part is broken rather than adding features.
How often should a loyalty app send push notifications?
As often as the notification carries something the person cannot get by opening the app, and no more often than that. A streak at risk, a mission nearly complete and a reward ready to redeem are reasons to notify. A count of available offers is not. Permission is granted generously at install and withdrawn quickly once notifications feel like noise, so spend it on reasons rather than on reminders.
How do I calculate LTV for a mobile loyalty programme?
Multiply the number of days a user stays by the value they generate per day, and separate the two revenue lines - in-app spend and rewarded activity - because they respond to different mechanics. The number to watch alongside LTV is payback period: how long until a user's revenue covers what it cost to acquire and keep them. A strong day-30 retention figure can still hide a payback period longer than the app's expected life.
Should a loyalty app live inside a rewarded app?
It can, and many do, but keep the two balances and the two purposes apart. The rewarded activity pays in money for tasks completed on behalf of advertisers; the loyalty mechanics pay in points or status for returning. If the offer wall becomes the main event, the loyalty programme starts competing with itself for the same session.