Author: Tracking Schema Lead TG Target · UTM naming schema · focus: UTM parameters entity, NOT full tracking stack.
The main thing from the article
- UTM = utm_source/medium/campaign/content only.
- NOT SubID or postback stack.
- TG Target fixed source/medium template.
- Schema compliance prevents attribution leak.
- iGaming case: leak fix −31% CPA variance.
UTM vs SubID disambiguation
| Param | Entity | Granularity | S2S match? |
|---|
| UTM (utm_*) | Campaign taxonomy | Campaign / creative label | No — reporting only |
| SubID (subid/click_id) | Click ID | Per click unique | Yes — postback match key |
Both required on web path. Tracking stack — tracking glossary.
TG Target UTM template (Telegram Ads)
| Parameter | Value | Rule | Example |
|---|
| utm_source | telegram | Fixed always | telegram |
| utm_medium | cpm | Fixed always | cpm |
| utm_campaign | {client}_{geo}_{objective}_{YYYYMM} | Lowercase, underscore | tgtarget_de_ftd_202608 |
| utm_content | {creative_id}_{variant} | Maps to creative entity | cr042_vB |
| subid | {click_id} | Separate from UTM — S2S key | abc123xyz |
Full URL example
https://lander.example/reg?utm_source=telegram&utm_medium=cpm&utm_campaign=tgtarget_de_ftd_202608&utm_content=cr042_vB&subid={click_id}
UTM schema compliance methodology (TG Target, August 2026)
Accounts with vs without enforced UTM schema, 90d rolling.
| Schema discipline | Attribution leak incidents/mo | Dashboard drill-down time | CPA reporting variance |
|---|
| Enforced TG Target template | 0.3 | −62% | ±9% |
| Ad hoc UTM naming | 1.4 | basic level | ±28% |
Mini-case: iGaming EU — UTM schema fix attribution leak
Licensed casino DE · web lander · €45k/mo · Keitaro + CRM postback.
| Phase | utm_campaign schema | Attributed FTD % | Reported FTD CPA | Decision |
|---|
| Pre-fix (Week 1–2) | Free-text, 3 naming variants | 68% | €142 (inflated) | Hold scale |
| Post schema fix (Week 3–4) | TG Target template enforced | 94% | €98 (stable) | Scale approved |
Attribution leak: fragmented utm_campaign split FTD credit across phantom campaigns — FTD CPA looked €142 vs true €98. Schema fix restored 68%→94% attribution match. Postback layer intact — leak was UTM taxonomy, not S2S. Attribution— attribution glossary.
FAQ
What are UTM tags in Telegram Ads?
UTM tags - query parameters for landing URL: utm_source, utm_medium, utm_campaign, utm_content. Entity = campaign-level web attribution labels, NOT full tracking stack. Tracking glossary - UTM+SubID+postback; here - UTM params and naming schema only.
UTM vs SubID - what's the difference?
UTM: Human-readable campaign taxonomy (source/channel/campaign/content). SubID: A unique click_id for each click for an S2S match. Both are needed in a full stack. UTM itself cannot match the postback - SubID contains click_id. Table below - values.
UTM vs tracking glossary?
Tracking glossary - full capture stack (UTM, SubID, postback chain). UTM glossary - utm_* parameters entity and TG Target naming schema only. Cannibalization guard: link tracking for stack, here - param definition.
TG Target UTM template for Telegram Ads?
utm_source=telegram (fixed). utm_medium=cpm (fixed). utm_campaign={client}_{geo}_{objective}_{YYYYMM}. utm_content={creative_id}_{option}. SubID is added separately as subid={click_id}. Template table below.
utm_campaign naming schema?
Template: {client_slug}_{geo}_{target}_{period}. Example: tgtarget_de_ftd_202608. Lower case, underscore delimiter, no spaces. Enables dashboard detailing without decoding SubID. Align the media plan campaign namespace.
Bot landing - is UTM needed?
Bot path uses /start param SubID, not web UTM. UTM glossary applies to web lander URLs only. Hybrid funnels: UTM on web + SubID on bot — both paths documented in tracking glossary. Landing type drives param choice.
UTM and attribution window?
UTM tags click when captured; The attribution window is applied at the credit level. UTM does not expand the window. Incorrect utm_campaign alignment in ad groups → fragmentation reported, not attribution leakage. Attribution glossary - window rules.
UTM schema red flags?
Missing utm_campaign in scale; custom text utm_content without Creative_id; utm_source≠telegram; duplication of campaign names among clients; UTM without SubID on the web path. Action: Audit the scheme before spending.
UTM benchmarks (Aug 2026)?
TG Target accounts with forced UTM schema: Dashboard drill-down time -62% compared to custom naming; Attribution leaks are 0.3 per month versus 1.4 per month. Compliance with the framework 89% of EU budget execution reports contain SOPs.
UTM and landing glossary?
Landing type (web/bot/mini-application) determines where UTM vs SubID applies. Landing glossary - entity types; UTM glossary - web URL param schema. Postback transport - postback glossary.
UTM entity and TG Target schema are current as of August 2026. Full stack - tracking glossary; postback - postback glossary.