Email deliverability for iGaming and betting operators

iGaming email faces two compounding problems: filters treat gambling as a high-risk content category, and the industry's standard acquisition channel — affiliates — produces the worst lists in email. The operators who reach the inbox are the ones who isolate account-critical mail from promotional mail, refuse affiliate-supplied address lists, and run per-market sending domains. Nothing in the message copy fixes a programme that gets those three wrong.

Why gambling mail is treated differently

• Category classification. Mailbox providers group gambling with other regulated and high-complaint verticals. The same message content from a gambling domain and a retail domain does not score identically.
• Complaint rates are structurally high. Bonus-driven signups produce users who registered for one offer and do not want a daily email. Complaints above Google's published 0.3% threshold put the whole sending domain at risk.
• The acquisition channel is adversarial. Affiliate traffic is paid per registration, which creates pressure to supply addresses that were never consented — including purchased and scraped data, and the spam traps that come with it.
• Age and geography restrictions mean a non-trivial share of your list should never have been mailable in the first place.
• Brand-spoofing is common. Fake casino promotions impersonating real operators make providers more suspicious of the whole category and make DMARC enforcement non-optional.

Separate the streams, or nothing else works

This is the single highest-value decision, and it has to be made before volume grows.

Reputation is evaluated per sending domain, so a subdomain does not inherit the root's standing — each needs warming on its own. Accept that cost; the alternative is a bonus campaign that delays a withdrawal confirmation.

Compliance that is also deliverability

Gambling marketing rules vary by licence, and the specifics change, so verify against your regulator's current guidance. The constants across jurisdictions:

• Consent must be real and recorded. Timestamp, source, the consent text shown, and which brand it was given to. Consent to one brand in a group is not consent for the others.
• Self-exclusion must suppress marketing. In Great Britain, self-exclusion through GAMSTOP must be honoured by licensed operators, and operator-level exclusions apply alongside it. Treat exclusion registers and self-exclusion flags as a hard suppression layer checked at send time, not as a list filter applied at build time.
• Affiliates are your liability. Marketing sent on your behalf is attributed to you — by regulators and by mailbox providers. Contractual language is not a control; auditing is.
• Required messaging. Age restrictions, licensing information and responsible-gambling signposting belong in the footer as live text, not inside an image.
• Bonus terms must be accurate in the email, not only on the landing page. A subject line that promises more than the terms deliver is both a regulatory and a complaint problem.

The sending setup

1. Authenticate every subdomain. SPF within the 10-lookup and 2-void-lookup limits, DKIM at the selector you publish, DMARC with rua monitored. Verify on a delivered message's Authentication-Results, not in a DNS checker.
2. Go to `p=reject` once reports are clean. Brand impersonation is an active problem in this vertical, and spoofed casino mail damages the reputation of your real mail.
3. Add `np=reject` for non-existent subdomains — free protection against spoofing of hostnames you never created.
4. Warm each new subdomain before it campaigns, and send account mail through it from day one because it has the best engagement of anything you send.
5. Keep tracking links on your own subdomain via CNAME. Public shorteners in gambling mail are a fast route to a URI blocklist.
6. Ramp volume gradually — no more than roughly 30–50% day over day while young — and treat 421/450 deferrals as an instruction to slow down.
7. Monitor per provider. Gmail, Microsoft and Yahoo behave differently, and a blended placement number hides the market where you are failing.

List practices that decide the outcome

• Never accept an address list from an affiliate. Accept registrations, which carry their own consent record, and nothing else.
• Double opt-in every non-registration source: pop-ups, competitions, sweepstakes.
• Sunset aggressively. Bonus hunters who registered once and never returned are the segment generating your complaints. One re-engagement attempt at six to twelve months, then suppress.
• Cap frequency centrally across promotional flows. A user who deposits during a tournament should not receive four promotions that week.
• Honour one-click unsubscribe properly: List-Unsubscribe plus List-Unsubscribe-Post, acted on within two days, no login, no preference-centre detour.
• Monitor complaint rate by acquisition source. One affiliate or one campaign type usually dominates, and you cannot see it in the aggregate.

What not to do

1. Do not send promotions and account mail from the same subdomain.
2. Do not mail an affiliate-supplied list, under any commercial pressure.
3. Do not put the offer, the age restriction or the responsible-gambling notice inside an image — Outlook on Windows blocks remote images by default.
4. Do not rotate through fresh domains to escape a reputation problem. New domains have no history, and the pattern itself is a signal.
5. Do not use public link shorteners.
6. Do not blast a tournament or jackpot announcement to the full list from a young domain.
7. Do not treat Promotions-tab placement at Gmail as a failure without measuring it separately from spam placement.

MailPilot handles warm-up and measurement for this architecture: warm-up over OAuth (Gmail, Outlook) or SMTP/IMAP including Amazon SES, SendGrid, Mailgun, Postmark and custom SMTP, SPF/DKIM/DMARC checks against delivered mail, daily per-mailbox reputation, and real inbox placement per provider from a seed-inbox network — reported per sending domain, so your account stream and your promotional stream are never judged by one number.