Why does my conversion tag fire on every page instead of just the thank you page?

A conversion tag fires on every page when its trigger is not limited to the thank-you page – usually because it uses the All Pages trigger, a condition that matches every URL or a wildcard event trigger. The fix for a conversion tag on every page is one precise trigger per conversion: a page view with Page Path equals /thank-you/ or, better, an event your form sends only after a successful submission.

Every extra conversion tells Smart Bidding that a visitor converted who did not, and the bidding chases the wrong people. If Google Ads reports far more conversions than you receive enquiries, also read why Google Ads shows more conversions than you actually have.

Why does a conversion tag fire on every page?

• All Pages trigger. It fires on every page view, so every visit counts as a conversion.
• A condition that matches too much. “Page URL contains /” behaves like All Pages; “contains thank” also catches a blog post about thank-you notes.
• Wildcard custom events. Google warns that the regex .* makes a trigger “execute on all detected events”. Since 8 October 2026, gtag('config') commands also appear in the data layer as gtag.config events, and according to the Tag Manager release notes wildcard custom event triggers may then fire tags.
• Several triggers on one tag. Each trigger fires the tag on its own, so one enquiry can count two or three times.
• Click instead of success. A click trigger on the send button also counts empty or invalid submissions.
• URL rules in Google Ads. A conversion action set up with a URL rule such as “URL contains” counts every page that matches, without GTM being involved.

How do you limit the trigger to the thank-you page?

1. Open the conversion tag in GTM and note every trigger under Triggering. One conversion should have one trigger.
2. Create a new trigger: Triggers → New → Trigger Configuration → Page View. Under “This trigger fires on”, choose Some Page Views and add Page Path equals /thank-you/. Google uses the same pattern in its trigger recommendations.
3. If your form shows a success message without loading a new page, use a Custom Event trigger. Your site pushes dataLayer.push({'event': 'form_success'}) after a successful submission, and the trigger listens for exactly that name, without regex.
4. With the Form Submission trigger, tick Check Validation. Google says the trigger then fires only if the form is successfully sent; without it, every submit attempt counts, including those that fail validation.
5. Remove the old triggers from the tag, save, test in Preview and publish.

Thank-you page or success event?

A page view on /thank-you/ is easy to set up, but visitors can reload, bookmark or open that page directly, and each view counts again. An online shop had its contact form tag on three triggers at once: the visibility of the success message, a page view of /thank-you that anyone could open, and the form plugin’s “mail sent” event. We left only the event.

Two settings in Google Ads limit the damage. Pass a unique enquiry or order number into the tag’s Transaction ID field: if two conversions for the same action share a transaction ID, Google Ads does not count the duplicate. For leads, set Count to One (Goals → Conversions → Summary → conversion action → Edit settings), which counts “only one conversion per ad click”. This hides the problem rather than fixing it: with a tag on every page, every ad visitor still counts once.

What did a client case with 1,040 Ads conversions and 345 form submissions show?

A retail client’s Google Ads account reported 1,040 contact form conversions in 30 days, while GA4 counted 345 successful submissions in 28 days from all sources. The Ads tag fired on the click on “SEND”, the GA4 tag only when the success message appeared. On 17 July 2026 we moved the Ads tag to the same success trigger. Ads form conversions fell from 40.7 to 18.3 a day; GA4 stayed at 14.6 and 15.0 a day, so the real number of enquiries did not change. The account’s cost per conversion rose from €12.30 to €23.60. That looks worse but is honest. On the same day phone and email clicks became secondary conversions, which explains part of the jump.

How do you test the fix with Tag Assistant?

1. Click Preview in GTM and connect your site.
2. Open two or three normal pages. Select each page view in Tag Assistant: the conversion tag must appear under the tags that did not fire.
3. Submit the form with a required field left empty. The tag must not fire.
4. Submit a valid test enquiry. The tag now fires exactly once.
5. Reload the thank-you page. With an event trigger nothing happens; with a page view trigger the transaction ID must stay the same.
6. After publishing, compare Google Ads with GA4 or your enquiry inbox for a week, allowing for conversions that arrive a few days after the click.

Count the success, not the attempt. Give every conversion tag exactly one trigger, ideally an event that fires only after your server has accepted the form. Pass a unique ID as transaction ID, set lead conversions to Count: One and compare the daily numbers with your enquiries before you let Smart Bidding work with them.

Sources

• Tag Manager Help: Best practices for trigger configuration
• Google Ads Help: Use a transaction ID to minimize duplicate conversions
• Google Ads Help: About conversion counting options

Do your conversions match your real enquiries? We check triggers, conversion actions and counting settings and fix what inflates the numbers. Book a free initial call or see how we handle Google Ads and conversion tracking for our clients.