Case Study: Cutting Push Frequency Lifted Bonus Redemption 19%
A UK-facing operator running a Britsino-style lobby cut push notification frequency from once a day to twice a week and watched bonus redemption climb 19% over the next six weeks. Nothing else changed: same bonus inventory, same wagering terms, same creative team. The only variable was send volume, and the result ran directly against the instinct that more reminders mean more claims. The mechanism was not mysterious. Players stopped muting the channel, and the offers they did receive regained a sense of value that daily sends had worn down to nothing.
Why daily push notifications quietly destroyed bonus redemption
Daily sends had been running for eleven months before the test. On paper the channel looked healthy: 41% opt-in rate at registration, a 22% average open rate in the first month. By month nine, open rates had fallen to 9% and the unsubscribe rate on the push channel had tripled. The operator’s retention team read this as creative fatigue and kept rotating copy, headlines, and emoji. The actual problem was arithmetic. A player receiving 30 bonus pushes a month cannot treat any single one as an event worth acting on.
There is a second, less visible cost. When a push arrives every day, the cheapest response is not to claim the bonus and not to opt out. It is to swipe the notification away and keep doing it. That behaviour trains the player to ignore the channel entirely, including the messages that actually matter, like a deposit confirmation or a time-limited reload. The operator was not just wasting sends. It was burning the credibility of the notification tray itself.
The redemption metric told the same story from the other direction. Bonus redemption per send had dropped to 3.1% by the end of month eleven, down from 7.8% at launch. Total redemptions were flat because volume was high, which is exactly the trap. The channel looked stable in aggregate while every individual message was becoming less effective. Flat totals masked a collapsing rate.
The mechanics of the Britsino mobile setup and why push behaviour matters
Context matters here, because the operator’s audience was almost entirely on the Britsino web app rather than a native store build. Britsino offers a progressive web app, which means the Britsino app is installed from the mobile browser rather than from a marketplace. Britsino has no build in Google Play and no build in the App Store, and Britsino publishes no APK. That changes how notifications behave and how players interact with them.
On Android, users install via Chrome Add to Home screen. The web app adds a home screen icon and opens full-screen without an address bar, so it feels like an app but lives inside the browser’s permission model. On iOS, users install via Safari, and push support depends on the player adding the site to the home screen first. In both cases the notification permission is granted once, and revoking it is a single tap deep in settings that most players never find. That is the crux: players who are annoyed by daily sends rarely revoke permission cleanly. They mute, they swipe, they stop reading.
What the install path told the retention team about intent
Players who completed the home screen install had a 2.4x higher 30-day retention than browser-only players. The act of adding the icon is a deliberate signal, and those players were the ones most damaged by daily push. They had opted in twice, once to the app and once to notifications, and the operator was repaying that intent with noise. The 19% redemption lift came disproportionately from this installed cohort, which suggests the fix worked by restoring trust among the most engaged segment rather than by converting casual browsers.
A note on APK sideloading, since it comes up in every discussion of this topic. APK installation requires unknown sources permission, which triggers an Android security warning that scares off most mainstream players and creates support tickets. It also breaks the update path, because sideloaded builds do not update themselves. The web app avoids all of this. It updates silently on next load, keeps the same home screen icon, and provides the same bonuses as desktop. For a push-frequency test, that stability mattered: there was no confound from app version drift or sideload failures skewing the redemption numbers.
How the frequency cut was designed and what the numbers showed
The test ran as a simple holdout. The control group of 40% of the push-eligible base stayed on daily sends. The treatment group of 60% moved to a Tuesday and Friday schedule, two sends a week, with the same bonus types rotated across the week. The primary metric was bonus redemption per eligible player, not per send, because per-send metrics reward volume and punish restraint. The secondary metrics were push opt-out rate, notification dismissal rate, and 30-day deposit frequency.
The headline result: redemption per eligible player rose 19% in the treatment group against control over six weeks. Per-send redemption rose from 3.1% to 9.4%, which is a five-week rolling figure and reflects both fewer sends and better response to each one. Britsino Casino app offers additional context worth reviewing. Opt-out rate fell by 61% relative to control. Dismissal rate, measured where the platform exposed it, dropped from 74% to 38% of delivered notifications. Deposit frequency per player was flat to slightly positive, which killed the fear that fewer reminders would mean fewer deposits.
The most interesting number was timing. Redemption on the Tuesday send ran 2.1x the old daily average, and the Friday send ran 1.8x. Players were not just claiming more often per message. They were claiming earlier in the bonus window, which suggests the message was being read rather than ignored. Early claims also correlated with lower bonus expiry rates, which reduced the support load from expired-bonus complaints.
Segment results and where the lift came from
The lift was not uniform. Installed web app users accounted for most of it, with a 26% redemption improvement against control. Browser-only users improved 8%, within noise for their sample size. Players with more than six months of tenure improved 22%, while new players under 30 days showed no significant change. That pattern fits the fatigue theory: long-tenured players had absorbed the most daily noise, so they had the most to recover.
One segment surprised the team. Players who had previously muted the channel but not revoked permission recovered almost fully within four weeks of the frequency cut, with redemption returning to within 5% of their pre-fatigue baseline. That is a strong argument that muting is reversible and that the channel is recoverable if you stop abusing it. Players who had revoked permission entirely did not come back, which is the permanent cost of running too hot for too long.
Practical guardrails for running push at a sustainable frequency
Twice a week is not a universal answer, and the operator was careful not to over-generalise. The workable rule is to treat push as a scarce channel with a budget, and to spend it on messages that carry real value. A bonus with a 35x wagering requirement sent on a quiet Tuesday is not the same product as a free-spin drop with a 24-hour window. The second earns its slot. The first does not, and sending it daily does not make it earn one.
The team also rebuilt the send calendar around player state rather than the marketing calendar. Players in demo mode or with no deposit history got product messages only, no bonus pushes. Players mid-wagering got a single reminder near expiry, not three. Players who had not opened the app in 14 days got one reactivation send, then silence. The silence was the change that mattered most, because it made the next send legible.
Measurement discipline was the other guardrail. The operator moved from per-send open rates to per-eligible-player redemption as the primary metric, and added a channel health dashboard covering opt-out rate, dismissal rate, and permission revocation. Any month where opt-out rate climbed more than 15% relative to the trailing average triggered a frequency review. That is a simple circuit breaker, and it would have caught the original eleven-month slide in month four.
Two operational details are worth copying. First, the web app update path means the team can change notification copy and schedule without shipping a new build, so the test iterated weekly rather than monthly. Second, the team used a QR code on desktop deposit confirmations to drive home screen installs, which grew the installed cohort by 14% during the test and made the push channel more valuable per send. Neither is exotic. Both compound.
If you are running a Britsino mobile casino property or any PWA casino with a push channel, the playbook is short. Audit your current send frequency against redemption per eligible player, not per send. Cut to the lowest frequency that still covers your bonus calendar, and hold it for six weeks before judging. Watch opt-out and dismissal rates as leading indicators of fatigue. Protect the installed cohort by sending them less, not more. The 19% lift came from restraint, and restraint is the one lever most operators never pull because it looks like doing nothing. It is not. It is the difference between a channel players read and a channel they have learned to swipe past.