How to Measure Qualified Leads From Google Ads

Keep measuring enquiries, but give qualified leads a separate definition and a separate record. A successfully submitted form is useful evidence that your landing page works. It cannot tell you whether the business can serve the person who submitted it, whether the sales team reached them, or whether the enquiry became a sale.

The distinction matters when two campaigns produce similar submission counts but very different sales conversations. Before asking which campaign deserves more budget, check whether both are being judged at the same stage of the funnel. A cheaper enquiry is only cheaper at that particular stage.

This guide starts with the decision a business can make before touching its ads account: what would the sales team agree to call a qualified lead? Once that is clear, you can work out whether the CRM records it reliably and whether the signal belongs in Google Ads at all.

What should count as a qualified lead?

Choose a rule that a colleague can apply without guessing. For a fictional equipment servicing company, a qualification rule might require that the enquiry concerns a supported machine, comes from an area the team serves, and has been confirmed in a conversation. Another company might require an agreed discovery meeting. The useful rule is the one that describes your sales process.

Separate the evidence of contact from the evidence of fit. A disconnected number, a duplicate enquiry and a genuine prospect who has not yet answered are different cases. If every unreviewed lead is marked unqualified, your report starts measuring how fast the team reviews its inbox. If every person who answers is marked qualified, the report misses whether you can actually help them.

Google’s qualified and converted lead guidance distinguishes a lead assessed outside Google Ads from one that has completed a chosen later step. These are categories for describing outcomes you already record. Selecting the category does not determine whether a particular enquiry meets your own rule.

Stage	Evidence to record	What it helps you decide
Enquiry received	A distinct, accepted enquiry in the system	Whether people complete the contact step
Contact attempted	A call or follow-up was attempted	Whether the team is working the queue
Contact made	A conversation or substantive reply	Whether enquiries are reachable
Qualified	The agreed fit criteria were met	Whether campaigns bring people you can serve
Converted	A defined outcome such as a signed order	Whether the funnel produces business
Not yet reviewed	No assessment has been made	Whether the reported quality figures are mature enough to use

A reason code makes rejection useful. An enquiry outside your service area calls for a different investigation from a valid lead that nobody called. If response is the issue, start with our lead response guide before assuming the campaign is sending the wrong people.

What should your CRM keep that an ad report cannot?

Give each enquiry a stable reference. Keep the time it arrived, its source where known, and the time it reached each stage. Preserve the fact that a lead was reviewed as well as the outcome. A system that overwrites the original enquiry date with the latest edit date makes it difficult to compare cohorts or understand delays.

Choose what counts as one lead. If someone submits twice and then calls, your team may want one opportunity with several interactions rather than three separate opportunities. Decide how sales staff merge duplicates and how the measurement pipeline recognises the same stage change after a retry. Re-exporting a record after a spelling correction should not create another qualified lead.

For a first check, take one recent period and reconcile the CRM’s enquiry count with the accepted submissions recorded by the website. Review examples that appear on only one side. If a form says thank you before a record has been saved, or if a CRM integration discards a failed write, neither campaign targeting nor a new conversion action will repair that gap.

Keep room for enquiries that cannot be attributed. An unidentified source is still a business enquiry. Do not assign it to Google Ads because it arrived during a campaign. A CRM should remain a complete record of the business’s work, including rows that an ad platform cannot match.

When does it make sense to import outcomes?

A manual review can answer the first budget question. Use a consistent qualification rule and compare mature cohorts by source. For a small operation, this may be enough to identify a gap in follow-up, landing page wording or targeting without building an import.

An import becomes useful when the CRM produces repeatable stage events and the business wants to measure attributable outcomes inside Google Ads. Google’s enhanced conversions for leads overview explains how permitted user-provided data can supplement offline matching. It is an attribution mechanism. It cannot validate your qualification rule, and a successful import does not mean every record will be attributed.

Use the current route for your setup. Google’s offline conversion developer documentation says new API implementations must use the Data Manager API rather than starting a legacy offline upload integration in the Google Ads API. Check the current eligibility of an existing integration before changing it. A connector or Data Manager workflow may already meet the need without custom development.

Review data eligibility before sending anything. Google’s customer data policies restrict measurement of sensitive conversion categories in enhanced conversions, including health and medical information. Hashing does not make restricted data eligible. Keep excluded outcomes in your own business reporting, and leave free-text notes and unnecessary customer information out of any export.

How do you verify the signal before using it?

Start with one stage and a clear rule for when to export it. Compare the CRM count for eligible events with the number sent, the number accepted and any reported errors. Then look separately at attributed conversions. Those counts describe different steps, so matching two numbers in a dashboard does not prove that the pipeline works from end to end.

Check a small set of representative cases in an approved test setup: a normal qualification, a duplicate submission, an event sent again after a failed import, and a record that should be excluded. Confirm the integration records the time the outcome happened and does not change it each time the record is exported. Agree who will check failures and how the team will correct them without blindly repeating a batch.

When you compare campaigns, allow time for sales to review the leads. If one campaign ran last week and another ran last month, the older group may simply have had more time to qualify. Use cohorts defined by enquiry date and apply the same review window. Track the number still awaiting assessment instead of silently treating those leads as failures.

A useful summary includes cost per enquiry, cost per qualified lead and the share of enquiries assessed. Define the campaign spend and which cohort is included before dividing. Keep the underlying counts visible. A change from one qualified lead to two is worth looking at, but it is a thin basis for a budget decision.

For example, suppose two sales teams use the same CRM stage name. One marks a lead qualified after checking service fit; the other marks it qualified whenever a call connects. Before combining their numbers, review a few records together and agree which evidence is required. If the definitions remain different, report the teams separately until the process is consistent. The import can faithfully deliver both labels while the comparison remains wrong.

Should qualified leads replace form submissions in bidding?

Not until the deeper signal is dependable. Keep form submissions visible for diagnosis: a fall there can help explain whether a later problem begins at the landing page or further down the funnel. Before changing bidding, check whether the team applies the rule consistently, how long qualification takes and whether enough relevant outcomes arrive to make the signal useful for that campaign.

Review the actual campaign goals. Google’s primary and secondary conversion guidance explains that primary actions can be used for bidding when their standard goal is selected. Secondary actions are normally for observation, but a secondary action included in a custom goal can be used for bidding. Check the campaign’s goal configuration rather than relying on the label alone.

Do not count every milestone as a separate sale when you read the results. One person may submit, qualify and sign an order. Measuring each stage is useful. Adding them together and presenting the total as customers makes it impossible to judge the campaign. Pick the outcome you are trying to optimise and explain which other events remain in the report for diagnosis.

When should you leave the integration alone?

Hold off if the team cannot agree what qualifies, if many leads remain unreviewed, or if you cannot verify that the proposed data is eligible for import. Fix those issues first. A manual review of a comparable group of enquiries can be more informative than a fully automated feed of inconsistent outcomes.

If the CRM already answers the budget question, there may be no reason to build anything. If the gap is real, our paid advertising team can review it alongside the campaign’s measurement setup. Tell us which lead stage you can verify today. A description of the process and anonymised counts is enough to start.