UTM parameters and auto-tagging at a glance
UTM parameters are key-value pairs appended to a landing page address: source, medium, campaign and, optionally, term and content. The analytics tool reads them once, on the landing page, and writes them to the session. Google Analytics Help documents how to build these links and how GA4Google's event-based analytics platform. uses the values. Because they are just text, UTMs work on any link from any platform, email, partner or printed code, and any analytics tool can read them. Their weakness is that they are only as good as the people and templates that write them. A campaign tagged three ways appears as three campaigns, and a medium value the channel rules do not recognise lands in Unassigned. The UTM and naming conventions guide covers the five parameters and the convention that keeps them consistent.
Auto-tagging is a Google Ads account setting. When it is on, Google appends a click identifier, gclid, to the
landing page address of each ad click. The identifier carries no campaign names itself; it is a key that Google Ads
and linked Google products resolve into the click's details, which is why it can carry more than a manual tag. A
linked analytics property uses it to label the session with campaign, ad group, keyword and cost, and a lead form can
store it so that later sales can be sent back to Google Ads. The
GA4 and Google Ads integration tutorial covers the link and the checks that
keep auto-tagging working, and the glossary entry on auto-tagging lists what breaks it.
So the comparison is not a contest between two equivalent methods. Auto-tagging is richer but narrow: it works for one ad platform and the Google products linked to it. UTMs are universal but manual: they work everywhere, carry only what someone wrote, and depend on discipline. The practical question is which method each traffic source needs, and how to keep them from interfering where they overlap.
Compare table
UTM parameters vs Auto-tagging
| Row label | UTM parameters | Auto-tagging |
|---|---|---|
| How it works | Labels added to the link by hand or by template, read on the landing page | A click identifier added automatically to each Google Ads click, resolved by linked products |
| Platforms covered | Any link: every ad platform, email, social posts, partners, QR codes | Google Ads clicks, read by linked Google Analytics and other Google products |
| Data passed | Source, medium, campaign, and optionally term and content | Campaign, ad group, keyword, creative and click detail held in Google Ads |
| Cost data | None; cost has to be imported or joined separately | Flows into the linked analytics property with the account link |
| Setup effort | Ongoing: every link needs tagging, ideally through templates and a builder | One setting, plus a check that redirects and forms keep the identifier |
| Error risk | Typos, inconsistent case and unrecognised mediums split or misfile traffic | Silent loss when redirects, domain changes or consent strip the identifier |
| Conflict behaviour | Can override or clash with auto-tagged values when both are on one link | A property-level setting decides whether manual values override it |
| Readable by other tools | Yes; any analytics tool or CRM can read the values | Only by Google's products, unless the identifier is stored and passed on |
| Best-fit sources | Meta, LinkedIn, TikTok, Microsoft Ads, email, partners, offline codes | Google Ads campaigns with a linked analytics property |
The rows on cost data and conflict behaviour matter most for Google Ads. Turning auto-tagging off and relying on UTMs loses cost and keyword detail in analytics. Adding UTMs on top of auto-tagging without a decision can make campaign names stop matching between the two systems.
When to choose UTM parameters
Use UTMs for every link where auto-tagging does not reach analytics. That covers most of the marketing mix: paid social, other search engines, display and video platforms outside Google Ads, email, organic social posts, influencer and partner links, affiliate placements and codes on print. Other ad platforms append their own click identifiers, but analytics does not read campaign detail from them, so a paid social link without UTMs is recorded from the referrer and usually lands in organic social. That single gap is one of the commonest reasons paid social looks underreported.
Generate UTMs rather than type them wherever possible. Most ad platforms offer URL-parameter templates that insert campaign and ad names automatically; use them with the convention's vocabulary. For links outside ad platforms, a builder and a request process, such as the UTM link request SOP, keep values consistent and logged.
UTMs are also the fallback for Google Ads clicks that need reading outside Google's products. If a CRM, a non-Google analytics tool or a partner report needs to recognise Google Ads traffic, a manual tag may be the only thing it can read. That is a reason to add UTMs deliberately, with the precautions below, not by default.
When to choose auto-tagging
Use auto-tagging for Google Ads whenever an analytics property is linked to the account, which in practice means almost always. It carries campaign, ad group, keyword and cost detail that a UTM cannot, it needs no tagging effort per link, and it cannot be mistyped. Google Ads Help documents the setting, and the link setup offers to switch it on; accept unless there is a documented reason not to.
Auto-tagging also matters beyond analytics. Google Ads conversion tracking relies on the click identifier to match a later conversion to the click, and lead businesses capture it on forms so that sales outcomes can be uploaded back to the ad account. Turning it off to make UTMs work breaks more than reporting.
Its one demand is that the identifier survives the journey. Redirects that drop query stringsA key and value appended to a URL after a question mark, such as a filter, sort order, session or tracking tag, that may or may not change the page., a booking or checkout domain that the visit moves to without Cross-Domain TrackingConfiguring analytics so a visit that moves between a business's own domains stays one session., forms that do not capture the value and declined consent can all lose it silently. When a sudden rise in direct or Unassigned traffic coincides with a fall in paid search sessions, the Unassigned traffic guide is the place to start the diagnosis.
An outdoor retailer untangles its campaign names
Verrin Outdoor runs auto-tagging on Google Ads and, on an agency's advice, also adds UTMs to every Google Ads final URL. Its analytics property is set to let manual values override. Over a quarter the agency renames 12 campaigns in Google Ads but not in the UTMs, so GA4 reports 31 campaign names for Google Ads traffic against 19 in the ad account, and cost no longer lines up with sessions for the renamed campaigns. Verrin removes UTMs from Google Ads URLs, leaves auto-tagging on and switches the override setting off. It keeps UTMs, generated by platform templates, on its Meta and Microsoft Ads links, where paid social sessions had been landing in organic social. The following month, Google Ads campaign names in GA4 match the ad account and paid social appears in its own channel.
Decision table
| Traffic source | Use | Why |
|---|---|---|
| Google Ads with a linked analytics property | Auto-tagging | Richer detail and cost data with no tagging effort |
| Meta, LinkedIn, TikTok and other ad platforms | UTM parameters, from platform templates | Analytics does not read campaign detail from their identifiers |
| Microsoft Ads | UTM parameters | A GA4 property does not resolve its identifier into campaign detail |
| Email campaigns and newsletters | UTM parameters | No click identifier reaches analytics |
| Partner, affiliate and influencer links | UTM parameters, issued through a request process | Third parties need fixed, logged values |
| Google Ads traffic read by a non-Google tool | Auto-tagging plus deliberate UTMs | The other tool cannot read the identifier |
| Comparing client-side and server-side collection | See client-side versus server-side tagging | A different decision about how data is sent |
Avoiding conflicts between the two
The safest rule is the one the naming conventions guide states: auto-tag where the platform and the analytics tool share an identifier, tag manually everywhere else, and never put both on the same link without a documented reason. For most teams that means no UTMs in Google Ads final URLs or tracking templates at all.
Where there is a reason to use both, make three decisions and write them down. First, check the analytics property setting that decides whether manual values override auto-tagged ones, and record which way it is set. Second, if manual values are allowed to win, generate them from the ad account's own campaign and ad names through a tracking template, so that a rename in Google Ads changes the UTM too. Third, test a live click after any change, confirming that the identifier survives redirects and that the session lands in the expected channel with the expected campaign name.
Keep an eye on the whole path from click to conversion. Auto-tagging and UTMs both depend on query parameters reaching the landing page and, for later conversions, being stored. A redirect rule, a new checkout domain or a form rebuilt without hidden fields can break either method without any error, and the first sign is usually a channel report that no longer adds up.
Common mistakes
- Turning auto-tagging off to use UTMs. Analytics loses Google Ads cost and keyword detail, and conversion matching suffers.
- Adding UTMs to Google Ads links by default. Campaign names drift apart when one side is renamed and the other is not.
- Leaving paid social links untagged. Their sessions land in organic social and the paid channel looks weak.
- Typing UTMs by hand. Case and spelling differences split one campaign into several; use templates and a builder.
- Using medium values the channel rules do not recognise. Sessions fall into Unassigned.
- Ignoring redirects and domain changes. Both methods fail silently when the query string is dropped.
- Not recording the override setting. Nobody can explain why analytics and the ad account disagree.
