Reactivating a Dormant Push Subscriber Base

Reactivating a dormant subscriber base means winning back a response from people who stopped opening or clicking your pushes, without paying for new traffic to replace that volume. A dormant base isn't dead weight by definition — it just needs a different approach than your active segment: a different tone, a different sending pace, and an honest willingness to eventually let part of it go. Here's how to tell dormant from active, how to structure a win-back series, and when it's actually time to prune the list.

How to tell when a base has gone dormant

There's no universal number of inactive days that defines "dormant" — instead of borrowing someone else's benchmark, look at your own base's median open cycle: if a typical active subscriber usually responds within a few days, and a given segment hasn't opened or clicked well past that window, it's fair to call it dormant. Segmenting by recency of last action is the most practical way to isolate that group instead of guessing by eye.

Why reactivation often beats buying fresh traffic

A subscriber has already been acquired and paid for once — reaching out again doesn't require new click spend, unlike buying fresh traffic to replace that same volume. Even a modest response rate from a dormant segment often produces better economics per action than cold traffic, especially in verticals with repeat deposits like gambling and betting, where someone who's converted once is statistically more likely to come back than a random new visitor.

How to structure a win-back series

A short series with escalating specificity works better than a single blast: the first push is a soft reminder or a "what's new" note, the second is a more direct offer with a concrete incentive, the third carries a sense of limited time. Each following step should target only whoever didn't respond to the last one, not the whole original group again — otherwise the series turns into repeated spam against the same list.

Timing and send frequency

A reactivation series is better spread across several days than crammed into one, and it should account for the audience's time zone and typical hours of activity in that geo. It's worth running as its own separate track, not overlapping in dates with regular campaigns to the active segment — that makes it much easier to see what response the reactivation itself is actually producing, without muddying overall deliverability numbers.

Which offers work for win-back, and when to clean the list

Tying the message to a specific event or news hook, a major match for betting or a new promotion for gambling, usually pulls a better response than a generic "we miss you" with no specifics. If a reactivation series goes out and still gets no response, it's reasonable to pull that segment out of regular sends instead of hitting it with every future campaign — otherwise open rates and sender reputation suffer across the whole base. APEX's push engine supports segmenting by recency and running both triggered and scheduled series, which covers the technical side of reactivation without a separate tool.

FAQ

After how many inactive days should I launch a reactivation series?
There's no universal number — base it on your own list's median open cycle, not someone else's benchmark, and launch once a segment clearly falls outside that cycle.
How many messages should a win-back series have?
A short series of a few steps with increasingly specific offers is usually enough — a single message rarely wins back someone who's already stopped responding to regular sends.
Should I reactivate the whole dormant base at once?
Better to do it in segments — that makes it easier to judge the real response and protects sender reputation if something in the series underperforms.
What should I do with subscribers who don't respond even to reactivation?
Pull them out of regular sends — continuing to target them usually just drags down open rates and deliverability for the whole active base.
Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free

Read also