Platform pack
UTM parameters for Snapchat
Where the tracking goes in Snapchat, what its dynamic values fill, the rules the pack checks, and a worked link. Read from the Snapchat pack, version 2026.09.1.
Where the tracking goes
In Snapchat, the pack puts UTM parameters in URL parameters.
The platform’s own click ID parameter is ScCid.
Source values the pack recognizes for this platform: snapchat, snap.
Snapchat macros (dynamic values)
Dynamic insertion means the platform replaces a token with the real value, such as a campaign ID, when the ad is clicked. Tag Docket leaves these tokens untouched. Syntax: double braces.
| Token | What it fills | Recommended for | Note |
|---|---|---|---|
{{campaign.name}} | Campaign name | ||
{{campaign.id}} | Campaign ID | utm_id | |
{{adSet.name}} | Ad set name | camelCase adSet, where Meta uses lowercase adset | |
{{adSet.id}} | Ad set ID | utm_term | camelCase adSet |
{{ad.id}} | Ad ID | utm_content | |
{{creative.name}} | Creative name | ||
{{creative.headline}} | Creative headline | ||
{{site_source_name}} | Site source |
Which UTM field each value is for
Snapchat fills these in when the ad is clicked. Note the camelCase {{adSet.id}}: Meta's lowercase {{adset.id}} does not work here.
utm_id={{campaign.id}}. The Snapchat campaign ID, for joining to Snapchat's reporting.utm_term={{adSet.id}}. The ad set — Snapchat's audience-and-budget level.utm_content={{ad.id}}. The individual ad, so GA4 can tell creatives apart.
Source, medium and campaign stay your own values, from your naming convention.
Rules and pitfalls
The pack checks a link against these before it is minted.
- Blocks
Snapchat uses {{adSet.name}} in camelCase; Meta uses {{adset.name}} in lowercase. Four other tokens are byte-identical across the two platforms, so a URL copied from a Meta workflow PARTLY works — the shared tokens resolve, the ad-set token does not, and nothing looks broken.
- Advises
Shopify advertisers using the Snapchat Ads App have snap_campaign_id set to a fixed identifier that cannot be overwritten, by the builder or by url_macro_parameters.
- Advises
Previewing an ad by scanning a Snapcode populates dynamic parameters as 'successful_' rather than real values. That is preview-only behaviour, but it looks exactly like broken tagging.
A worked example
Built from the base preset’s convention: lowercase, _ between parts,
utm_source={platform}, utm_medium={channel} and
utm_campaign={season}_{offer}_{service}. Here the platform is snapchat,
the channel is paidsocial (Paid social) and the campaign is
spring26_freeestimate_roofing.
Parameters for URL parameters:
utm_source=snapchat&utm_medium=paidsocial&utm_campaign=spring26_freeestimate_roofing With the pack’s recommended values added:
utm_source=snapchat&utm_medium=paidsocial&utm_campaign=spring26_freeestimate_roofing&utm_id={{campaign.id}}&utm_term={{adSet.id}}&utm_content={{ad.id}} On a plain landing-page link, the same three values read:
https://example.com/free-estimate?utm_source=snapchat&utm_medium=paidsocial&utm_campaign=spring26_freeestimate_roofing Where GA4 files it. Medium paidsocial lands in:
Paid Social for social sites, Paid Other otherwise. See every medium and its GA4 channel.
How this pack is monitored
Not automatically monitored. Renders in the browser, like Meta, and is checked by hand for the same reason.
The pack is verified (last verified September 28, 2026). Version 2026.09.1, effective September 28, 2026. Source: businesshelp.snapchat.com/s/article/add-url-macros.
Related
- Free UTM checker: check a tagged link before it ships.
- UTM naming convention template for agencies
- All 8 platform packs
- Start free trial: every plan includes every platform pack.
Questions
Where do I put UTM parameters in Snapchat?
Does Snapchat have dynamic URL macros?
Is the Snapchat pack verified, and how is it monitored?
Bring the spreadsheet. We’ll show you the registry.
Start a free trial, no card needed. Your team signs in with an email link, no passwords.