Betting playbook: run BR/IN traffic to first bet and deposit, with or without Telegram
Betting traffic on leadgram lives or dies on one number: how many clicks turn into a first bet and a funded account. This playbook runs a single campaign - Betting — Live odds, targeting BR and IN - down both delivery paths leadgram supports, and shows where the first-bet and deposit conversions get recorded on each. The Telegram path routes players through a bot; the server-to-server path keeps them on a landing and reports back over the events API. Same offer, same geo, two attribution mechanics.
With Telegram - the bot funnel
Point the ad at a leadgram tracking link, not at the bookmaker directly. The click is recorded before anyone sees a bot, so BR and IN split cleanly in Reports from the first second. The link opens your bot with the click id attached in the /start payload - that is what lets attribution survive into every event further down the funnel. Set the link up in Tracking links and clicks.
The active flow on that bot is Betting — first bet. It greets the player, hands over the live-odds hook, and pushes them to the bookmaker with a deposit link. When the player reaches the money nodes, the flow fires the conversions - the first bet as a custom event, the funded account as deposit/ftd - and those go to Meta CAPI and trigger your postbacks in the same step. Build and activate it on the Message Flows page, and run the whole dialog through the simulator before you spend on it.
Without Telegram - landing + S2S
When there is no bot in the funnel - a webview offer, an app install, a plain bookmaker landing - keep the player on the web and report conversions server-to-server. The campaign points at the Live odds preland landing (/live-odds), which carries the click id forward to the bookmaker. The offer behind it is StavkaLive BR ($120 CPA, geo BR/IN).
Routing on this path is a click flow, Betting — device-split: it reads the click and sends Android and iOS players to the right destination before any deposit happens. The bookmaker's postback then hits your events API with the first-bet and deposit events, keyed by the click id, and leadgram relays them out to your partner trackers as postbacks. No Telegram anywhere in the chain - attribution rides entirely on the click id and the S2S callback.
From a media buyer's seat
The pain a betting buyer knows: two BR sources look identical on spend, but one funds accounts and the other only prints clicks, and without a clean per-source split you keep paying for both. The setup is one campaign per source, BR and IN separated by geo, both feeding the same offer so the money math stays comparable. The payoff is in Reports: deposit revenue sits next to cost per campaign, EPC tells you which creative earns its click, and the source that never reaches a first bet is the one you cut.
The two clips below walk the same decision from each path - first the Telegram funnel, then landing-plus-S2S - so you can see which one fits the offer in front of you.
Whichever path you run, keep BR and IN on separate campaigns rather than one campaign with a geo filter. A single first-bet conversion is worth $120 on StavkaLive BR, so a source that looks profitable blended can be hiding an IN half that never deposits - and you only see that once the two geos bill and report on their own line.
Keep going: Campaigns and funnels for the per-source split, Message Flows for the bot dialog, and Reports and ROI for where the deposit revenue shows up.