UTM convention
How to add UTM parameters to StackAdapt ads
The UTM template for StackAdapt, where it goes on each creative’s link, and what every parameter records.
Add the template to the end of the link each creative sends people to. StackAdapt fills in the campaign, line item and creative on every click.
The template#
Add this to the end of the link each StackAdapt creative sends people to, after a question mark. The parts in single braces are StackAdapt’s dynamic parameters: StackAdapt replaces them with the real campaign, line item and creative on every click.
utm_source=stackadapt&utm_medium=programmatic&utm_campaign={SA_CAMPAIGN_NAME}&utm_mc_id=cm-{SA_CAMPAIGN_ID}-ag-{SA_LINE_ITEM_ID}-cr-{SA_CREATIVE_ID}Where to paste it in StackAdapt#
- In StackAdapt, open the campaign and edit the creative.
- Find the link the creative sends people to.
- Add the template to the end of the URL, after a ? (or after an & if the URL already has a ?), then save.
- Click through from a live ad and check that no braces, or %7B and %7D, are left in the address.
StackAdapt has no ID for individual ads, so the creative is the most detailed part of utm_mc_id.
StackAdapt has no creative name parameter, so the template leaves utm_content and utm_term out and keeps the creative ID in utm_mc_id.
What each parameter records#
| Parameter | Value in the template | What it records |
|---|---|---|
utm_source | stackadapt | The platform the click came from. Always stackadapt. |
utm_medium | programmatic | The kind of ad: a display or video ad bought programmatically. |
utm_campaign | {SA_CAMPAIGN_NAME} | The campaign name, filled in by StackAdapt on each click. |
utm_content | Not sent | StackAdapt has no creative name parameter, and the creative ID is already in utm_mc_id. |
utm_term | Not sent | StackAdapt has no ad name parameter, and the creative ID is already in utm_mc_id. |
utm_mc_id | cm-{SA_CAMPAIGN_ID}-ag-{SA_LINE_ITEM_ID}-cr-{SA_CREATIVE_ID} | Maven’s tracking ID: the campaign, line item and creative IDs, in one value, so a visit ties to the exact ad even after you rename it. |
The parts of utm_mc_id#
utm_mc_id carries the IDs Maven needs to tie a visit to the exact StackAdapt ad, in one value, so it survives link shorteners and redirects. Each part starts with a short prefix.
| Prefix | StackAdapt dynamic parameter | Meaning |
|---|---|---|
cm- | {SA_CAMPAIGN_ID} | Campaign ID |
ag- | {SA_LINE_ITEM_ID} | Line item ID |
cr- | {SA_CREATIVE_ID} | Creative ID |
Check it’s working#
Click through from the ad to your site. The address should carry utm_source=stackadapt and a utm_mc_id that starts cm- followed by the real IDs, not the parameter names in single braces. Maven reads your ads each morning, and Attribution settings shows StackAdapt as following the convention once StackAdapt reports the new parameters.
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 StackAdapt, 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.
utm_mc_id is the one parameter every ad needs. Without it, Maven can’t tie a visit to the exact ad.
For the whole convention and the other platforms, see Maven’s UTM convention.