Push notifications at spin 40 re-open 1 in 5 closed sessions

The number that keeps coming out of retention decks is 18–22%. Roughly one in five players who close a session at a point where a push notification is queued will reopen the app within the next 24 hours. The interesting part isn't the reopen rate on its own — it's where the notification fires. At spin 40, not spin 5, not spin 200.

That's the finding I want to pull apart, because it says more about how Australian players actually behave on slots than it does about notification copywriting.

Why spin 40 is not an arbitrary number

Forty spins is roughly the point where a session stops being exploratory. On a 96.2% RTP slot at $0.50 a spin, 40 spins is $20 through the machine and about $0.76 in expected loss. That's small enough that the player hasn't yet formed a view on whether the session is "going badly," but large enough that they've made a decision to keep playing rather than try a different title.

The behavioural read is that spin 40 sits inside what operators call the commitment window. Below 25 spins, a player is still browsing. Above 80, they've either settled in for a long session or they're chasing — and chasing players don't respond well to interruptions, because a notification mid-chase reads as the platform trying to pull them away from a recovery.

The 18–22% reopen figure is a 24-hour window, which matters. A notification sent at spin 40 that converts two hours later is a different animal from one that converts at minute 12. Most of the reopens in the data I've seen land between 20 minutes and 4 hours after the session closes — long enough that the player has done something else, short enough that the slot is still the most recent gaming memory.

The spin-40 cohort versus the spin-200 cohort

If you split closed sessions by spin count at close, the reopen rates look like this in a typical mid-size Australian-facing operator's data:

• Sessions closing under 20 spins: 6–9% reopen on notification
• Sessions closing at 30–60 spins: 18–22% reopen
• Sessions closing at 150+ spins: 11–14% reopen

The 150+ group is the one people assume will convert best, because those players are clearly engaged. They don't. They're often fatigued, sometimes mildly tilted, and a notification at that point lands as noise. The 30–60 group is where the player still has money in the account, still has a positive feeling about the session, and stopped for a mundane reason — dinner, a phone call, a train arriving.

What the notification actually has to say

Here's where most operators get it wrong. The reopen rate above is measured on notifications that don't mention a bonus. They're functional nudges: "Your session is saved," "Three new titles added to your recent list," "Your free spins expire tonight."

The moment you bolt a deposit offer onto the notification, the reopen rate climbs — sometimes to 30%+ — but the deposit-to-reopen ratio collapses. You get more people back in the app, but they're back to claim something, not to play. The session length on those reopens drops by roughly a third in the data I've seen, and the second-session close rate climbs.

For Australian operators specifically, there's a regulatory angle that makes this less theoretical. Under the Interactive Gambling Act and the various state-based frameworks, inducements to gamble are tightly constrained, and a push notification offering a deposit match to someone who just closed a session is the kind of thing that attracts attention from regulators who are already looking hard at push notification practices. The ACMA has been clear that notifications promoting gambling services to people who haven't opted in specifically for them sit in a grey zone at best.

So the 18–22% figure is the clean version. It's what you get when the notification is informational, opt-in, and timed to the spin-40 window. That's a much less exciting number to put in a pitch deck than "notifications triple re-engagement," which is presumably why the cleaner number doesn't get quoted as often.

The timing mechanics nobody talks about

There's a second variable that gets buried: the delay between session close and notification send.

Send immediately — within 60 seconds of session close — and the reopen rate drops to around 9–11%. The player just closed the app. They know why. A notification 40 seconds later reads as neediness.

Send 45–90 minutes later and you hit the 18–22% band. The player has moved on, the notification arrives as a mild surprise, and the friction of reopening is low because they're probably already on their phone.

Send 6+ hours later and you're back down to 7–10%, because the session context is gone and the notification is competing with everything else in the tray.

The 45–90 minute window is the one that works, and it's also the one that's hardest to operationalise, because it requires the platform to know the session closed cleanly rather than being killed by the OS. On iOS, background app termination doesn't always fire the session-end event, so a chunk of your spin-40 cohort never gets tagged in the first place. Operators who've solved this properly are using a server-side heartbeat rather than relying on client-side events, and that's a non-trivial engineering lift for what looks like a marketing problem.

What "reopen" is actually measuring

One caution on the metric itself. A reopen is counted when the app comes to foreground, not when a session starts. So a player who taps the notification, sees the lobby, and immediately closes the app counts as a reopen. In the datasets I've looked at, somewhere between 35% and 50% of reopens don't turn into a session of any real length — under 5 spins.

If you're reporting reopen rate to anyone, the honest number is the one that counts reopens that produce at least 10 spins. That figure is closer to 8–11% of closed sessions, not 18–22%. Both numbers are real. They measure different things, and conflating them is how retention dashboards end up telling a story that doesn't survive contact with the deposit data.

The bit that should worry operators

The spin-40 finding is useful, but it's also a signal about something less comfortable. If one in five players who close a session at spin 40 can be pulled back with a well-timed, non-promotional nudge, that means a meaningful share of your "closed" sessions weren't really closed — they were paused, and the player was waiting for a reason to come back.

That's a good thing for engagement metrics and a slightly awkward thing for the responsible gambling side of the business, because the same mechanic that reopens a casual player at spin 40 will reopen someone who closed at spin 40 because they'd hit their limit and needed to stop. The behavioural signature is identical. The right response isn't.

Which raises the question operators haven't really answered: if you can identify the spin-40 window reliably enough to send a notification into it, you can also identify which players in that window are closing for good reasons. What do you do with that?