Geo-Fenced Jackpots Shrink Pool Visibility 29% in 500 Sessions

A 500-session test of jackpot lobby visibility across three geo-fenced operator groups found that players saw 29% fewer distinct progressive jackpot pools than players on the same software stack with unrestricted pool access. The gap widened with session length: by minute 40, restricted players had encountered a median of 11 pools against 17 for unrestricted controls. The finding matters less for what it says about any single operator than for what it implies about how jackpot liquidity is measured, marketed, and audited.

Method and sample

The test ran between 14 January and 6 March 2025 across 500 logged sessions split into two arms. The control arm (250 sessions) used accounts registered in jurisdictions with no pool-level restrictions; the treatment arm (250 sessions) used accounts subject to geo-fencing rules that limit which progressive pools a player can see and contribute to. Sessions were capped at 45 minutes, matched by device class and time of day, and driven by a scripted navigation path that visited the lobby, the slots category, and the jackpot filter in a fixed order before free browsing.

Three operator groups were represented, each running the same aggregation provider but with different jurisdictional configurations. That matters: the treatment effect is not a software artifact. The same pool inventory existed on the back end in both arms. What differed was the client-side filter applied before the lobby rendered.

Visibility was measured as the count of distinct pool identifiers surfaced to the player, not the count of contributing games. A pool visible through a single game counted once. Repeat exposures across games were deduplicated. Sessions that hit a login or verification wall before the lobby loaded were discarded and replaced; 41 sessions were discarded on that basis, 23 in the treatment arm.

What "visibility" excludes

The metric deliberately excludes pools a player could reach only through direct URL or deep link. In practice, almost no one navigates that way, and the treatment arm's deep links resolved to restricted pools in 94% of attempts anyway. The number that matters to a player is what the lobby shows, because that is what shapes which games get opened.

Where the 29% gap comes from

The headline figure is a mean across all 500 sessions: 11.4 distinct pools per restricted session against 16.1 per unrestricted session, a difference of 4.7 pools or 29.2%. The distribution is more informative than the mean.

Two rows deserve attention. First, the zero-pool sessions: 18 restricted sessions never surfaced a single pool that spanned more than one operator's network. Those players were not told why. The lobby simply presented a smaller inventory, indistinguishable from an operator that runs no network progressives at all.

Second, the time-to-first-view gap. Restricted players took 57% longer to encounter their first pool, which compounds through a session as browsing momentum carries players toward whatever the lobby surfaces early.

The gap is not uniform across pool types. Local pools operated by a single brand showed a 4% difference between arms, within noise. The 29% figure is driven almost entirely by multi-jurisdiction network pools, where the restricted arm saw roughly half the pool count of the control arm (5.2 against 10.6). Operators whose jackpot inventory is mostly local will find the headline number overstates their exposure.

Why operators fence pools at all

Geo-fencing of progressive pools is usually a licensing requirement rather than a commercial choice. Pool participation is a form of shared liquidity, and shared liquidity across borders triggers regulatory questions about which regulator supervises the pooled funds, how the reserve is held, and whether players in market A are effectively funding a prize that a player in market B might win. Several jurisdictions resolve this by requiring that their licensees' players contribute only to pools ring-fenced within the market, or by prohibiting cross-border contribution outright.

The result is a structural tension. Aggregation providers build network pools because size drives prize growth, and prize growth drives player interest. Regulators fence pools because pooled funds are hard to supervise. Players in fenced markets get a smaller, slower-growing jackpot inventory and, as the data here shows, a materially thinner lobby.

The marketing problem

Operators rarely disclose the fence. A player in a restricted market sees a jackpot lobby that looks complete. The 18 zero-pool sessions in the sample suggest some players see no network pools at all without any indication that a larger pool exists elsewhere. Whether that constitutes a misleading presentation is a question for regulators, not for this study, but the asymmetry is real and it is not disclosed at the point of play.

What the 29% does and does not establish

The sample is 500 sessions across three operator groups on one aggregation provider. It is not a census, and the 29% figure should not be generalized to markets not represented. A jurisdiction with a narrower fence, or one that permits contribution but restricts prize eligibility, would produce a different gap.

The measure is also visibility, not participation. A player who sees fewer pools may concentrate play on the pools they can see, and the effect on total jackpot contribution per player could run in either direction. This study did not track stake allocation, so it cannot say whether restricted players contribute more or less per visible pool. That is the obvious next question, and it is the one that determines whether fencing shrinks the prize pool or merely redistributes attention within it.

There is a measurement problem underneath all of this. Operators report jackpot contribution and prize data to regulators, and aggregation providers report pool sizes to operators. Neither party routinely reports what an individual player could see. Without that, the visibility gap documented here is invisible in every compliance return filed in the markets studied. A player who never sees a pool cannot complain about its absence, and a regulator reviewing contribution figures has no reason to ask.

The open question is whether visibility should be a disclosed metric at all. If a fenced market produces a lobby with half the network pool count of an unfenced one, players comparing screenshots across markets will notice eventually. The more durable fix is probably not to unfence the pools but to label them: a lobby that says plainly which pools are local and which are network-wide would close most of the information gap without touching the licensing architecture. Whether any operator volunteers that label before a regulator requires it is a different study.