Key facts
- A thank you or confirmation page tag fires again every time that page loads, which means a page refresh, a back button return, or a bookmarked confirmation page can each register as a brand new conversion.
- Running a GA4 conversion tag and a separate native Google Ads or Meta conversion tag on the same page, without linking them, records the same real action twice under two different systems.
- Google Tag Manager's preview and debug mode shows every tag that fires on a given page load in order, which makes it the fastest way to see two tags firing for one event.
- Enhanced Conversions and a standard conversion tag are meant to work together on the same action, not as two separate conversions, and misconfiguring the setup can cause both to report independently.
- A single page acting as the confirmation step for more than one form, or embedded in an iframe that also carries its own tag, can trigger the same conversion tag from two different contexts on one visit.
The Confirmation Page Is the Most Common Cause
If your conversion tracking depends on a visitor reaching a thank you or confirmation page, that page's tag fires every single time the page loads, with no built in way to know whether this is the first time or the fifth time a given visitor has landed there. A refresh, a browser back button press after checking the confirmation, or a bookmark saved to that page can each generate another recorded conversion for an action that only happened once.
This is especially common on slower connections, where a visitor refreshes a confirmation page that looks like it has not finished loading, unaware that the refresh just logged a second conversion behind the scenes. It also shows up heavily on mobile, where accidentally tapping back and forward while checking a confirmation is a common, harmless seeming habit that quietly inflates the count.
The fix is to track the action itself rather than the page load. A form submission event, tied to the actual submit action through Google Tag Manager, fires once per genuine submission and ignores page refreshes entirely, which removes this entire category of double counting without needing to change the page.
Two Tags Tracking the Same Real Event
The second common cause is having more than one independent tracking tag fire for the same real world action. This often happens when a business sets up GA4 conversion tracking directly, then later adds a native Google Ads conversion tag to the same button or page without realizing GA4 conversions can already be imported into Google Ads as a separate, connected conversion action. Both tags fire for the one real form submission, and if both are also imported or counted as primary conversions, the reported total effectively doubles.
A similar overlap happens when Enhanced Conversions is layered onto an existing setup incorrectly. Enhanced Conversions is meant to strengthen the match quality of the conversion you already track, not to exist as a second, separate conversion event running in parallel to the original tag.
Use Google Tag Manager's preview and debug mode to load the page that triggers a conversion and watch, in order, exactly which tags fire. Two conversion tags firing for one button click or one page load is visible immediately in that view, and it tells you precisely which two tags need to be reconciled into one.
Confirm It With a Real Test, Not a Guess
Run a single, deliberate test conversion and count how many times it registers everywhere it could possibly show up: GA4's real time report, the Google Ads conversions column, and any CRM or email notification tied to the form. Submitting one test lead and comparing the count across all three systems tells you immediately whether the duplication is inside one platform's tag firing twice, or across two platforms both counting the same action once each.
Check the conversion action's count setting in Google Ads specifically. Some conversion actions are set to count 'every' conversion rather than 'one' per click or session, which is appropriate for purchases where a customer might buy twice, but is exactly wrong for a lead form, where every legitimate submission should represent one unique interested person, not a running tally inflated by refreshes.
Also check whether the site has more than one instance of Google Tag Manager installed, which happens occasionally after a website migration or a platform change where an old tag was never removed before a new one was added. Two live containers on the same page will each fire their own copy of every tag defined inside them.
Fixing It and Keeping It Fixed
Once you know which pattern applies, the fix is usually specific and quick: switch the trigger from a page load to the actual submit or purchase event, set the conversion count setting to match the real business action, and remove or properly link any duplicate tag rather than letting both run independently. Document which tag owns which conversion so a future website update does not accidentally reintroduce a second copy.
Double counted conversions are not just a reporting nuisance. An automated bid strategy learns from conversion volume, and feeding it artificially inflated numbers teaches the algorithm the campaign is working better than it actually is, which can push spend toward searches and audiences that are not really converting at the rate the dashboard suggests.
SearchPod audits conversion tracking as a standard part of every Google Ads account takeover, checking exactly this kind of duplication before making any bid or budget changes. Managing the account afterward runs 10% of the ad budget, floored at $600 monthly for Canadian clients and $450 for US clients. Request one through /get-proposal and a free proposal usually comes back the next business day.
Related questions
Submit one deliberate test lead or purchase, then check how many times it appears in GA4 real time reports, the Google Ads conversions column, and your CRM or inbox notification. If one real action shows as two or more conversions in any single system, or is counted independently by two systems that were never linked together, that confirms double counting rather than a coincidence.
Pick one path for each action and stick to it. Importing a GA4 conversion into Google Ads is a common, supported setup, but only if the equivalent native Ads tag is removed or excluded from primary conversions. Running both as separate primary conversions for the same action is what causes the double count in the first place.
If the conversion tag is tied to the page loading rather than to the actual form submission event, yes, every refresh fires the tag again. Switching the trigger to the submit event itself, set up through Google Tag Manager, fixes this permanently, since a refresh does not resubmit the form and therefore does not refire an event based trigger.
Usually yes, since you are removing conversions that were never real. This is a good outcome even though the number looks worse at first glance, because it means your true cost per lead and true conversion rate become visible again, which lets you and any automated bidding actually make accurate decisions instead of chasing an inflated number.
Yes. Automated bidding strategies use conversion data to decide which auctions to enter and how much to bid. Inflated conversion counts can convince the system a campaign, keyword, or audience is performing better than it really is, which can push budget toward traffic that looks productive on paper but is not actually producing that many real customers.
Want a second opinion on your situation?
Get a free, no-obligation proposal. We’ll look at your site and your market and tell you honestly what we’d do — and what we wouldn’t.
Get your free proposal