The short answer
When Google Ads shows far more conversions than real leads, it's usually counting the same lead more than once. The common causes are two conversion actions both set to Primary (often a Google Ads tag plus an imported GA4 key event), a lead action set to count "Every" conversion, or a tag that fires twice. Split the Conversions column by conversion action to see which one is inflated, then fix that action's settings or remove the extra tag.
The usual causes
A "conversion" in Google Ads is any action you've told it to count, such as a form sent, a call or a purchase. Every action set to Primary lands in the same Conversions column. So the column can climb well past your real leads without a single fake visit.
| Cause | What happens | The fix |
|---|---|---|
| Two actions for one lead, both Primary | A Google Ads tag and an imported GA4 key event each count the same form | Keep one as Primary, set the other to Secondary |
| Lead action counting "Every" | One person who sends the form three times counts three times | Set the action to count "One" |
| The same tag twice | A snippet in the theme plus a tag in Tag Manager, or a plugin plus Tag Manager | Remove one copy |
| One tag on click, one on submit | Both fire on the same press of the button | Keep the submit trigger only |
| Tag on a thank-you page | Each reload, or a return to the page, fires it again | Count "One", or add a transaction ID |
Google's own defaults make the second row easy to hit. "Every conversion" is the default for website actions, and Google recommends "One" for leads. Google says "One" counts "only one conversion per ad click".
What the browser sent when we tried each one
On 11 November 2026 we built a test page with Google's real tag (gtag.js) for a made-up Google Ads account and GA4 property. One visitor went through six setups: four where a form was sent, and two where the thank-you page was loaded and then reloaded.
We recorded every hit to Google and stopped it before it left the browser, so nothing reached a real account.
| Setup | Conversion hits sent to Google Ads | Also sent |
|---|---|---|
| One Ads tag on submit | 1 | |
| The same Ads tag twice | 2 | |
| One tag on button click, one on form submit | 2 | |
| Ads tag plus a GA4 key event | 1 | 1 generate_lead to GA4 |
| Tag on the thank-you page, page reloaded once | 2 | |
| The same, with a transaction ID | 2, both carrying the ID lead-1042 |
The browser didn't deduplicate anything. In every doubled setup, it sent two conversion hits with the same conversion label. Whether the second one counts is decided inside Google Ads.
Any clean-up happens inside Google Ads. A transaction ID marks the second hit as a copy, within one conversion action: "If there are 2 conversions for the same conversion action with the same transaction ID, Google Ads will know the second conversion is a duplicate." The "One" setting also works inside a single action.
Neither helps with the GA4 row, which sent one hit to Ads and one to GA4. Import that GA4 key event into Google Ads, make both actions Primary, and Ads counts two actions for one lead.
A GA4 conversion created from the Analytics side starts as Secondary, and only Google Ads can switch it to Primary, so check what yours is set to.
Find yours in ten minutes
- In Google Ads, open your campaigns and segment by conversion action (Segment › Conversions › Conversion action). Each action now gets its own row.
- Compare each row with your real leads for the same dates. An action that matches is fine. One that runs at double, or one you don't recognise, is the problem.
- Under Goals › Conversions › Summary, open each action and check two settings: its optimisation (Primary or Secondary) and its Count.
- To see whether a tag fires twice, send a test form with your browser's developer tools open on the Network tab, filtered to
pagead/conversion. One press should send one hit.
The r/PPC owner who asked about 267 conversions against 53 leads had a gap of about five to one. A single tag firing twice gives two to one. A gap that wide usually has more than one cause, often several actions landing in the Conversions column, so step 1 is where to start.
Fixes, in order
- One Primary action per real outcome. If a GA4 key event and a Google Ads tag both track the form, pick one. Set the other to Secondary so it still shows in "All conversions" but stops feeding the Conversions column and bidding.
- Count leads as "One". Leave purchases on "Every".
- One tag, one trigger. Search your theme, plugins and Tag Manager for your conversion ID (
AW-followed by numbers) and keep a single copy, fired on submit. - Add a transaction ID where a thank-you page can be reloaded. Use a real order or lead number that's unique each time.
GA4 can double-count forms for its own reasons. When enhanced measurement's form tracking is on, GA4 sends form_submit whenever a form is sent, so a form that also sends your own generate_lead produces two events. Mark only one of them as a key event, and check its counting method: "Once per event" counts every time it fires.
When it isn't a duplicate
Some gaps come from timing. Google Ads files a conversion under the date of the ad click, so October can include leads that arrived in November. The Conversions column can also hold modelled conversions for people who declined cookies. Our piece on why GA4, Google Ads and Meta don't match covers both.
Spam is the other one. A form filled by a bot is a real submit, so the tag fires and Ads counts it. If your CRM throws those leads away and Ads keeps them, the gap is spam.
Where TagSentry fits
Fixing a double count means deleting tags, and the risk is deleting the one that worked. Then the problem flips: conversions drop to zero, and nobody tells you.
Event monitoring lists which events fired and every platform the browser sent them to, Google Ads included. Save your form's event (say generate_lead) as a key event and TagSentry emails you once if it stops arriving, and once when it's back. It's one line of code above Google Tag Manager, free up to 250,000 events a month.
If your count fell instead of rising after a cookie banner went live, start with Google Ads conversions that dropped with Consent Mode.
Sources
- Google Ads Help: About conversion counting options
- Google Ads Help: Use a transaction ID to minimize duplicate conversions
- Google Ads Help: About primary and secondary conversion actions
- Google Ads Help: Create conversions from Google Analytics events (why numbers differ)
- Google Ads Help: About consent mode modeling
- Analytics Help: Change the counting method of key events
- Analytics Help: Enhanced measurement events