Your Conversion Tag Is Firing on Every Page (and Smart Bidding Believes It)

There is a category of tracking bug that does not quietly lose you data. It invents data. A conversion tag attached to an All Pages trigger reports every single visitor as a conversion, and because the number goes up rather than down, nobody treats it as a problem. The account looks like it is performing better than it ever has.

This is the most common serious misconfiguration we find, and it is almost always invisible from inside the ad platform. Google Ads does not know that your “purchase” tag is firing on your blog. It receives a conversion, logs a conversion, and feeds that conversion to the bidding algorithm. Everything downstream behaves exactly as designed, on a signal that means nothing.

What it actually looks like

In Google Tag Manager, a conversion tag has two parts that matter: the tag itself, which says what to report, and the trigger, which says when to report it. The tag is usually fine. The trigger is where this goes wrong.

A correct setup fires the conversion on something that only happens when a conversion happens. A thank you page URL. A purchase event pushed to the data layer. A form submission on a specific form. The broken setup fires it on All Pages, which in GTM means the page load event with no condition attached to it at all.

The result is arithmetic rather than opinion. If a site gets ten thousand sessions a month and the conversion tag fires on page load, Google Ads records something close to ten thousand conversions. Your real number might be two hundred.

Why it happens so often

• Somebody was testing. All Pages is the fastest way to confirm a tag fires at all, and it is genuinely the right first step when you are debugging. The mistake is leaving it there once the test passes.
• The thank you page was never identified. Whoever installed the tag did not know which URL represents a completed order, so they picked the trigger that definitely fires.
• The site changed. A trigger pointed at /thank-youstops matching after a replatform, somebody “fixes” it by widening the condition, and the widening goes too far.
• It was inherited. The container was built by an agency three years ago and nobody has opened it since. See auditing a new client's tracking.

What it does to your bidding

This is the part that costs money rather than just credibility. Smart Bidding strategies like Maximise Conversions and Target CPA work by finding more people who resemble the people who converted. If everyone who lands on the site is labelled a converter, the algorithm learns that the ideal customer is anyone who clicks.

So it buys clicks. Cheap ones, from broad audiences, because cheap clicks maximise the thing it has been told to maximise. Your cost per conversion drops to a figure that looks extraordinary, your conversion rate approaches one hundred percent, and your actual revenue does not move. If anything it falls, because budget has been redirected away from the traffic that was genuinely converting.

Google's own documentation is clear that conversion actions should represent a completed, valuable customer action. The system has no way to audit whether you have honoured that. It trusts the signal.

The symptoms, in the order you usually notice them

1. Conversion volume jumps sharply with no campaign change to explain it, often the day after a site update or a tag manager edit.
2. Cost per conversion falls to a number that would be remarkable if it were real. Two dollars on a service that sells for two thousand.
3. Conversion rate sits near the click-through rate, or above fifty percent, which almost no business sustains.
4. The client says the leads have not arrived. This is usually the point at which someone finally looks.

If your platform numbers and your actual sales have drifted apart, this is one of several causes worth ruling out. We go through the others in ad platform revenue versus what actually hit your bank.

How to check it in five minutes

You do not need account access to the ad platform for the first three of these. You do need access to the tag manager container.

1. Open the container and filter by tag type. In GTM, look for tags of type Google Ads Conversion Tracking, Floodlight, or a Custom HTML tag containing a conversion snippet.
2. Read the trigger on each one.You are looking for All Pages, or any page view trigger with no conditions. A trigger named something reassuring like “Conversion Trigger” can still be an unconditioned page load underneath, so open it rather than trusting the name.
3. Check the conditions, not just the event. A page view trigger with a condition such as Page URL contains /thank-you is correct. The event alone is not the problem. The absence of a condition is.
4. Load a page that is not a conversion. Open your homepage in GTM preview mode and watch which tags fire. A conversion tag appearing on the homepage is the whole diagnosis.
5. Confirm in the ad platform. In Google Ads, open the conversion action and compare its count to the number of real orders in the same window. A ratio of fifty to one is not an attribution quirk.

How to fix it properly

The fix is to give the tag a trigger that matches the actual conversion. Which one depends on how the site signals that a conversion happened.

If there is a thank you page

Create a page view trigger with a condition on the URL, and make the condition specific. Page Path equals /thank-you is safer than Page URL contains thank, which will also match a blog post titled “thank you for reading”. Check the URL in an incognito window after a real purchase, because some platforms append order parameters that change the path.

If the site pushes a data layer event

Most modern ecommerce platforms push a purchase event on order completion. A custom event trigger on that event name is the most reliable option available, because it survives URL changes and it carries the order value and transaction ID with it.

If neither exists

Then the honest answer is that the site is not currently capable of accurate conversion tracking, and the job is to add that capability rather than to pick a trigger that approximates it. A form submission trigger on the specific form is usually the quickest path for a lead generation site.

What to do about the data already collected

Fixing the trigger stops the problem. It does not undo it. The conversion action now has weeks or months of inflated history, and Smart Bidding has learned from all of it.

• Expect a dramatic drop in reported conversions the moment you fix it. This is the correct number arriving, not a new problem, but somebody needs to warn the client before they see it. We cover how to have that conversation in explaining tracking issues to clients.
• Expect bidding to behave unpredictably for a week or two while it relearns. Your target CPA was calibrated against a fiction, so it will need resetting against reality.
• Consider whether to create a new conversion action rather than repair the existing one. A clean action has no poisoned history, though it also has no history at all, which matters for campaigns near the volume thresholds automated bidding needs.
• Document the date of the fix. Every report that straddles it will show a cliff, and in six months nobody will remember why.

If the account has been bidding on bad data for a while, the recovery sequence is its own piece of work. We wrote it up in recovering Google Ads after a tracking outage.

Why this one is worth checking today

Most tracking problems lose you information. This one manufactures it, which means every safeguard you have that is based on noticing a number fall over will not trigger. There is no alert in Google Ads for conversions that are too good. Nobody opens a ticket because performance improved.

It is also silent in the way that matters most. The tag is present, the container is published, the conversion action reads as recording, and the reporting is full of conversions. Every box you would normally tick is ticked.

You can check any site for this in about thirty seconds with our free tracking scan. It reads the public source and the published tag manager container, resolves which trigger fires which tag, and tells you if a conversion tag has no condition beyond the page loading. It does not need access to the site or to the ad account, and it is deliberately narrow about this particular finding: a tag that fires on page load and a thank you page condition is a correct setup and is left alone.

Configuration being right today is also only true today. A theme update, a container edit, or a new developer can reintroduce this next Tuesday. Taglert rechecks every connected account every thirty minutes and emails you when conversion tracking changes, so the fix stays fixed.