The Google Ads backend shows conversions, but the sales team reports that the quality of the leads is poor? Or there is obviously a form submission, but the background conversion is zero? Inaccurate conversion data is one of the most common problems with global expansion advertising, which directly leads to the bidding strategy being biased in the wrong direction and wasting a lot of budget. Starting from the attribution logic, this article systematically sorts out the six major causes of inaccurate conversion data and the corresponding repair methods.
6 common reasons why conversion data is inaccurate
1. Conversion code not firing correctly
The most common cause is that the Google Tag or conversion event tag isn't firing at the right time. Common problems include: the code is installed on the thank you page but the URL of the thank you page is not fixed, the code is installed on a button click but the page jumps directly after the click and there is no time to send the event, and the code is incorrectly blocked by other scripts.
Troubleshooting methods: Use Google Tag Assistant (Chrome plug-in) to record a complete conversion behavior and check whether the event is triggered correctly. Or use the Network panel of the browser developer tools to filter the "google" request and confirm whether the conversion hit is issued.
2. The conversion window setting is unreasonable
Google Ads default conversion windows are 30 days (clicks) and 1 day (views). If a customer has a long decision cycle (e. g. enterprise purchases typically take 60-90 days), a short window will miss a lot of real conversions.
Fix: Enter Google Ads → Tools → Conversion → Edit conversion window, and adjust the click conversion window to 60 or 90 days to match the actual sales cycle.
3. Wrong choice of attribution model
Google Ads currently supports multiple attribution models: last click, first click, linear, time decay, and data-driven. If you use the "last click" model, all conversion credit will be attributed to the last touch point, which will seriously underestimate the value of brand words and top-level ads.
suggestion: For accounts with a certain amount of data (> 50 conversions per month), switch to "data-driven attribution" and let machine learning automatically assign the credit weight of each touch point.
4. Double counting conversions
If the same conversion event is deployed in both Google Tag Manager and Google Ads tags, the number of conversions will be inflated. Commonly seen in: coexistence of new and old code after website revision, tag manager configuration error causing the event to be triggered twice.
Troubleshooting methods: Check the "Conversion Source" in the Google Ads conversion list to confirm that no multiple data sources are reporting the same event at the same time. Use Tag Assistant to record and check the number of event triggers corresponding to a single behavior.
5. Missing cross-device conversions
Users watch ads on mobile phones and complete forms on computers. This cross-device behavior is difficult to fully attribute without the support of login data. This will lead to the conversion value of mobile advertising being underestimated.
solution: Enable Google's Enhanced Conversions to improve the accuracy of cross-device attribution through hash comparison of user email and other information.
6. Technical issues with official website landing page
Some pages use iframe embedded forms, and events within the iframe cannot be captured by the Google Tag of the parent page. In addition, route switching in SPA (Single Page Application) does not trigger standard page load events and will also cause conversion tracking to fail.
Fix: For iframe forms, event callbacks need to be installed on the form provider side to notify the parent page through postMessage. For SPA, you need to use GTM's History Change trigger.
CAPI: A long-term solution for server-side conversion tracking
Client-side tracking is increasingly disrupted by browser privacy policies (ITP, ETP) and ad blockers. The Conversion API (CAPI) launched by Google allows conversion data to be reported directly to Google from the server side, bypassing client limitations.
For accounts with a monthly consumption of more than 100, 000 yuan and high requirements for the accuracy of conversion data, it is recommended to deploy CAPI and Google Tag in parallel to form a "dual-track reporting" structure, and Google will automatically remove duplicates. This is the solution with the highest data accuracy currently.
Quick Self-Check Checklist
- ☐ Whether the conversion event code is correctly installed on the thank you page/trigger point
- ☐ Does the conversion window match the actual sales cycle?
- ☐ Whether the attribution model is appropriate for the current account stage
- ☐ Whether multiple codes are reported repeatedly for the same event
- ☐ Whether to enable enhanced conversions to supplement cross-device data
- ☐ Whether there are technical tracking vulnerabilities caused by iframe or SPA
If there are abnormal conversion data in your Google Ads account, it is recommended to conduct a systematic tracking audit. Provided by SeaSeekFree Google Account Diagnostic Service, can help you quickly locate the root cause of data inaccuracy and provide specific repair plans.
