# Google Ads tracking template for UTM parameters

> The UTM template for Google Ads, where it goes in your account’s tracking settings, and what every parameter and ValueTrack value records.

Source: https://mavendata.ai/docs/utm-convention/google-ads

Paste the template into your Google Ads account’s final URL suffix once. Google fills in the campaign, ad group, ad and keyword on every click, and auto-tagging keeps sending the rest to Google Analytics.

## The template

Paste this into your Google Ads account’s final URL suffix, in the account’s tracking settings. The parts in single braces are Google’s dynamic parameters: Google replaces them with the real campaign, ad group, ad and keyword on every click.

```text
utm_mc_id=cm-{campaignid}-ag-{adgroupid}-ad-{creative}-kw-{keyword}-nw-{network}
```

## Where to paste it in Google Ads

1. In **Google Ads**, open your account’s settings.
2. Open the **Tracking** section.
3. Paste the template into **Final URL suffix**, replacing anything already there, and select **Save**.
4. Check that auto-tagging is switched on for the account and that Google Ads is linked to your Google Analytics property.

Campaigns, ad groups and ads can have a final URL suffix of their own, and theirs wins over the account’s. If any of yours do, paste the template there too.

If your account uses a tracking template instead, start it with {lpurl}? followed by the template, and test it before you save.

Auto-tagging adds Google’s click ID (gclid) to every click and gives Google Analytics the source, medium and campaign, which is why the template only carries utm_mc_id.

## What each parameter records

| Parameter | Value in the template | What it records |
| --- | --- | --- |
| `utm_source` | Not sent | Google’s auto-tagging (gclid) gives Google Analytics the source, medium, campaign and keyword, so the template only carries utm_mc_id. |
| `utm_medium` | Not sent | Google’s auto-tagging (gclid) gives Google Analytics the source, medium, campaign and keyword, so the template only carries utm_mc_id. |
| `utm_campaign` | Not sent | Google’s auto-tagging (gclid) gives Google Analytics the source, medium, campaign and keyword, so the template only carries utm_mc_id. |
| `utm_content` | Not sent | Google’s auto-tagging (gclid) gives Google Analytics the source, medium, campaign and keyword, so the template only carries utm_mc_id. |
| `utm_term` | Not sent | Google’s auto-tagging (gclid) gives Google Analytics the source, medium, campaign and keyword, so the template only carries utm_mc_id. |
| `utm_mc_id` | `cm-{campaignid}-ag-{adgroupid}-ad-{creative}-kw-{keyword}-nw-{network}` | Maven’s tracking ID: the campaign, ad group and ad IDs, plus the keyword and network, 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 Google Ads ad, in one value, so it survives link shorteners and redirects. Each part starts with a short prefix.

| Prefix | Google Ads dynamic parameter | Meaning |
| --- | --- | --- |
| `cm-` | `{campaignid}` | Campaign ID |
| `ag-` | `{adgroupid}` | Ad group ID |
| `ad-` | `{creative}` | Ad ID |
| `kw-` | `{keyword}` | The keyword that matched the search (empty for Display and Video ads) |
| `nw-` | `{network}` | Network: where the ad showed, such as Google Search, search partners, Display or YouTube |

## Check it’s working

Click through from the ad to your site. The address should carry 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 Google Ads as following the convention once Google 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 Google Ads, utm_campaign is the campaign ID”. 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](https://mavendata.ai/docs/utm-convention).
