Auto-Tagging Is Off, and Your Attribution Has Been Guessing Ever Since

Auto-tagging is a single checkbox in your Google Ads account settings, and it decides whether every click on every ad carries an identifier with it. When it is on, almost everything downstream works without you thinking about it. When it is off, nothing errors. No status turns red, no email arrives, and the campaigns keep spending exactly as before. You simply start getting worse answers to every question you ask about where results came from.

This is one of the few tracking problems that is both extremely consequential and genuinely trivial to fix. The whole repair is one setting and a day of waiting. The reason it is worth an article is that the symptoms almost never point back at the cause, so agencies usually spend weeks blaming attribution models, iOS, or the client’s website before anyone opens account settings and looks.

What auto-tagging actually does

When someone clicks your ad with auto-tagging enabled, Google appends a parameter to the destination URL called the GCLID, short for Google Click Identifier. A landing page URL that looked like example.com/offer arrives in the browser as example.com/offer?gclid=EAIaIQobCh... with a long opaque string attached.

That string is not descriptive. It does not contain your campaign name or your keyword in readable form. It is a reference number that Google can look up on its own side, which is precisely what makes it more reliable than anything you could construct by hand. It identifies the exact click, not the general category of click.

Several things read that identifier, and all of them matter:

• Google Analytics uses it to attribute the session to the correct campaign, ad group, and keyword, rather than relying on whatever the referrer happens to say.
• Conversion tracking uses it to connect a conversion back to the specific click that produced it, which is what makes conversion reporting more than a correlation.
• Offline conversion imports depend on it entirely. When a lead becomes a closed deal six weeks later, the GCLID captured at form submission is how you tell Google which click earned the revenue.
• Smart Bidding is downstream of all of the above. It optimises against the conversion signal it receives, and a degraded signal produces degraded bidding.

How it ends up turned off

Nobody disables auto-tagging out of malice, and in most accounts where it is off, nobody remembers doing it. The common routes are mundane.

Somebody wanted clean URLs

The GCLID is ugly. It is a long string of characters on the end of an otherwise tidy landing page URL, and periodically a client, a designer, or a developer decides this looks unprofessional and asks for it to be removed. The request sounds cosmetic. It is not.

A third-party tool asked for manual tagging

Some analytics and call tracking platforms document a setup that uses manual UTM parameters, and a reasonable person reading those instructions concludes that auto-tagging is the thing being replaced. It usually is not. The two can coexist, and in most stacks they should.

The account was rebuilt or migrated

A new account, a new manager account structure, or a migration from another agency is the most common moment for this setting to end up in a state nobody chose deliberately. Do not assume a default. Open the account and look, because the only thing that matters is what your account says today.

A redirect is eating the parameter

This one is the most insidious, because auto-tagging can be switched on and working correctly while the GCLID still never reaches your analytics. If your landing page URL redirects, say from the non-www version to the www version, or from HTTP to HTTPS, or through a link shortener or an A/B testing tool, that redirect has to carry the query string with it. Plenty of redirect rules do not. The click arrives with a GCLID, the redirect drops it, and the page that finally loads has no identifier on it at all.

What it looks like from the outside

Here is the frustrating part. None of the symptoms announce themselves as an auto-tagging problem, and most of them look like a different problem entirely.

1. Paid traffic appears as organic or direct. Without the GCLID, analytics falls back to the referrer, and a referrer from a Google domain looks an awful lot like organic search. Your Google Ads spend starts showing up credited to channels you are not paying for, which makes organic look like a hero and paid look like a waste.
2. Google Ads and GA4 stop agreeing, badly. Some discrepancy between these two is normal and expected. A gap that suddenly widens and stays wide is not, and missing click identifiers is one of the few causes that produces a persistent structural gap rather than noise.
3. Offline conversion imports fail or go quiet. If you are a lead gen advertiser uploading closed deals back into Google Ads, those uploads are keyed on the GCLID. No identifier captured at form submission means nothing to upload, and the import either errors or silently matches almost nothing.
4. Performance looks mysteriously worse. Campaigns that fed on a clean conversion signal start making worse decisions. Nothing broke. The inputs just got noisier.

How to check it in two minutes

Three checks, in increasing order of how much they prove.

1. The setting itself

In Google Ads, open your account settings and find the auto-tagging section. You are looking for the option about tagging the URL that people click through from your ad. Confirm it is ticked. If you manage through a manager account, check the individual client account, because this is an account-level setting and not something inherited in a way you should trust without looking.

2. A real click

The setting being on proves the intent. A real click proves the outcome, and the two can differ when a redirect is involved. Click one of your own live ads, let the landing page fully load, and then read the address bar. If you see a gclid parameter sitting there, the identifier survived the trip. If the setting is on but the parameter is missing from the final URL, you have a redirect problem rather than a settings problem, and the fix is in your redirect rules rather than in Google Ads.

3. The analytics side

Finally, confirm that the sessions are landing where they should. Look at how much of your Google Ads traffic is being credited to paid search versus organic or direct. A sharp change in that split on a date when nothing else changed is a strong signal, and the date itself usually tells you what happened that day.

Fixing it, and what to expect afterwards

Switch the setting on. That is the fix, and it takes effect for clicks from that point forward, not retroactively. The historical data stays wrong, and there is no way to repair it, which is an argument for checking this on every account you inherit rather than waiting for a symptom.

Then deal with the redirect question properly, because turning the setting on while a redirect strips the parameter leaves you exactly where you started. Ask whoever owns the site to confirm that redirects preserve query strings. For most server configurations this is a one line change, and it is a change that quietly improves every tracking parameter you will ever use, not just this one.

Do you still need UTM parameters?

You can run both. If you use UTM parameters for a reporting stack that needs readable campaign names, keep them, and keep auto-tagging on as well. They serve different consumers. The important thing is not to think of manual tagging as a replacement, because the GCLID does things no hand-written parameter can do, most obviously offline conversion import. A campaign name in a URL is a label. The GCLID is a reference to a specific click, and Google is the only party that can resolve it.

Why this goes unnoticed for so long

Every surface you would normally check looks healthy. The campaigns are serving. The conversion action is recording conversions. The landing page loads. The tag is present on the page. Nothing in the Google Ads interface tells you that the clicks arriving at your site are anonymous, because from the ad platform’s point of view the clicks happened and were billed exactly as expected.

The damage is downstream, in the quality of every attribution decision you make afterwards, and in a budget conversation where you cannot prove what paid search did. By the time someone asks the question that exposes it, the affected period is usually months long.

You can check any site for the tracking side of this in about thirty seconds with our free tracking scan. It reads the public source and the published tag manager container and tells you what is installed and what looks misconfigured, without needing access to the site or the ad account. It is honest about its limits too: whether auto-tagging is enabled is a setting inside your Google Ads account, so the scan will not see it, and the two minute check above is how you confirm that part.

What a scan also cannot tell you is whether the setup still looks like this next month. A redirect rule added during a site update, a migration, or a well-meaning request for cleaner URLs can undo this at any point. Taglert rechecks every connected account every thirty minutes and emails you when conversion tracking changes, so the fix stays fixed rather than quietly reverting.