Analytics
Is Your Conversion Tracking Lying? Duplicate Conversions
Updated 7 November 2026·9 min read·MeraSEO, Mumbai
Say you open Google Ads and see 80 conversions at a low cost each. Then you look at your inbox and your WhatsApp and find 25 real enquiries. Somebody is telling a pleasant lie, and it is usually the tracking. This matters beyond the report: Google’s automated bidding uses your conversion data to decide whom to bid for, so a wrong count steers spend toward the wrong users.
This post lists the usual ways conversions get counted twice or counted when nothing real happened, and a testing routine to find them. It covers over-counting. If you have the opposite problem, enquiries that analytics never sees, read reporting SEO results when analytics misses your enquiries. For first-time setup, start with our GA4 setup guide.
With Smart Bidding, Google adjusts your bids auction by auction based on which searches and users led to conversions in the past. If a conversion fires for people who merely loaded a page, the system learns to find more people who load that page. You then see a healthy-looking cost per conversion while real sales stay flat. Fixing the count is usually a better use of an afternoon than rewriting ads. Our guide to Smart Bidding setup makes clean conversion data its first step for this reason.
If your conversion fires whenever the thank-you page loads, anyone who refreshes it, opens it from history or bookmarks it creates another conversion. Staff testing the form create them too. Prefer to fire the conversion from the form-success event rather than the page view, and set the Google Ads action to count one conversion per click (cause 5). For online stores, send the order number as the transaction ID with every purchase: GA4 and Google Ads both use it to drop a repeat of the same order when someone reloads the order-confirmation page. In GA4, define your office IP addresses as internal traffic and turn the filter on, so staff tests stop counting.
This is the most common cause on sites that use both Google Ads tags and GA4. Suppose you have a Google Ads conversion tag for form submits and you also import a GA4 key event for form submits into Google Ads. If both are set as primary conversion actions, one enquiry is counted twice. Check the conversion list in Google Ads: for each real-world action there should be one primary source. Others, if kept, should be secondary so they report without influencing bidding.
A key event defined as “page_view where the URL contains /contact” counts everyone who opens the contact page, not those who submit. Define the event on the action itself, such as a successful form submission.
A generic “form submit” trigger in Google Tag Manager can fire when someone clicks the button, even if validation fails because the phone number was missing. The person retries, and you have two conversions for one lead. Use a trigger tied to the success message, a redirect to a success URL, or the form plugin’s own success event. On WordPress this matters a lot: popular form plugins such as Contact Form 7 and Elementor Forms send the form in the background without a normal page submit, so the built-in Form Submission trigger, even with its “Check Validation” option ticked, may fire on every click or not at all. Contact Form 7, for example, fires a “wpcf7mailsent” browser event only after the mail is sent, and a small listener in GTM can turn that into your conversion event.
Google Ads lets you count every conversion from an ad click, or only one. For lead generation, one enquiry per click is normally right, because a person who submits three times is still one lead. “Every” suits purchases, where several separate orders from one click each have value.
A tap on a WhatsApp button means interest, not a conversation. If every tap is a primary conversion, you pay for accidental taps and for people who never send a message. Track it as a secondary action, or give it a low value, and keep the primary conversion for something stronger, such as a form submit or a call over a minimum length. The same goes for taps on a tel: link: GTM can only see the tap, not whether the call happened. Google Ads can count calls with a minimum call duration, but only for calls it can measure through its call reporting, which shows a Google forwarding number in place of yours. Some owners prefer not to show an unfamiliar number to customers; in that case keep tel: taps secondary.
| Symptom | Likely cause | Check |
|---|---|---|
| Conversions are about double the real enquiries | Ads tag plus imported GA4 event, both primary | Conversion actions list in Google Ads |
| Conversions with no matching lead | Page-view trigger or reloads | Open the thank-you URL directly, count what fires |
| Duplicate conversions per lead | Form trigger fires on errors | Submit an invalid form in Preview mode |
| Low-quality traffic gets cheaper “conversions” | WhatsApp taps as primary | Compare taps to messages actually received |
| Same-session repeats | Counting set to “every” | Conversion action settings |
A note on GA4 key events versus Google Ads conversions: on our own GA4 property, WhatsApp “click to chat” and contact-link clicks are marked as key events. That is fine for reporting inside GA4. Whether those events should also train bidding is a separate choice you make in Google Ads, and for taps the answer is usually “secondary”.
Here is an illustrative example of a pattern that is easy to fall into (the numbers are made up to show the method). A Mumbai clinic runs search ads. Google Ads reports 60 conversions in a week. The front desk logged 22 appointment requests. An audit finds two things. First, the thank-you page fired a Google Ads form tag, and a GA4 form key event imported into Google Ads was also set as primary: every form counted twice. Second, “click to call” taps were primary, and the mobile page showed a sticky call button that visitors often touched while scrolling.
The fix: keep one primary form conversion, set the imported duplicate to secondary, move the call-button taps to secondary (or, if the clinic accepts a forwarding number, count only calls above a minimum duration), and set counting to one per click. After a week, reported conversions fell sharply, which looked worse on paper but matched the front desk much better. Only then does it make sense to adjust bids, because the system now optimizes toward real appointments. If you want an outside review of an account, our PPC audit and optimization service includes a conversion tracking check.
Tracking changes usually need to be done with care in Tag Manager. If you want it done properly, see our GA4 and Google Tag Manager setup service.
Usually because one action is counted more than once: a Google Ads tag and an imported GA4 key event both set as primary, a thank-you page that reloads, or a form trigger that fires on errors. Check the conversion actions list, then test each action in Tag Assistant.
Either can work, but avoid counting the same action through both as primary. Pick one source for each real action, and set the other to secondary if you want to keep it for reporting. What matters is a single, consistent definition of what counts as a lead.
Use Google Tag Manager Preview mode and GA4 DebugView together. Perform each action once, including an invalid form submission, and confirm the event fires once with the right name. Then compare a week of reported results with your real enquiries.
Not by itself. A tap shows interest, but many people tap and never send a message. Track it as a secondary action or a low-value one, and use a form submit, or a call that Google Ads measures above a minimum length, as the primary signal that trains bidding.
We audit GA4, Tag Manager and Google Ads conversion settings and clean up duplicates before you spend more.
Get a tracking review →WhatsApp us