Author: Tracking Operations Lead TG Target · UTM/SubID stack · focus: tracking entity, NOT analytics pillar SOP.
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
| Layer | Component | Capture method | Failure mode |
|---|
| 1 — Click ID | SubID / UTM | URL params, bot /start | Missing param on click |
| 2 — Event | CRM conversion | Reg, FTD, funded account | Event without click_id |
| 3 — Transport | Postback S2S | HTTP to tracker URL | 404, timeout, duplicate |
| 4 — Credit | Attribution window | 7d last-click | Window mismatch |
Layer 3 — postback glossary; layer 4 — attribution glossary; analytics SOP — analytics tracking pillar.
Bot start param vs web UTM
| Landing | Capture | Example | CRM field |
|---|
| Web lander | UTM on URL | ?utm_source=telegram&subid={click_id} | subid, utm_campaign |
| Telegram bot | /start param | t.me/bot?start={click_id} | subid from start payload |
| Mini-app | Deep link param | startapp={click_id} | subid via initData |
Landing entity - landing glossary.
Before expenses verify gate
- Configure tracker campaign + postback URL.
- Run 20 test clicks: web + bot paths.
- Trigger test conversion in CRM staging.
- Confirm postback received + match rate ≥95%.
- 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 expenses | Match rate median | Scale delay (days) | CPA rework incidents |
|---|
| Completed | 96.2% | 0 | 0.2/mo |
| Skipped | 87.4% | 12 | 1.8/mo |
Mini-case: forex EU — SubID tracking fix before scale
EU forex broker · bot + web hybrid · €28k/mo planned · Keitaro + CRM postback.
| Phase | Bot SubID pass | Test match rate | Decision | Live funded CPA |
|---|
| Pre-scale audit | Broken — 62% bot clicks | 71% | Hold scale | N/A |
| Post SubID fix | Unified web+bot chain | 97% | 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.
Tracking entity is current as of August 2026 (TG Target). Analytics SOP - analytics tracking pillar; postback - postback glossary.