UTM Parameters for Facebook, Google, TikTok & Reddit Ads: 2026 Cheat Sheet
You launch the same offer on Facebook, Google, TikTok and Reddit. A week later you open your analytics and see four different naming schemes, half the traffic labeled “direct”, and a campaign_id column that mixes Facebook IDs with Google IDs. The culprit is almost never your analytics tool - it is URL tagging done four different ways, because every ad platform has its own macro language, its own place to put the parameters, and its own click ID. This guide is the cheat sheet we wish existed when we tagged our own campaigns: exact syntax for all four platforms, copy-paste templates, and the traps that silently mislabel your data.
In a hurry? Use the free UTM generator above: paste your landing page URL, pick your platform, and it produces the exact tagging string for that platform’s URL parameters field - plus the full tagged link. Keep reading for the macro syntax behind every field it fills. The same builder also has its own page, the free UTM builder, if you want to bookmark it.
What UTM Parameters Are (In One Paragraph)
UTM parameters are five standardized query-string parameters - utm_source (where the click came from, e.g. facebook), utm_medium (the channel type, e.g. paid_social or cpc), utm_campaign (which campaign), utm_content (which ad or variant), and utm_term (which keyword or audience) - appended to your landing page URL so that analytics tools can attribute the visit, and everything the visitor later does, back to the exact ad that caused it. They were introduced by Urchin (the company Google bought to build Google Analytics) two decades ago, and they remain the lingua franca of campaign attribution: every analytics platform, including AxiTrace, reads them. The catch is that you should never type the values by hand per ad - every ad platform provides dynamic macros that fill in campaign, ad set and ad identifiers automatically at click time. The macros are where the four platforms diverge.
The Four Macro Languages at a Glance
| Facebook / Meta | Google Ads | TikTok Ads | Reddit Ads | |
|---|---|---|---|---|
| Macro syntax | {{campaign.name}} |
{campaignid} |
__CAMPAIGN_NAME__ |
{{CAMPAIGN_NAME}} |
| Name macros available | ✅ names + IDs | ❌ IDs only | ✅ names + IDs | ✅ names + IDs |
| Where you configure it | Ad level → “URL parameters” field | Campaign/account → “Final URL suffix” | Ad level → “URL parameters” section | Ad level → destination URL |
| Click ID (auto-appended) | fbclid |
gclid (needs auto-tagging ON) |
ttclid |
rdt_cid |
| Editable after publish? | Yes - but may restart learning | Yes - freely at campaign level | Yes (ad edit) | No - locked at publish |
| Classic mistake | Baking params into the link instead of the URL-parameters field | Using {campaign.name} (doesn’t exist) |
__AID__ is the ad group, not the ad |
Assuming Google’s {...} syntax works |
Four platforms, four syntaxes, four click IDs. Now platform by platform.
Facebook & Instagram (Meta): {{macro}} in the URL Parameters Field
Meta gives you a dedicated URL parameters field at the ad level (Ads Manager → ad → Tracking section). Parameters entered there are appended to your link at delivery time - and if the same parameter exists in both places, the URL-parameters field wins - so your landing page URL stays clean and the tagging lives in one dedicated place instead of being baked into the destination link. One warning straight from Meta’s own documentation: changing URL parameters after publishing may push the ad set back into the learning phase, so finalize your tagging before you hit publish, not after. Also note that name-based macros freeze at first publish - rename a campaign later and your URLs keep receiving the old name - which is exactly why the numeric IDs ride along in the template below.
Meta’s macros use double curly braces with dot notation, and cover both names and IDs across the full hierarchy:
| Macro | Resolves to |
|---|---|
{{campaign.name}} / {{campaign.id}} |
Campaign name / numeric ID |
{{adset.name}} / {{adset.id}} |
Ad set name / numeric ID |
{{ad.name}} / {{ad.id}} |
Ad name / numeric ID |
{{placement}} |
Delivery placement (e.g. facebook_feed, instagram_stories) |
{{site_source_name}} |
Origin surface: fb, ig, msg, an, th (Threads) |
Copy-paste template (URL parameters field):
utm_source=facebook&utm_medium=paid_social&utm_campaign={{campaign.name}}&utm_content={{ad.name}}&campaign_id={{campaign.id}}&adset_id={{adset.id}}&ad_id={{ad.id}}
Names go into the utm_* params so reports are human-readable; numeric IDs ride along in dedicated params so tools can join back to the Marketing API even after someone renames a campaign. Meta additionally appends the fbclid click identifier to every outbound click on its own - you never add it manually. (Since 2024 Meta may also auto-append a basic parameter set - source, medium, ad and campaign IDs - on some traffic with zero configuration; an explicit template like the one above overrides it and stays consistent.) If you run the Meta Pixel or the Conversions API, fbclid is what becomes the _fbc cookie that ties the click to the conversion.
Google Ads: ValueTrack {param} in the Final URL Suffix
Google works differently in three ways, and each one surprises people coming from Meta.
First, the field. You do not tag individual ads. Google has a Final URL suffix setting at account, campaign or ad group level (Campaign settings → Additional settings → Campaign URL options) - it technically exists at ad and keyword level too, with the most specific level winning, but campaign level is the sweet spot: suffix edits at account, campaign or ad-group level don’t send your ads back to review, while ad- and keyword-level edits do. Set it once at the campaign level and every ad, keyword and sitelink under it inherits the tagging.
Second, the syntax. Google’s macros are called ValueTrack parameters and use single curly braces: {campaignid}, {adgroupid}, {creative} (the ad ID), {keyword}, {matchtype}, {device}, {network}. Writing {{campaign.id}} or {campaign_id} produces nothing - the literal text passes through to your URL.
Third, there are no name macros. ValueTrack exposes IDs only. There is no {campaignname}. Your utm_campaign will contain a numeric ID like 24135657241, and your reporting layer is expected to resolve IDs to names via the Google Ads API - which is exactly what AxiTrace’s Google Ads dashboard does.
Copy-paste template (Final URL suffix):
utm_source=google&utm_medium=cpc&utm_campaign={campaignid}&utm_term={keyword}&utm_content={creative}&campaignid={campaignid}&adgroupid={adgroupid}
{keyword} in utm_term is a Google-only superpower - search campaigns tell you the exact keyword that triggered the ad, a dimension social platforms simply don’t have.
And the click ID: enable auto-tagging (Account settings → Auto-tagging) and Google appends gclid to every click. Auto-tagging is also a prerequisite for uploading offline conversions back into Google Ads, so there is no scenario where you want it off.
TikTok Ads: __MACRO__ and the AID/CID Trap
TikTok appends its click ID ttclid to every landing URL automatically. For UTMs you have two options: an auto-attach toggle that fills a basic set (source, medium, campaign) for you, or - for full macro-level control - a manual template entered in the ad’s dedicated URL parameters section. Don’t put UTMs in the “Tracking URLs” field; that one is reserved for third-party measurement pixels. The macros use a double-underscore convention: __CAMPAIGN_NAME__, __CAMPAIGN_ID__, __PLACEMENT__ (values: TikTok, TikTok Pangle), and here is where nearly everyone gets burned:
| Macro | Actually resolves to |
|---|---|
__CAMPAIGN_NAME__ / __CAMPAIGN_ID__ |
Campaign - as expected |
__AID_NAME__ / __AID__ |
The ad group - not the ad |
__CID_NAME__ / __CID__ |
The creative (ad) - not the campaign |
__ADID_V2_NAME__ / __ADID_V2__ |
The ad - Smart+ campaigns only |
__AID__ reads like “ad ID” and __CID__ reads like “campaign ID”; both intuitions are wrong. TikTok substitutes values either way and never errors, so the mistake produces confidently mislabeled reports instead of a failure you’d notice. Tattoo the mapping somewhere: AID = ad group, CID = creative.
Copy-paste template (ad → URL parameters section):
utm_source=tiktok&utm_medium=paid_social&utm_campaign=__CAMPAIGN_NAME__&utm_term=__AID_NAME__&utm_content=__CID_NAME__
Do not add ttclid yourself - TikTok appends it, and a duplicated parameter can degrade attribution. One more TikTok quirk: the macros are typo-fragile. A single missing underscore (_CAMPAIGN_NAME__) passes through as literal text with zero warnings, so paste the macros, never retype them.
Reddit Ads: {{MACRO}} Plus an Automatic rdt_cid
Reddit’s macro system looks like Meta’s - double curly braces - but with flat uppercase names instead of dot notation. The officially documented set: {{CAMPAIGN_NAME}}, {{CAMPAIGN_ID}}, {{ADGROUP_NAME}}, {{ADGROUP_ID}}, {{AD_NAME}}, {{AD_ID}}, plus {{CREATIVE_ID}}, {{POST_ID}} and {{ADVERTISER_ID}}. Parameters are appended to the ad’s destination URL at the ad level (catalog ads additionally get a parameter builder with a Preview URL tester) - there is no account-level tracking template you can set once, so the template below goes on every ad. And the biggest Reddit-specific rule, straight from Reddit’s docs: URL parameters cannot be changed after the ad is published. Triple-check the tagging before you hit publish, because fixing it later means recreating the ad.
Reddit auto-appends its click ID rdt_cid to ad clicks. You never strip it, because rdt_cid is what the Reddit Pixel and Conversions API use to match a later purchase back to the click - if a “URL cleanup” plugin or a redirect drops it, Reddit conversion tracking goes dark while everything looks fine in the browser. If your setup involves redirect chains that might lose the auto-appended value, you can additionally pass it explicitly with the rdt_cid={{CLICK_ID}} macro - belt and suspenders.
Copy-paste template:
utm_source=reddit&utm_medium=paid_social&utm_campaign={{CAMPAIGN_NAME}}&utm_term={{ADGROUP_NAME}}&utm_content={{AD_NAME}}
Tagging for AxiTrace: One Convention, Full Attribution
AxiTrace reads all five UTM parameters and captures every platform click ID out of the box - fbclid, gclid (plus gbraid/wbraid), ttclid, rdt_cid - and stores them on the visitor profile, so a purchase three visits later still attributes to the original ad. To get the cleanest possible dashboards, follow two rules on top of the templates above.
Rule 1 - keep utm_source canonical and lowercase. facebook, google, tiktok, reddit. Facebook, FB and fb-ads are three different sources to any analytics tool, and your traffic report splinters accordingly. Even if you forget the tag entirely, AxiTrace infers the source from the click ID (fbclid → facebook, gclid → google, and so on) - but the explicit tag always wins, so keep it consistent.
Rule 2 - ID parameters are platform-namespaced. In AxiTrace, campaign_id, adset_id and ad_id are Meta’s ID parameters (matching Meta’s own CAPI conventions), while campaignid and adgroupid - the raw ValueTrack names - are Google’s. They are not interchangeable: putting campaign_id={campaignid} in a Google suffix files a Google campaign ID into the Facebook column. Use the templates exactly as written above and each platform’s IDs land in the right place, which is what powers per-campaign ROAS in the Google Ads and Meta dashboards.
Everything else is automatic: the AxiTrace snippet persists the parameters past the first pageview, ties them to the visitor, and server-side tracking reports the eventual conversion back to each ad platform with the matching click ID attached. The unified ads dashboard then ranks every campaign by the revenue your store actually booked.
The Mistakes That Silently Break Attribution
Typing macros by hand. One character off and the platform passes the broken macro through as literal text. Paste from this page or from the platform’s macro picker.
Using one platform’s syntax on another. {{campaign.name}} on Google, {campaignid} on TikTok - no error, no substitution, just garbage in your reports.
Manually adding click IDs. gclid, ttclid, rdt_cid and fbclid are appended by the platforms. Adding them yourself creates duplicate parameters and can break conversion matching.
Redirects that drop query strings. Link shorteners, www → apex redirects, http → https hops and “pretty URL” plugins frequently strip parameters. Click your own ad preview and check what actually arrives in the address bar.
Tagging the link instead of the parameters field (Meta). The dedicated field keeps tagging separate from the creative and cleanly overrides any duplicate parameters. But don’t count on fixing it later either way - Meta explicitly warns that changing URL parameters after publish can push the ad set back into the learning phase. Tag it right the first time, on every platform (Reddit won’t even let you change it).
Inconsistent casing and naming. Decide paid_social vs cpc per channel once, write it down, and reuse it forever. The best convention is the one nobody ever improvises on.
Using the Generator: What You Type vs. What It Fills
The builder at the top of this page implements the four templates from this guide. You type exactly one thing - your landing page URL. Everything else arrives prefilled with the correct macro for the platform you pick, and every field can be overridden with static text if you prefer.
- Facebook: campaign and ad names come prefilled as
{{campaign.name}}/{{ad.name}}; optionally add your audience name toutm_term(or use the{{placement}}macro), and keep the Meta ID parameters on -campaign_id={{campaign.id}},adset_id={{adset.id}},ad_id={{ad.id}}are what AxiTrace stores as the Meta CAPI fields and they survive campaign renames. - Google: nothing to type at all - ValueTrack passes IDs only. The one thing worth choosing is your campaign type: Search puts
{keyword}intoutm_term, Display swaps in{placement}, Performance Max dropsutm_termand puts{placement}intoutm_content, Shopping uses{product_id}. Thecampaignid={campaignid}andadgroupid={adgroupid}pair is AxiTrace’s Google namespace. - TikTok: campaign, ad group and creative come as
__CAMPAIGN_NAME__,__AID_NAME__(ad group - not the ad) and__CID_NAME__(creative - not the campaign). Paste the result into the URL parameters section, never the “Tracking URLs” field. The builder deliberately adds no ID parameters: AxiTrace matches TikTok conversions on the auto-appendedttclid- and sincecampaign_idis reserved for Meta in AxiTrace, reusing it for TikTok IDs would file TikTok data into the Facebook column. - Reddit: campaign, ad group and ad names come as
{{CAMPAIGN_NAME}},{{ADGROUP_NAME}},{{AD_NAME}}. Same ID rule as TikTok: AxiTrace matches on the auto-appendedrdt_cid. The result is locked after publish, so generate it, paste it, and triple-check before you go live.
The builder outputs two formats: the full tagged URL (for testing in your browser) and the bare parameter string (for the platform’s URL parameters field or Final URL suffix). Click IDs - fbclid, gclid, ttclid, rdt_cid - are deliberately never included: every platform appends its own automatically, and duplicating them by hand breaks conversion matching. And the ID namespaces are kept platform-clean for AxiTrace: campaign_id/adset_id/ad_id only ever carry Meta values, campaignid/adgroupid only ever carry Google values, and TikTok/Reddit rely on their click IDs - the exact convention described in the Tagging for AxiTrace section above.
FAQ
Should I put names or IDs in my UTM parameters?
Both, in different slots. Names (utm_campaign, utm_content) make reports readable by humans; IDs (in platform-specific parameters) survive renames and let tools join spend data via the platform APIs. Google is the exception - ValueTrack has no name macros, so you pass {campaignid} and let your analytics resolve names via the API.
Do UTM parameters affect ad delivery or SEO?
The parameters themselves are inert query-string data; ad platforms ignore them for delivery and search engines ignore them for ranking (canonical tags on your landing pages prevent duplicate-content indexing). What is not free is editing them after launch: Meta documents that changing URL parameters on a published ad may restart the learning phase, and Reddit locks them entirely at publish. Google is the forgiving one - suffix changes at campaign level apply without re-review.
Why does my traffic still show up as “direct”?
Usually one of three things: a redirect stripped the query string, the landing page is behind a consent wall that blocks the analytics snippet before it reads the URL, or the visitor converted in a later session and your tool doesn’t persist first-visit attribution. AxiTrace stores UTM and click-ID data on the visitor profile at first touch, so later sessions and delayed purchases keep their original source.
Is there a difference between utm_medium=cpc and paid_social?
Only convention. cpc traditionally means paid search, paid_social means paid social feeds. What matters is picking one value per channel and never varying it - mixed mediums split the same channel into multiple rows in every report you’ll ever build.
What do I actually have to type into the generator?
Just your landing page URL. Pick the platform and the generator fills utm_source, utm_medium, utm_campaign, utm_content and utm_term with that platform’s macros. Overrides exist for the campaign name, ad name and audience if you want static values - but the macro defaults are what we recommend, because they never go stale.
Where do I paste the result?
The bare parameter string goes into the platform’s dedicated field: the URL parameters field at ad level (Meta), the Final URL suffix at campaign level (Google), the URL parameters section at ad level (TikTok), or the destination URL at ad level (Reddit). The full tagged URL is for previewing what a visitor’s address bar will actually receive.