News

The compliance stack for US prediction-market affiliates

Geo-gating, age verification, creative approval, and state-by-state ad rules. The under-discussed operational layer that determines whether an affiliate property can scale.

Overhead view of a tidy desk with stacked papers, a closed laptop, glasses and three coloured folders arranged like a staircase.
← News

Note, November 15, 2026: this analysis was written in May 2026. Figures in it are estimates that we have not traced to a primary source, and some details have changed since. For current rules and status, see our regulation news and state table.

TL;DR:

Running a US prediction-market affiliate at scale requires a small but non-trivial compliance stack: geo-IP gating, age verification on outbound clicks, partner-approved creative, per-state ad-policy mapping, and a documented audit trail. None of it is technically complex; all of it is operationally necessary. The properties that ignore this layer either stay small or get shut down loudly.

Key takeaways
  • Geo-IP gating at the outbound-click level (not the page level) is the minimum standard.
  • Age verification on the affiliate side, even where not strictly required, reduces partner-side disputes.
  • Every creative shown to users must be on the venue's approved list. No exceptions.
  • State-by-state ad rules diverge meaningfully; a single creative cannot run everywhere.
  • Compliance evidence (logs, screenshots, version history) is what protects both the affiliate and the partner in an enforcement action.

What the compliance stack actually has to do

A US prediction-market affiliate operating at scale needs to answer five questions in real time, for every user, on every page.

  1. Is this user in a jurisdiction where the recommended venue is currently accessible?
  2. Is this user plausibly of legal age?
  3. Is the creative shown to this user one that the venue has approved?
  4. Does the surrounding content comply with the relevant state's ad rules?
  5. Can we, if asked, reconstruct exactly what this user saw on what date?

Each of these maps to a specific technical or operational requirement. None of it is exotic. All of it must work.

Geo-IP gating at the click level

Page-level geo-gating, hiding entire pages from users in restricted states, is the easy and visible approach. It is also bad SEO and bad UX, because users in restricted states still have legitimate informational interest in the category.

This requires:

  • A reliable IP-to-state mapping service (MaxMind, IPinfo, or similar) refreshed weekly.
  • Edge-cached geo headers so the gating decision happens before page render, not after.
  • A documented fallback for VPN traffic: typically, default to the most restrictive interpretation.

Age verification on outbound clicks

Age limits differ by state and by exchange. Many states set 21 for sports betting, and each exchange sets its own minimum age in its rules, often 18. Check each exchange's current terms. The venue is technically responsible for age verification at account creation. In practice, affiliates that add a lightweight age-confirmation interstitial on outbound clicks materially reduce partner-side disputes and underage-account remediation costs.

The interstitial does not have to be heavy. A single-click confirmation, logged with timestamp and IP, is enough to demonstrate intent.

Creative approval, without exceptions

Every banner, button, callout, comparison table, and screenshot that depicts a partner platform must be on that partner's approved-creative list. This is non-negotiable for two reasons:

  • Most partner contracts explicitly require it, with termination clauses for breach.
  • Many state advertising rules require advertised claims to match what the platform actually offers.

The operational implication: a process. New creatives go through partner review before they go live. Updates to existing creatives reset the approval. A versioned creative library tied to page-render logs is the audit trail.

Per-state ad-policy mapping

State ad rules for gambling and gambling-adjacent products diverge across at least eight dimensions: minimum-age disclosures, responsible-gaming language, geographic-restriction notices, prohibited-claims lists, problem-gambling hotline placements, social-media policies, college-athlete depictions, and influencer-disclosure rules.

A single creative cannot satisfy all 50 state regimes simultaneously. The practical approach is a state-policy matrix that maps each creative to the states in which it is compliant, and serves the appropriate variant based on the detected geo.

This is operational work, not legal work. The legal work is done once, per state, by counsel. The serving logic is done in code.

The audit trail

When a state attorney general, a partner platform's compliance team, or a class-action plaintiff asks 'what did this user see on this date,' the property must be able to answer that question precisely.

The minimum logging stack:

  • Page-render logs with user-agent, IP-derived state, and rendered creative IDs.
  • Outbound-click logs with timestamp, source page, destination, and any interstitial interaction.
  • Versioned content history with timestamps for every editorial change.
  • A separate audit log of partner-creative-approval state changes.

Retention: minimum 24 months for advertising claims, longer where state rules require.

What this costs

A two-person property can run this stack with off-the-shelf tooling: an edge geo service, an analytics layer with custom event logging, a CMS with versioned content history, and a spreadsheet-based creative-approval workflow. The marginal cost is engineering hours, not licensing fees.

The properties that skip this layer save those hours. They also do not scale beyond the point where any partner does a routine compliance audit.

For the per-state legality status that feeds this stack, see our legality tracker.

#operator

#ops

Related