UTM convention

Maven’s UTM convention for paid ads

The UTM parameters Maven expects on every paid ad, what each one records, why utm_mc_id matters most, and the template for each ad platform.

Maven expects every paid ad to carry the same set of UTM parameters. Paste the template for each ad platform once, and Maven ties every visit, lead and sale to the campaign and ad behind it. If your ads already use a different convention, keep it and tell Maven where it differs.

How the convention works#

Each ad platform gets one template. Most of it is readable: the platform, the kind of ad, and the campaign and ad names, so reports in Google Analytics and other tools make sense on their own. The last parameter, utm_mc_id, carries the platform’s IDs for the campaign, ad group and ad. Names change when someone renames a campaign; IDs don’t, so Maven matches on the IDs.

The parts in braces or underscores are the platform’s dynamic parameters. The platform replaces them with the real values on every click, so one template covers every ad.

Every parameter#

ParameterWhat it recordsValuesPlatforms that send it
utm_sourceThe platform the click came from, such as meta or linkedin.meta, bing, tiktok, linkedin, pinterest, snapchat, reddit, stackadapt9 of 10
utm_mediumThe kind of ad: a paid social ad, a paid search click or a programmatic ad.paid_social, cpc, programmatic9 of 10
utm_campaignThe campaign name, so reports in Google Analytics and other tools read in plain words.Filled in by the platform8 of 10
utm_contentThe level below the campaign: the ad set, ad group or line item name.Filled in by the platform7 of 10
utm_termThe ad name or, for search ads, the keyword that matched.Filled in by the platform7 of 10
utm_mc_idMaven’s tracking ID: the campaign, ad group and ad IDs, and more where the platform has them, in one value. Maven uses it to tie each visit to the exact ad.Built from the platform’s IDs10 of 10

Google Ads is the exception: its auto-tagging already tells Google Analytics the source, medium and campaign, so its template only carries utm_mc_id.

Why every ad needs utm_mc_id#

utm_mc_id is the one parameter Maven can’t work without. It holds the IDs that tie a visit to the exact ad, in one value, so it survives link shorteners and redirects, and it still matches after a campaign or ad is renamed. Without it, Maven can only guess which ad a visit came from.

Each part starts with a short prefix. Platforms send the parts they have:

Templates by platform#

Each platform page has the template to copy, where to paste it, and what every parameter records.

Platformutm_sourceutm_mediumutm_mc_id parts
Google AdsNot sentNot sentcm ag ad kw nw
Meta Adsmetapaid_socialcm ag ad cr pl ss
LinkedIn Adslinkedinpaid_socialcm ag ad
Microsoft Advertisingbingcpccm ag ad kw nw
TikTok Adstiktokpaid_socialcm ag cr pl
TikTok Smart+tiktokpaid_socialcm ag ad cr pl
Pinterest Adspinterestpaid_socialcm ag ad pl
Snapchat Adssnapchatpaid_socialcm ag ad
Reddit Adsredditpaid_socialcm ag ad
StackAdaptstackadaptprogrammaticcm ag cr

If your ads use a different convention#

Keep it. In Maven, open Attribution settings and add an exception for the parameter that differs, for example “On Meta Ads, utm_medium is paid”. Maven then reads your ads the way you tag them. When Maven sees ads that don’t match the convention, it asks you there whether to keep them that way, and points you to the platform’s guide if you’d rather fix the ads.

The one thing every ad needs is utm_mc_id.