Re-engaging lapsed players: a campaign design

By Isaac Turner, Measurement Editor — Archive date: 5 min read

View author profile
A fading player icon reconnected to a game interface by a dotted return path

A practical design for lapsed player re-engagement: audience windows, deep links, offer structure, frequency caps and the incrementality test.

Re-engagement spend gets approved on instinct more than most UA budget lines: a lapsed player already knows the game, so winning them back feels cheaper and safer than acquiring a stranger. It often is cheaper. Whether it's actually adding revenue, rather than recapturing players who would have come back on their own, depends on a campaign design most teams skip.

Defining lapsed before you define the campaign

"Lapsed" isn't one audience. A player who last opened the app four days ago has a different reason for absence than one who last opened it ninety days ago, and a single re-engagement flow aimed at both will underperform against either. A reasonable starting structure splits lapsed players into at least three windows, something like seven to fourteen days, then fifteen to forty-five, and a third for everyone who has been gone forty-six days or longer, with the offer changing by window and the message and channel changing with it. The short-window group needs no incentive at all; a reminder that something changed since they left does the job. The long-window group is harder. It typically needs a stronger reason to return, and it needs a lower bar for what counts as success, since a portion of that group has genuinely uninstalled or moved on.

Then there are the exclusions. Recently active players go without saying, but the group most briefs forget is players who churned for a reason a campaign can't fix: they refunded a purchase, they filed a support complaint, they hit a hard progression wall that's still there, or they left over a bug nobody has shipped a fix for. Spending against that last group is close to guaranteed waste.

Deep links to the right moment, not the app icon

A re-engagement ad that opens the app to its default home screen wastes the single advantage this channel has over cold acquisition: the returning player's context. Deep linking into the specific content that prompted the campaign converts noticeably better than a generic open. That content might be an unclaimed reward, a season that started while they were away, something a friend did in the game, or a storyline they abandoned midway. Support deep links for the handful of triggers the programme actually uses regularly; the engineering pays for itself. Building one generic link and hoping the ad copy does the work is the cheaper option, and it costs more.

Offer design without training players to lapse on purpose

The obvious lever is a discount or a bonus currency grant for returning. It works. It also carries a real cost if used carelessly: players learn that lapsing gets rewarded, and some will deliberately go quiet to trigger a better offer next time. The mitigation is to cap how often a given player can receive a win-back offer within a rolling window, and to vary offer value so it's never perfectly predictable. Content-based offers, such as early access to a new feature or event, tend to carry less of this risk than currency grants because nobody can farm them the same way.

Channel choice should follow the window, not the media plan default

Owned channels (push notification and email) are usually the right first move for the shortest lapsed window, since the cost of reaching a player who only left a few days ago is close to zero and a paid impression would go to someone who might return regardless. Paid re-engagement products, whether run through a platform's own retargeting tool or a mobile measurement partner's re-engagement attribution, earn their cost in the middle and long windows, where owned channels alone get a lower response rate and a paid nudge with sharper creative has more work to do. Treating all three windows as a single paid campaign with a shared budget line is how studios overspend on the audience least likely to need convincing while underspending on the audience that actually requires a real offer to move.

Frequency caps matter more here than in cold acquisition

Re-engagement audiences are small and finite, so it's easy to over-serve them. A lapsed player who sees the same win-back creative eight times in a week without returning is unlikely to convert on the ninth exposure; the more likely outcome is a player who now associates the brand with nagging. Cap frequency at a level that would look conservative for a cold acquisition campaign, and rotate creative more aggressively than the budget alone would suggest. That protects the audience for future campaigns rather than exhausting it in one push.

The incrementality test that has to come with this

The uncomfortable truth about re-engagement campaigns is that a meaningful share of "won-back" players would have returned anyway, prompted by nothing more than habit or a friend's message. An incrementality test you can afford, whether that's a geo holdout, a ghost-ad design that shows the control group nothing, or a simple randomised suppression of the campaign against part of the eligible audience, is the only way to separate spend that changed behaviour from spend that took credit for behaviour already under way. Running a re-engagement programme without this test means running a programme that can't tell the difference between working and merely coinciding with players who were coming back regardless.

The budget conversation gets much harder to win once someone asks for that number directly.

Related archive reading

These articles provide related context and remain subject to their stated review status.

Featured

Related posts

measurement

media buying

·

1 min read

Using predicted LTV in bids: disclosure checklist for the UA team

measurement

media buying

·

1 min read

Blended ROAS targets that hide channel failure in F2P portfolios

measurement

media buying

·

2 min read

Web-shop LTV with VAT-inclusive prices versus store net proceeds (labelled synthetic)

measurement

media buying

·

1 min read

View-through attribution windows on F2P rewarded and interstitial traffic

More from the Measurement desk

measurement

·

2 min read

Airbridge adds Amazon Ads as an app measurement channel

measurement

·

2 min read

When to freeze a cohort for payback review (and when not to)

measurement

·

1 min read

Web-shop purchaser quality vs store IAP purchaser quality

measurement

·

1 min read

Web-shop attributed revenue in MMP vs payment-provider settlements