Attribution & tracking · Tracking

What is tracking in Telegram Ads: UTM and SubID

Tracking Object: UTM, SubID, postback chain, NOT analytical SOP. Case on setting up Forex tracking TG Target (August 2026).

Published: ·Updated:

Tracking — capture layer: UTM on landing URL, SubID/click_id per click, postback chain to tracker. Entity definition only - NOT analytics pillar procedural SOP. Postback transport — postback glossary; attribution rules — attribution glossary; landing types - landing glossary; before QA costs - campaign audit guide.

The main thing from the article

  • Tracking = UTM + SubID + postback chain.
  • NOT analytics pillar SOP.
  • Bot /start param vs web UTM.
  • Verify gate is required before spending.
  • Forex case: SubID fix before scale.

Tracking stack layers

LayerComponentCapture methodFailure mode
1 — Click IDSubID / UTMURL params, bot /startMissing param on click
2 — EventCRM conversionReg, FTD, funded accountEvent without click_id
3 — TransportPostback S2SHTTP to tracker URL404, timeout, duplicate
4 — CreditAttribution window7d last-clickWindow mismatch

Layer 3 — postback glossary; layer 4 — attribution glossary; analytics SOP — analytics tracking pillar.

Bot start param vs web UTM

LandingCaptureExampleCRM field
Web landerUTM on URL?utm_source=telegram&subid={click_id}subid, utm_campaign
Telegram bot/start paramt.me/bot?start={click_id}subid from start payload
Mini-appDeep link paramstartapp={click_id}subid via initData

Landing entity - landing glossary.

Before expenses verify gate

  1. Configure tracker campaign + postback URL.
  2. Run 20 test clicks: web + bot paths.
  3. Trigger test conversion in CRM staging.
  4. Confirm postback received + match rate ≥95%.
  5. Sign-off in campaign audit before live spend.

Audit checklist — campaign audit guide.

Tracking QA methodology (TG Target, August 2026)

Accounts with vs without before expenses gate, first 30d live.

Before gate expensesMatch rate medianScale delay (days)CPA rework incidents
Completed96.2%00.2/mo
Skipped87.4%121.8/mo

Mini-case: forex EU — SubID tracking fix before scale

EU forex broker · bot + web hybrid · €28k/mo planned · Keitaro + CRM postback.

PhaseBot SubID passTest match rateDecisionLive funded CPA
Pre-scale auditBroken — 62% bot clicks71%Hold scaleN/A
Post SubID fixUnified web+bot chain97%Scale approved€156 (stable)

Before expenses gate caught bot SubID failure — avoided €28k spend on broken tracking. Post fix: match 71%→97%, scale cleared. Postback layer - postback glossary; attribution — attribution glossary.

FAQ

What is tracking in Telegram Ads?

Tracking - capture layer object: UTM parameters, SubID/click_id, chain of postbacks from the click to the CRM event. NOT an analytical SOP (Telegram analytics-advertising tracking). The definition of just the components of the tracking stack is here.

UTM in Telegram Ads - how to use?

Add utm_source, utm_medium, utm_campaign, utm_content to the landing URL in your ad. The cabinet misses a click; the tracker reads UTM upon landing. TG Target: utm_source=telegram, utm_medium=cpm always.

SubID vs UTM?

UTM: Campaign-level web attribution parameters. SubID: A unique click_id for each click for an S2S match. Both are needed in a full stack. The bot path uses the /start SubID parameter instead of web UTM.

Tracking vs analytics pillar?

Analytics pillar - procedural SOP (dashboards, reporting cadence). Tracking glossary - entity definition (UTM, SubID, postback chain). Cannibalization guard: link pillar for process, here - stack layers.

Bot start param vs web UTM?

Web landing: UTM by URL. Telegram bot: t.me/bot?start=SubID encodes click_id. Both must reach CRM for the postback to match. Broken bot param - error with maximum hit rate.

Before expenses verify gate?

TG Target SOP before any spending: (1) test click → landing page/bot → event CRM → postback → tracker shows conversion. (2) Match rate test ≥95% with 20 test clicks. (3) Certification of campaign audit.

Tracking stack layers?

Level 1: Click capture (UTM/SubID). Level 2: CRM event. Level 3: postback. Level 4: Attribution Window. Table below. Postback is a third-level object.

Tracking vs attribution?

Tracking = how the click_id is captured and delivered. Attribution = rules for assigning credit. Tracking glossary - capture; attribution glossary - window/model.

Tracking red flags?

Missing utm_campaign in scale; bot /start without SubID; Postback URL 404; web+bot same user double click_id; there is no surcharge test. Action: Campaign verification checklist.

Tracking and landing types?

Web lander, Telegram bot, mini-application - each needs SubID/UTM path to CRM. Landing glossary - entity types; here - param capture per type.

Need tracking stack setup

TG Target: UTM/SubID QA, bot+web chain, verify gate before expenses.