Playbook — iGaming

iGaming Playbook: Run a KZ Slots Cap With or Without Telegram

iGaming is a deposit business: the click is cheap, the FTD is everything, and geo discipline is what keeps a KZ campaign from bleeding into traffic that will never fund an account. This playbook walks one real setup - the "iGaming — Slots KZ" campaign, geo KZ (Kazakhstan/CIS), pointed at the GombetCasino KZ offer ($180 CPA) - through both delivery paths Leadgram gives you: the Telegram bot funnel and the plain landing-plus-S2S route. Pick the one that matches where your creative sends people.

With Telegram — the bot funnel

When the ad drops users into a bot or channel, the conversation is the funnel. The tracking link on "iGaming — Slots KZ" carries the click id into Telegram on the /start deep link, so the first message the user sees is already attributed. From there the "iGaming — deposit funnel" Message Flow does the work: greet in the KZ user's language, qualify (age, deposit intent), hand off the GombetCasino KZ offer button, and fire the deposit and FTD conversion events back to Meta and your tracker the moment they land. Because every message is tied to the original click, a KZ deposit at 2 a.m. still rolls up to the exact creative that bought it - no attribution gap between the tap and the FTD.

From KZ ad click to FTD inside the deposit-funnel bot flow.

Without Telegram — landing + S2S

Not every casino offer runs through a bot. When the creative sends KZ traffic to a web preland instead, the path is server-to-server. The tracking link lands on Slots preland KZ (/slots-kz), which warms the visitor and forwards to the GombetCasino KZ offer with the click id in the URL. The "iGaming — geo-split" Click Flow runs at redirect time: KZ traffic goes to the live offer, everything else to a fallback, so you never pay to push Uzbek or Russian clicks into a KZ-only cap. Deposits and FTDs come back the S2S way - the casino posts each conversion to your events API with your x-api-key, tied to the click id it received - and Leadgram fires postbacks onward to Keitaro or RedTrack, so the FTD shows up wherever you optimize spend.

KZ preland to GombetCasino, geo-split at redirect, FTD via S2S.

From a media buyer's seat

The pain is always the same: you can see clicks and cost, but the FTD lives in the casino's dashboard, a day late and un-joinable to the creative that earned it. Setup is 20 minutes either way - one campaign, one offer, one flow or one geo-split - and after that the Reports page pivots KZ deposits by campaign, sub and day with EPC and ROI next to the funnel. That's the whole point: decide what to scale on the KZ cap and what to kill before the weekly numbers, not after. The two clips below are the same $180 CPA offer told from the buyer's chair - one team running it through Telegram, one through a preland.

A KZ slots buyer runs the offer as a bot deposit funnel.

The same offer, run as a preland with geo-split and S2S FTDs.

Keep the geo filter honest on both paths. A KZ-only CPA cap will reject deposits from neighbouring geos, so let the "iGaming — geo-split" flow drop non-KZ traffic before it ever reaches the offer - paying for clicks that can never become a billable FTD is the fastest way to wreck ROI on an iGaming cap.