The challenge

A new product on the same wallet, no separate UA.

The operator already had a casino brand with active players. Adding prediction markets via a separate microsite would have meant rebuilding identity, payment and KYC — and re-acquiring players the operator already paid for. The bet was that prediction markets would only work commercially if they shared the same wallet, the same KYC and the same player view as casino.

What we did

Polybetting embedded; casino as the cross-sell target.

Polybetting deployed inside the existing casino product, sharing wallet and KYC. Prediction-market players were already KYC'd through casino; cross-sell was a single tap, no re-deposit, no re-verification. We routed liquidity through Polymarket as the first source. Kalshi, Manifold and on-chain venues sit on the integration roadmap and plug in without operator-side work.

CROSS-SELL FUNNEL · WEEK ONE · SAME WALLET POLYBETTING All players who placed a prediction-market bet 100% cohort baseline SAME WALLET · SAME KYC Single-tap to casino No re-KYC · no re-deposit CASINO Placed at least one casino bet in week 1 41% of Polybetting cohort +28% LTV on the cross-sell cohort vs casino-only baseline
Same-wallet cross-sell from Polybetting into casino. 41% of the prediction-market cohort placed a casino bet in week one.
Results

By the numbers.

  • 41% of Polybetting players placed at least one casino bet in week one
  • Player LTV +28% on the cross-sell cohort vs casino-only baseline
  • Same KYC, same wallet, no separate compliance flow
  • Polymarket as first source — Kalshi and on-chain on the roadmap
Polybetting paid for itself in casino in the first thirty days. That was the test.
Anonymous (operator-confidential) CCO · LATAM Tier-2 operator
Share LinkedIn Telegram Email