Why qualified leads aren’t showing in Google Ads
Trace a qualified lead from your CRM through the import and into Google Ads reporting. A worked example shows where to look when the figures differ.
- CRM qualification
- Import processing
- Google Ads reporting
Conceptual guide · not campaign results
Your sales team qualified 40 leads last week, but Google Ads shows 28. It’s tempting to assume Google lost the other 12. Before you change the campaigns, check which leads your integration sent, what Google processed and how you’re counting them in the report. Each check answers a different question, and only one of them might need fixing. This guide covers qualified outcomes imported from your CRM. If website form submissions have stopped recording, check the form tracking first.
Start with one conversion action
Pick one outcome your sales team records consistently. If your conversion action is called Qualified lead, use the point at which an enquiry actually reached that stage in your CRM. An enquiry created on Monday and qualified on Thursday belongs in Thursday’s qualification figures. If you export it on Friday, that gives you a third date. Comparing the wrong two can make a healthy import look broken.
Write down the conversion action, the destination Google Ads account, the period, the time zone and when you pulled each report. Keep a reference for each CRM record in your own secure working file. If your problem is broader than a single conversion action, start by checking why Google Ads, Meta and your CRM report different lead totals.
Find out what the integration sent
Open the file or connector run that should have sent the records. If a lead reached the qualifying stage but never appeared in that submission, check the trigger, stage mapping and filters before opening campaign settings. For example, a connector configured to run when an enquiry is first created may never see a qualification added later. Check the rule against an actual record and confirm it was eligible to send. There may be a good reason it was excluded.
Check what Google processed
Open the import results or offline data diagnostics for your setup. Compare the errors with what was submitted. A timestamp in the wrong time zone, a missing identifier or the wrong destination action can send you down very different paths. Check the actual event time and the requirements for your import method before correcting anything.
If your integration uses the Data Manager API, keep the request ID and the original row order. The initial response tells you the request was accepted for processing. Request diagnostics show the subsequent status by destination. If an error shows a row index of 0, check the first row in the original request. A row can also carry a warning and still be processed. Check the report separately to see how many conversions Google credited to ads.
Check the report before calling a lead missing
In Google Ads, add All conv. (by conv. time) to the campaign report and segment by conversion action. Google recommends this check when comparing imported records with reporting. The regular columns can credit the conversion to the earlier ad interaction. The conversion-time column puts it on the date the outcome happened. Compare the same action, date range and time zone, and give the import time to appear. If the action is secondary, it usually appears under All conversions. Check the action and campaign goal settings, especially if the campaign uses a custom goal.
Even then, the counts may differ. A conversion action set to count One can count only one conversion per ad interaction. And if your enhanced conversions for leads setup sends outcomes from organic or other channels too, Google may not attribute those outcomes to a Google ad. Look into an unexpected shortfall, but don’t assume every CRM record should become a Google Ads conversion.
What the 40-to-28 gap might look like
These figures are illustrative. Assume 40 distinct leads qualified from 19 to 25 October. One conversion action receives only this batch for that period, and the CRM and Google Ads comparison uses the qualification date and the same time zone. The Google Ads figure is a report total, not a list of matched CRM records.
Swipe or scroll horizontally to see the full table.
| Checkpoint | Count | What you can establish |
|---|---|---|
| Leads reached the agreed stage in the CRM | 40 | This is the group to check. Confirm which records were eligible to send. |
| Records in the integration submission | 36 | Four were not sent. Check why before treating any as a fault. |
| Submitted records failed processing | 2 | Use the available error details to identify and fix the issue. |
| Records processed without an error | 34 | Processing succeeded for these records. Attribution is a separate check. |
| Google Ads reported conversions for the action and period | 28 | Six fewer than processed. The total alone cannot tell you which records, or why. |
If you can trace a fault to a connector filter, fix the filter and check a small set of eligible records before rerunning a whole batch. If the imports worked and the difference is in the report dates, fix the comparison. Keep anything you can’t explain open rather than assigning every missing conversion to one cause.
Once you can rely on the numbers, you can decide which lead stage to use for bidding. If you’d like help checking where the figures diverge, talk to us about your Google Ads account.
Need help applying this to your campaigns?
Book a 30-minute discovery call to discuss your campaigns, the problem you want to solve and whether ADdictive can help.
Book a discovery callPrefer email? info@addictivedigital.co.uk