A sportsbook’s push calendar is not a marketing calendar. It is a fixture list. Sports betting push notifications succeed when every send is planned against the match itself — build-up, kickoff, the ninety minutes, and settlement — and fail when a big fixture arrives and the team improvises.
The stakes are measurable: on a single World Cup group-stage day, betting sites on PushEngage saw ~4.6× baseline daily signups. Nobody ran a special opt-in campaign that day. The fixtures did the work.
This post lays out every send from T−7 to the Monday after — segment, timing, and example copy — plus the 2026 spacing rules and the responsible-gambling lines the sequence never crosses.
Match days are acquisition, retention, and reactivation at once
A derby weekend is three campaigns running at once, and treating it as one blast wastes all three:
- Acquisition. Casual fans read previews and stats pages all week. The 4.6× signup day happened on ordinary opt-in prompts meeting extraordinary traffic.
- Retention. Active bettors want early odds, team news, boosts, and settlement confirmations.
- Reactivation. A dormant subscriber ignores a generic bonus push but opens one about a fixture they care about — the best win-back hook of the quarter.
All three run through one channel in one week, to overlapping segments — improvise and you send late, in bursts, into the throttles covered below; run a sequence and you own the week. Sportsbook push notifications map to fixtures, not to a content plan. The channel foundations are in our retention playbook for betting sites; this post is its match-day chapter.
The sports betting push notifications timeline, T−7 to post-match
| Phase | Send | Kitle | PushEngage feature |
|---|---|---|---|
| T−7 to T−3 | Fixture announcement | Team-tagged segments | Scheduled send to segment |
| T−7 to T−3 | Early-odds alert | High-value tier | Audience-triggered workflow (deposit_tier) |
| T−7 to T−3 | Welcome-offer capture | New visitors on content pages | Opt-in prompts + welcome workflow |
| T−48h | Match briefing + boost preview | Both team segments | Scheduled send |
| T−48h | Dormant reactivation | 30 / 60 / 90-day inactive tiers | Audience-triggered workflows |
| T−24h | Lineup-news alert | Team segments | Scheduled send |
| T−24h | Bet-builder nudge | Multi-leg bettors | Segment send |
| T−60m | Kickoff + odds boost | Bet-placed OR team followers | Workflow with decision node |
| T−15m | Last call / in-play preview | Live-bettor flag | Segment send |
| In-play | Halftime odds refresh | Match followers | Scheduled send at the interval |
| In-play | Key-moment triggers | Live bettors | Custom-event workflow (Growth plans and above) |
| Post-match | Bet settled (win / loss paths) | Bettors on the fixture | Event-triggered workflow, decision node |
| T+1 | Weekly cashback + next-fixture follow | Net losers / engaged on match day | Audience workflow (Monday) + segment send |
Every send below assumes a Sunday-evening derby; scale to the fixture — full T−7 build-up for derbies and cup nights, compressed T−48h for a regular round. Example copy below fits platform limits: titles ≤50 characters, bodies ≤100.
Fixture week: build the audience before the market moves
T−7 to T−3: announcement, early odds, and opt-in capture
Fixture announcement (“Derby Sunday, 19:00 — early markets are open”) goes to both team-tagged segments in the evening window, with timezone delivery so subscribers abroad get it in their evening, not yours.
Early-odds alert goes to your high-value tier only, filtered on a deposit_tier attribute at or above your VIP threshold. It rewards your best players with first look (“lock your price before the market moves”); sending it list-wide devalues it and burns frequency budget.
Opt-in capture on content pages. Big-fixture week is when casual fans read previews and stats — run your opt-in prompts on those pages, and put the welcome offer in a new subscriber’s first push, once, at signup. Never re-push no-deposit offers to existing subscribers.
T−48h: the briefing, the boost preview, and the reactivation wave
The match briefing is a content push to both team segments — head-to-head record, form, injuries. Content sends earn the promotional sends: they keep click-through healthy, which keeps sender reputation healthy.
The boost preview announces that enhanced odds are coming. Odds boost notifications perform best when the audience expects them; the preview is a second impression for free.
Dormant reactivation runs three tiers off a last_bet_date attribute — 30, 60, and 90 days inactive — each as its own audience-triggered workflow, paired with your standing weekend deposit offer. Reactivation copy states the offer and stops: no countdown language, no “last chance” framing on a deposit prompt. And self-excluded or timed-out players are excluded from every reactivation audience, always.
Title: The derby is back. So is your bonus Body: Your weekend deposit bonus is ready. Derby markets are open when you are.
T−24h: lineup news and the bet-builder nudge
Lineup news is one of the highest-CTR sends of the week; bettors build slips around team news.
Title: Team news: lineups expected at 18:00 Body: Predicted XIs and the late fitness calls — read before you build your slip.
The bet-builder nudge follows an hour later, only to subscribers whose history shows multi-leg slips (a bet_type attribute set through the API).
Match day notifications: kickoff to full time
Match day notifications compress the discipline into a few hours: right segment, right minute, enough spacing that the platforms deliver all of them.
T−60: odds boost notifications and the kickoff send
Odds boost notifications land hardest an hour out, to subscribers with a bet on the fixture or followers of either team — one workflow, a decision node, different copy for each group. Bettors get “your match starts in an hour”; followers get the boost.
Title: Kickoff in one hour Body: The derby starts at 19:00. Boosted odds are live for the next 60 minutes.
T−15: the last call
The last call goes to the live-bettor flag only, teeing up the mode those subscribers actually bet in: lineups confirmed, in-play markets open at kickoff. It lands 45 minutes after the kickoff send by design — the spacing rules below explain why.
In-play betting notifications: halftime, key moments, cash-out
The simplest in-play betting notifications need no integration: a halftime odds refresh scheduled into the interval for match followers, resurfacing next-goal and comeback markets.
Key-moment triggers — a goal, a red card, a penalty — are the highest-engagement in-play betting notifications in the vertical, and the one with a real integration requirement. PushEngage fires them from a custom-event workflow, but your odds feed or trading platform has to emit the event through the PushEngage API; custom-event and webhook actions are available on Growth plans and above. Without a feed integration, the halftime refresh still delivers most of the in-play value.
Title: RED CARD — down to 10 men Body: The market is moving. Live odds updated for the final 30 minutes.
Cash-out reminders use the same mechanism — a bet-state event from your platform, a nudge to the open-bet holder.
Post-match and Monday: settlement, results, and the loss-path rule
The win path is triggered by a settlement event from your platform, routed through a decision node on the outcome: winnings settled to your balance, plus the next fixture to follow.
The loss path gets a settlement confirmation and nothing else. No same-night bonus push to losers. A deposit offer minutes after a lost bet is loss-chasing bait — the pattern regulators worldwide are moving against and the one Chrome’s on-device spam models flag. The path ends with the settlement notice; a wait node holds anything promotional until the next day. This is a hard rule, not a tone preference.
The full-time result goes to team followers who didn’t bet — a retention send disguised as a score alert; it keeps casual followers clicking and protects engagement.
Monday closes the loop. The weekly cashback send goes to weekend net losers (a net_result_week attribute your platform updates), scheduled mid-morning — a full sleep cycle after the final whistle. A next-fixture follow goes to everyone who engaged on match day, feeding straight into T−7 of the next sequence.
Push notification timing under the 2026 platform rules
Match days are when operators burst-send, and the 2026 platform environment punishes bursts. Three push notification timing rules protect the sequence.
Never send twice within about 15 minutes to the same subscriber. Android 16’s notification cooldown (shipped June 2025, on by default) progressively quiets back-to-back notifications from one source, collapsing them into a single minimized banner. Send a boost, a reminder, and an odds update inside a few minutes and the third is effectively invisible. The sequence above never puts two sends to one segment closer than 45 minutes; keep that spacing when you adapt it.
Stagger the kickoff send by segment priority. Since January 2026, Chrome scores every sending origin daily and throttles origins it classes as disruptive to roughly 1,000 push messages per minute. At that rate a 500,000-subscriber blast takes over eight hours — a dead list at kickoff. Send high-value bettors first, then bet-placed subscribers, then team followers, in waves a few minutes apart; PushEngage’s audience-based workflows stagger execution automatically within each wave, so your job is ordering the waves. For app push, FCM’s per-device quotas impose their own ceiling.
Quiet hours everywhere off-match. Every workflow carries a quiet-hours window, roughly midnight to 09:00 subscriber-local, set to reschedule rather than skip. Match day notifications timed to the fixture are exempt by nature; reactivation, cashback, and content sends are not. A late-night deposit prompt is both a churn driver and a responsible-gambling failure. Off-week, push notification timing follows the general best time to send push notifications guidance — it only bends to the fixture when there is one.
The segment prep checklist: build these before T−7
The sequence only works if the segments exist before the week starts. One prep session per season, plus a weekly data sync from your platform:
- Team tags — a segment per followed club, captured at opt-in via a team picker or set from betting history.
- Bet-recency tiers — a
last_bet_dateattribute segmented at 30 / 60 / 90 days for the reactivation ladder. - Deposit tiers — a
deposit_tierattribute for the high-value early-odds track. - Live-bettor flag — set when a subscriber places an in-play bet; gates the T−15 and in-play sends.
- Multi-leg flag — gates the bet-builder nudge.
- Self-exclusion suppression, confirmed rather than assumed. Every self-excluded or timed-out player must be excluded from every audience in this sequence, including all-subscriber sends. Verify the sync actually ran this week. A time-out must never trigger a re-engagement push, and an expired exclusion must never trigger an automatic win-back.
Every attribute is set through the PushEngage API or SDK from player data you already hold — no manual list management on match week. Segmentation is also your throttling defense: sends that fire to recently active players keep every signal Chrome measures healthy, which is why segmentation is now a deliverability requirement. If you operate several brands or regional domains, the same segments span one subscriber list across multiple domains.
Measuring sportsbook push notifications: what a good match day looks like
Judge the sequence on four numbers:
- CTR by phase. The median betting-site sender sees ~2.1% CTR on viewed notifications; the top decile does 6.9% — roughly triple. Well-run sportsbook push notifications slope upward through the sequence: announcements lowest, kickoff sends higher, key-moment and settlement sends highest. A T−60 send performing below your weekly content sends means the segment is wrong, not the fixture.
- Opt-in volume on match day. Big-fixture days should visibly bend your signup curve. If a derby day looks like a Tuesday, your opt-in prompts aren’t on the pages match traffic lands on.
- Post-fixture cohort retention. Tag every subscriber acquired on a big match day and track their 30-day activity. Betting lists churn brutally — in one 90-day window, unsubscribes erased roughly 91% of new subscriber acquisition across the segment. The cohort still active at T+30 is the true yield.
- Workflow analytics. Per-node drop-off shows which step loses people: the send, the timing, or the offer.
Then test, one fixture cycle per experiment: odds in the title versus a curiosity title, emoji versus none (on content sends, never deposit offers), and T−60 versus T−30 kickoff timing, split by segment so the fixture doesn’t confound the result. Split-path A/B testing runs inside PushEngage workflows on Premium plans and above; the method is covered in our push notification A/B testing best practices.
Everything above is standard PushEngage capability: segments and attributes, timezone-aware scheduling, workflows with wait, decision, and split-path nodes, quiet hours, and goal tracking that attributes bet placement to the send. Sports betting push notifications reward the operator who plans the week before the market opens. To run the sequence against your own fixture list, start with the web push notification platform and pick a plan on PushEngage pricing — every paid plan carries a 14-day money-back guarantee.
