Every quarter, the same meeting happens at most operators. The acquisition team reports the new-player number and takes the credit. Nobody reports how much of last quarter’s acquisition is already gone. Push notifications for betting sites are the cheapest way to close that gap — the one owned channel fast enough to reach a bettor in the minutes when a line actually matters — and, since 2026, the easiest channel to get wrong. This playbook covers why push fits betting economics, what the platform crackdown changed and when, and the 90-day path from blast-everything to a retention engine.
The leaky bucket: betting site retention is a CAC problem
Acquisition costs in this vertical move in one direction. Affiliates take CPA or revenue share, media gets bid up around every major event, and the welcome bonus is a real cost of goods. The player’s switching cost, meanwhile, is close to zero: the next operator is one search away with a richer signup offer. Every player you fail to retain gets re-acquired later at full CAC — often by a competitor.
The push list leaks the same way, mostly in silence. In one 90-day window, unsubscribes erased roughly 91% of new subscriber acquisition across the segment. The list that acquisition celebrated barely grew.
Much of that decay is now invisible. Chrome automatically removes notification permission from sites that send high volume to people who never interact — no opt-out click, no dashboard event, just a list that quietly stops being real. The subscribers most operators blast hardest are precisely the ones the browser removes first.
That is why betting site retention is a CAC problem before it is a marketing problem. A push subscriber is the one asset you own outright and can re-engage at near-zero marginal cost. Letting the list churn is the most expensive line item that never appears on the P&L.
Why push notifications fit betting sites better than email
Betting is an intent-window business. A pre-match line matters for about an hour. A halftime price matters for fifteen minutes. A cash-out decision matters for seconds. Email lands whenever the player next opens their inbox — tomorrow, maybe. Web push lands on the device in seconds, whether or not your site is open, with no app to install and no app store in the way.
The audience behaves accordingly. Betting and gaming sites on PushEngage have sent over 3.5 billion notifications, and the sharpest pattern in that data is event responsiveness: on a single World Cup group-stage day, betting sites on PushEngage saw ~4.6× baseline daily signups. Big fixtures move this audience. Operators who capture that spike into segmented lists keep it; operators who blast it churn it.
If you run a native app, app push works from the same segments and workflows. This playbook focuses on web push, the surface every operator already has.
The 2026 crackdown repriced push notifications for betting sites
Between late 2024 and early 2026, Google shipped a coordinated set of changes that reprice push notifications for betting sites and everyone else. None ban gambling content. All punish high-volume, low-engagement sending — the pattern most operators run today.
| Change | 機能 | Live since |
|---|---|---|
| Chrome Push API rate limiting | Daily origin scoring on push volume vs. engaged time, prompt frequency, and engagement. “Disruptive” origins throttled to no less than 1,000 pushes/minute (excess gets HTTP 429); penalties run 1, 7, then 14 days, resetting after 42 clean days. | January 2026 (announced Jan 6, 2026) |
| Automatic permission revocation | Chrome removes notification permission from sites with very low engagement and high volume. Installed PWAs exempt. | Announced October 10, 2025 |
| Safety Check + one-tap unsubscribe | Background revocation for unused sites; an Unsubscribe button in the Android notification drawer (~30% volume drop on supported Pixels). | September 2024 |
| On-device ML spam warnings | Chrome on Android flags aggressive prize-and-urgency copy, replacing it with a warning plus Unsubscribe. | May 8, 2025 |
| Android 16 notification cooldown | Bursts from one source are progressively quieted and grouped for up to a minute. On by default. | June 10, 2025 |
Run the math on the throttle alone. A “disruptive” origin capped at 1,000 pushes per minute needs more than eight hours to deliver a 500,000-subscriber blast. If that was your kickoff alert, it arrives after full time. Throttling does not degrade the event-driven use case — it deletes it. Chrome’s scoring mechanics get a full treatment in our deep dive on triggered push notifications; the primary sources are Google’s posts on web push rate limits and automatic permission revocation.
What the new rules mean for gambling push notifications
Google’s framing is blunt: less than 1% of all notifications receive any interaction. Gambling push notifications sit disproportionately in that ignored majority, because the modal pattern in this vertical is several daily broadcasts to a mostly dormant list — a profile that now accumulates every penalty in the table at once.
The pattern extends beyond Chrome. Google’s RCS Business Messaging added reputation-based traffic tiers in January 2026, and Apple gates the channel differently: web push on iOS works only for sites added to the Home Screen (since iOS 16.4, March 2023). Engagement-scored sender reputation is now the rule on every major messaging surface.
The flip side matters just as much: gambling push notifications sent to engaged segments at relevant moments are exactly what the scoring rewards. The crackdown is not a tax on the channel — it is a transfer from blast senders to targeted senders.
Opt-in strategy: grow your push notification opt-in rate without burning permissions
The browser permission is close to a one-shot instrument: a visitor who clicks Block on the native dialog is, for practical purposes, gone for good. And because prompt frequency relative to time-on-site is one of Chrome’s scored signals, careless prompting damages your origin, not just your conversion rate.
Never prompt on landing
Firing the native prompt on arrival is the default failure mode: zero context, single-digit conversion, and every Block a permanently lost subscriber. Wait for demonstrated intent — 15–30 seconds on page, meaningful scroll depth, or a completed action such as a registration or a placed bet.
Use a two-step opt-in
Show a branded soft ask before the native dialog: “Want kickoff alerts and your weekly bonus notifications?” with Yes and No buttons. Only yes-clickers see the browser dialog, so they convert at a much higher rate — and decliners keep their permission state intact and can be asked again later. The soft ask is also where you set expectations honestly: match alerts, bonuses, results, no spam. Subscribers who knew what they signed up for interact more — and interaction is the currency your origin is scored in.
Ask in context, on intent
One site-wide prompt underperforms a network of targeted ones. Sportsbook pages ask about match and odds alerts, slots pages about new-game drops and jackpots, lottery pages about draw results. The strongest trigger is a click: a “Notify me at kickoff” button next to a fixture produces a subscriber who told you exactly what they want — segmented from the moment of capture.
Treat your push notification opt-in rate as the most testable number in the program: timing, copy, and placement are all A/B-testable, and the tactics in our guide to raising your opt-in rate apply directly. A push notification opt-in rate built on honest expectations is pre-paid deliverability — those subscribers keep clicking.
Segments and triggers: how the best iGaming push notifications get sent
Here is the number that should reorganize your roadmap: the median betting-site sender sees ~2.1% CTR on viewed notifications; the top decile does 6.9% — roughly triple. Same channel, same kind of players. The top decile is not writing better headlines. It is sending fewer, more targeted messages — the exact behavior the 2026 scoring rewards.
Getting there takes a model shaped like a betting business, not a newsletter. The dimensions that matter for iGaming push notifications: vertical (sportsbook, casino, live casino, lottery), sport and team followed, bet-type preference, deposit tier, session recency, VIP tier, and game preference. The rule of thumb: to send to it, make it a segment; to branch or personalize on it, make it an attribute. Push notification segmentation is now a deliverability requirement in every vertical — betting simply has more intent signals to build with. Start with six segments, not sixty.
The best iGaming push notifications are not scheduled at all — they are triggered by what a player just did. Two workflows deserve to be built first, in a visual workflow builder rather than as engineering projects:
- First-deposit conversion. The registration-to-deposit gap is where paid acquisition dies. Three patient touches over five days — bonus presented as available, never expiring — exiting the moment a deposit lands.
- Continue where you left off. Betting’s cart abandonment: a bet slip built but not placed, a cashier opened but not completed. Wait 45 minutes, then send one deep-linked resume push. On the abandoned-deposit branch, one neutral nudge with no bonus and no countdown — an abandoned deposit is sometimes a decision, and the decision is respected.
These two workflows are also crackdown insurance: they fire only at players active minutes or days ago, so every send strengthens the engagement profile that protects your origin. There is far more underneath this section — match-day sequencing for sportsbooks, the casino week and its bonus rhythms, the full player segmentation model. Each runs deeper than a pillar post can go; treat this as the map, not the territory.
Message hygiene and responsible gambling messaging
Hygiene used to be etiquette. Since January 2026 it is infrastructure protection: Chrome scores your origin, so one bad campaign pattern degrades everything you send. Four disciplines keep the score healthy:
- Cap frequency deliberately. A per-subscriber ceiling per day and week, lower for cooler segments — and space sends to the same subscriber by minutes, not seconds, or Android 16’s cooldown mutes the third one.
- Enforce quiet hours in the platform. A do-not-disturb window per workflow, resolved in each subscriber’s timezone: reschedule offers that keep, skip alerts that expire.
- Prune dormant subscribers on a ladder. Downshift them out of broadcasts, run one short re-engagement sequence, then suppress non-responders. They were about to be auto-revoked invisibly anyway; you gain a cleaner origin score and, because pricing is based on active subscribers, a bill that reflects your real list.
- Write copy the ML filter ignores. A specific fixture, a specific amount, a specific expiry. The all-caps prize-and-urgency register is what Chrome’s on-device model flags — and most tactics that reduce your unsubscribe rate also keep the filter quiet.
Responsible gambling messaging belongs in the same breath: it is the same discipline pointed at the player instead of the browser. Treat it as a commercial trust practice, not a legal checkbox (and nothing here is legal advice). Four commitments, all buildable today:
- Self-exclusion is hard suppression, fast. An API call moves a self-excluded player into a suppression segment within 48 hours at the outside — excluded from every audience, with exit criteria that cancel any workflow they were in. Never send a “your exclusion has ended” win-back; re-entry must be the player’s own act.
- No bonus pushes at loss-chasing signals. Feed your platform’s chasing flag in as an attribute and gate every bonus workflow on it. A scheduled weekly cashback is a rhythm; a cashback push minutes after a losing streak is something else.
- No urgency framing on deposit prompts. Countdowns belong on things that genuinely expire — a kickoff, a draw close, a freespin expiry — never on depositing money. Manufactured deposit pressure is also prime ML-flag territory.
- Per-user quiet hours and instant opt-out. Defaults protect sleep; letting players tighten them protects the relationship.
Operators who hold this line get something rare in the vertical: a reason for players to leave notifications on. Responsible gambling messaging, done as design rather than disclaimer, is a differentiator — and every commitment above also feeds the engagement profile the 2026 rules reward.
The 90-day roadmap: crawl, walk, run
Ninety days moves an operator from broadcast-only to the sending profile that both the browser and the finance team reward.
| Phase | 日 | What you build | 終了基準 |
|---|---|---|---|
| Crawl | 1–30 | Two-step, intent-triggered opt-ins per page type. Six starter segments (vertical, big teams, session recency, VIP). Every broadcast moves to segment targeting. Weekly offer anchors. Pruning begins. | No send goes to the full list; CTR-on-view reaches the 2.1% median. |
| Walk | 31–60 | Three triggered workflows: first-deposit conversion, a settlement or weekly-cashback rhythm, one deadline or event sequence. Platform events wired via API. Goal tracking on. | First workflow-attributed revenue number in a weekly report. |
| Run | 61–90 | Lifecycle coverage per vertical. A/B split paths on the two highest-volume sends. Responsible-gambling gates in every bonus automation. Season overlay: derby weeks, tournaments, year-end draws. | Most push-attributed revenue comes from triggered sends, not broadcasts. |
On plan fit: the workflow builder exists on every plan, including Free. Wait-and-decision sequences need Business or above, split-path A/B testing and goal nodes need Premium, and custom-event triggers and webhooks need Growth. An operator running the full roadmap is a Growth-tier profile.
One architectural question sits outside this roadmap: operators running a portfolio of brands or regional domains (.com, .ca, .mx) need subscriber continuity across those properties and through domain migrations. Subscriptions anchor to the origin that captured them, so where you capture is a strategic decision — a topic that deserves its own post.
Push notifications for betting sites stopped being a megaphone in 2026. Run as a retention engine — intent-based opt-in, a player-shaped segmentation model, triggered workflows, hygiene, and responsible-gambling gates — the channel compounds the asset you already paid to acquire, and betting site retention stops being the number nobody reports.
PushEngage runs this entire program from one dashboard: web push notifications with the segmentation, workflows, quiet hours, and suppression controls described above. You can prove the channel on the free plan, and pricing scales with active subscribers — which your pruning discipline keeps honest. Every paid plan carries a 14-day money-back guarantee.
