Email and Push Deliverability: Keeping Players Engaged Without Spam
You send one more promo. Then two. Then a late-night push. Results look fine for a week. After that, complaints spike, inbox rate drops, push tokens decay, and revenue slips. This is not a volume problem. It is a trust and timing problem. Deliverability is the skill to reach the right player, at the right time, with a message they asked for. This guide shows how to build that skill for email and push, without spam.
The three levers you can actually pull
Deliverability moves when you pull three levers. First, identity and setup: your domains, IPs, and keys must be clean and aligned. Second, signals: opens, clicks, replies, complaints, and opt-outs tell inboxes and devices if you add value. Third, pressure: how often you send and if the content fits the player’s moment. If any lever is off, the other two cannot save you.
Field notes: what inboxes and OS vendors look at
Email reality check
Gmail and Yahoo judge your reputation over time. They look at complaint rate, spam trap hits, bad bounces, and user actions like “Not spam.” Gmail asks bulk senders to meet stricter rules in 2024+. Read the current Gmail bulk sender requirements. Set up and monitor Google Postmaster Tools. For Yahoo guidance, use the Yahoo Sender Hub. These pages show you how they think and what they flag.
Push reality check
Push deliverability depends on valid device tokens, user settings, OS rules, and your send pattern. Spammy pushes lead users to block your app or turn off alerts. Night pings hurt trust fast. Design your push levels and quiet hours with care. On iOS, note the official Apple interruption levels. On Android, set proper notification channels so users can choose what they get.
Privacy and the law
You must give clear consent, a simple opt-out, and honest sender info. In the U.S., follow the CAN-SPAM Act guide. In the EU, review the GDPR essentials. In Canada, see the CASL rules. For iGaming, add age gates, self-exclusion checks, and quiet hours. Never wake a self-excluded player with a promo, by email or push. That is both a legal and brand risk.
Authentication: your foundation for email trust
Send from a domain you own. Align your envelope, header, and visible From. Set SPF, DKIM, and DMARC. Roll out BIMI later when your reputation is steady. Read the DMARC overview, the DKIM basics, and the SPF framework. For logos, see the BIMI group. These are not “nice to have.” They are a must for inbox placement.
Five dials teams over-rotate and break
1) Frequency that feels like a fire hose
“More” is not “better.” Cap sends per user per week. For active fans, 2–4 emails a week can work. For high-risk or cold users, 0–1 per week is safer. For push, daily is often too much unless the message is time-based and wanted. Always offer one-click opt-out in the header. Use one-click list-unsubscribe (RFC 8058) to lower friction and lower complaints.
2) Warm-up done in a rush
New domains and IPs need a gentle ramp. Start small with your most engaged users. Grow 20–30% per day if complaint rate stays below 0.2% and bounce stays low. Watch Postmaster for spam rate and IP/domain health. If you use AWS, follow SES IP warm-up as a baseline. Slow is fast here.
3) Content that misses the player’s moment
Match the message to the stage: KYC done, first deposit, cool-off, reactivation, VIP. During a pause or self-exclusion, stop promos. Send only service notes if needed. For push, split channels: promos, wins, account, and security. Let users mute promos but keep security alerts.
4) Cross-channel echo that feels like noise
Do not send a push that just repeats the email five minutes later. Choose a lead channel. If email goes first, delay push by hours, or skip it if the user opens the email. Use push for time-bound items: live events, expiring bonus, bet settled. Email can carry longer guides and safer upsell.
5) Measuring the wrong thing
Apple Mail hides opens for many users. See Apple Mail Privacy Protection. Do not chase open rate. Track complaints, clicks, revenue per send, and inbox health. Keep Gmail complaint rate under 0.3% at all times. Watch unsub trend by segment after each test.
Three short stories from the floor
Story 1: Promotions to Primary, then back again
We moved from flashy promo lines to simple subject lines with clear value. We cut emojis, trimmed images, and led with the key point. For a test group, Gmail placed more of our mail in Primary for a week. Then complaints rose when we doubled send count. Primary did not save us. Sanity in frequency did.
Story 2: Night push and token decay
We used to ping users at 1 a.m. local time for a live offer. Many blocked push next day. We set quiet hours from 22:00 to 08:00 local time, kept only “time-critical” alerts at high level, and bumped other promos to day slots. Push blocks dropped, CTR rose, and token loss slowed.
Story 3: Trust first, then lifetime value
Players want choice. We show how to change email and push settings in plain steps. On our independent review hub https://bets-ru.com/, we also tell readers how to opt out in one click and how to set quiet hours. It builds trust, so users stay longer. Consent is the start of LTV, not the end.
The Deliverability Control Board
Use this table as your cockpit. Pick owners. Set thresholds. Review it each week.
| Authentication (SPF/DKIM/DMARC/BIMI) | Proves sender and brand | Auth pass rate | >99% pass; DMARC p=none → quarantine → reject over weeks | DevOps + CRM | Postmaster, DNS, BIMI | Roll out BIMI only after stable reputation | |
| Dedicated sending domain | Isolates risk, builds clean history | Reputation trend | No spikes; steady volume | CRM | ESP, Postmaster | Split promo and transactional | |
| Complaint rate | Main negative signal | Spam complaints | <0.3% at Gmail; aim <0.1% | CRM | Postmaster | Use one-click unsubscribe | |
| Frequency capping | Email + Push | Prevents fatigue | Msgs per user per week | Active 2–4; risky 0–1 | CRM | ESP, push provider | Use an “offer budget” per user |
| Quiet hours | Push | Fewer blocks and opt-outs | Night send ratio | ~0% 22:00–08:00 local time | CRM | FCM/APNs | Allow “time-critical” cases only |
| Token hygiene | Push | Reduces dead sends | Invalid token rate | <3–5% | Mobile + CRM | Provider feedback | Cull stale tokens weekly |
| IP/Domain warm-up | Builds trust with inboxes | Daily volume step | +20–30%/day if clean | DevOps + CRM | ESP docs | Warm by segment and geo | |
| Sunset policy | Removes dead weight | Inactivity age | 60–90 days, then ramp down | CRM | ESP flows | Use re-permission before drop | |
| Content fit | Email + Push | Drives positive signals | Clicks per send | Stable or up after tests | CRM | A/B tools | Short, clear, honest |
| Blocklist status | Big hit on inbox rate | Listings present | 0 listings | DevOps | Spamhaus | Have an incident plan | |
| Fallback channel rules | Email + Push | Stops echo spam | Duplication rate | <10% same-message dupes | CRM | Journey builder | Skip push if email is opened |
| List-unsubscribe | Cuts complaints fast | Header detected | Present for all promos | DevOps + CRM | ESP headers | Use RFC 8058 one-click |
A 90‑day playbook (email + push)
Weeks 1–2: fix the base
- Set up SPF, DKIM, and DMARC with strict alignment. Start DMARC at p=none, then move to quarantine, then reject.
- Add BIMI only after you hold a good sender score for weeks.
- Check reverse DNS (PTR) and HELO name. Follow RFC 5321 (SMTP) basics.
- Add List-Unsubscribe and one-click. Make the footer honest and short.
- Sign up for feedback loops. Turn complaints into auto-suppression at once.
- Scan for blocklists daily. If hit, review Spamhaus docs and pause risky sends.
- Map all consent sources. Store proof. Make opt-out flow two taps max.
Weeks 3–6: warm up and shape the flow
- Warm domain and IP by engaged segments first. Use the 20–30%/day rule only if complaints stay low.
- Segment by stage: new, active, lapsing, paused, self-excluded, VIP. Set a cap for each.
- Create quiet hours for push per locale. Only allow “time-critical” with a higher level. For iOS tech, read Apple Push Notifications docs. For Android, set channels and TTL; see Firebase Cloud Messaging.
- For web push, plan permission prompts well and respect user choice. Review the Web Push API basics.
- Build a cross-channel rule: if email is opened, skip or delay the push. If push is tapped, reduce email volume for 24–48 hours.
- Define a sunset ladder: 30 days low activity → fewer promos; 60 days → re-permission; 90 days → pause until user opts back in.
Weeks 7–12: raise quality, then scale
- Create a content matrix: education, new features, promo with limits, safer play tips, service notes. Keep tone clear and fair.
- Run small A/B tests on subject lines and send times. Prefer clarity to tricks.
- Keep Gmail complaints <0.3% always. If a test crosses 0.2%, roll back fast.
- Track per-user “offer budget.” Do not send five pushes plus four emails in one day to one person. That is not “omnichannel.” That is noise.
- Report weekly on token health, quiet-hour breaks, and opt-out reasons. Fix root causes, not symptoms.
Monitoring that catches trouble early
Set alerts on complaint spikes, hard bounces, and blocklist hits. Watch Postmaster spam rate, domain and IP reputation, and delivery errors. Keep an eye on SMTP codes and retry logic per RFC 5321. For push, log provider errors, token invalid events, and drop reasons. Tie all alerts to a runbook with owners and time limits.
How to design messages people want
- Lead with value. “Your bet won,” “Odds boosted on your club,” “KYC approved.”
- Make it small. One idea per message. One clear action.
- Set the right level. On iOS, use proper interruption levels so you do not wake users for minor news.
- On Android, place each push in the right notification channel. Let users mute promo but keep security.
- Make opt-out easy and near the top. Use one-click where it fits.
- Add responsible play lines where needed. Respect time-outs and spend limits.
Common traps and how to dodge them
- Do not copy email content into push. Write for the lock screen.
- Do not send during big sports moments unless it adds real help.
- Do not chase opens. After MPP, they lie. Track clicks and net revenue per 1,000 sends.
- Do not ignore web push. If you use it, handle permissions with care and follow the Web Push API rules.
- Do not bury unsubscribe behind a login. It harms trust and raises spam hits.
Launch-day sanity checklist
- SPF, DKIM, DMARC aligned and passing.
- List-Unsubscribe present and working (one click where allowed).
- From name clear and stable. Reply-to monitored.
- Dedicated promo domain and stream set.
- Caps by segment set in both email and push.
- Quiet hours on. Time zones mapped.
- Self-excluded and paused users fully suppressed.
- Feedback loops on. Complaints auto-suppress.
- Blocklist watch on, incident plan ready.
- Push channels split: promos, account, security.
- Token cleanup job lives and runs.
- Legal footer short, honest, with support links.
FAQ
What is a good spam complaint rate for Gmail?
Aim under 0.3% per send and per day. Safer is under 0.1%. If you cross the line, cut volume, fix content and caps, then ramp back up.
How does Apple Mail Privacy Protection change open rates?
It inflates opens. Many opens are machine fetch. Do not use opens as a main KPI. Watch clicks, revenue per send, complaints, and inbox health in Postmaster.
What is a safe push frequency for casino apps?
Start with 1–3 per week for promos, plus all needed service alerts. Use quiet hours. If a user taps many pushes and keeps them on, you can raise it. If they mute or ignore, scale back.
Do I need a dedicated IP or domain?
Use a dedicated domain for promos to isolate risk. A dedicated IP helps at scale. Warm both with care. Watch complaint and bounce rates while you grow.
How do I add one-click unsubscribe?
Add the List-Unsubscribe header and the List-Unsubscribe-Post header per RFC 8058. Test with major inboxes. Keep a normal unsubscribe link in the footer too.
Regulatory note and player care
This guide gives general info, not legal advice. Check local laws and provider docs before you ship. Keep strong age gates. Honor time-outs and self-exclusion. Offer links to help and safer play. Your brand should be the calm voice, not the loud one.
A small, firm close
Deliverability is not a hack. It is proof, over time, that you respect your players. Set up auth. Watch signals. Cap with care. Pick the right channel. Give easy exits. If you do this well, you will send less noise, get more value, and keep trust for the long run.
Reference links used in this guide
- Gmail bulk sender requirements
- Google Postmaster Tools
- Yahoo Sender Hub
- Apple Mail Privacy Protection
- CAN-SPAM Act guide
- GDPR essentials
- CASL rules
- RFC 8058: one-click list-unsubscribe
- AWS SES IP warm-up
- DMARC overview
- DKIM basics
- SPF framework
- BIMI group
- Spamhaus
- RFC 5321 (SMTP)
- Apple notification interruption levels
- Android notification channels
- Apple Push Notifications docs
- Firebase Cloud Messaging
- MDN: Web Push API