- Published
- Nov 15, 2026
- Reading time
- 10 min read
Google Ads Conversions vs Qualified Leads: Reconcile Local Actions
Separate Google Ads local actions, website events, qualified leads and sales. Reconcile conversion actions and campaign goals before changing bids.

In this guide (8 sections)
When Google Ads reports many more conversions than the number of qualified leads in a CRM, first identify which conversion actions contribute to the report and which goals the campaign uses. A Google Ads conversion is a configured, attributed action. It is not automatically a unique person, a completed lead form, a qualified lead, a store visit or a sale.
This difference is especially important when location assets or Google-hosted surfaces contribute local actions such as directions or call interactions. Those actions can represent useful local intent, but they are not the same event as a website form submission or a lead that passed the business's qualification process. Before changing bidding, map each action to its source, reporting role and business stage.
A recent advertiser question described 436 reported conversions over nine days and seven actual lead-form submissions. The author attributed 403 reported actions to Maps-side activity and 33 to website actions, and also mentioned a domain migration and offline qualified-lead goals. These account figures are self-reported; the account settings and event records were not available for independent verification. The post is a prompt for this reconciliation workflow, not evidence that local actions are invalid or that the campaign optimized incorrectly.
First define each conversion population#
Google Ads can show multiple conversion columns and action groupings. Record the exact report and metric before comparing its total with a CRM or lead spreadsheet. “Conversions,” “All conversions,” a local action row, a website event, an imported offline action and a qualified CRM lead answer different questions.
| Population | Example event | Evidence that defines it | What it does not prove |
|---|---|---|---|
| Ad interaction | Click on an ad | Ads report, campaign, date basis and account time zone | A site session, call or lead |
| Local action | Directions request or call interaction associated with a location | Local-action type, eligible campaign, location asset and report row | That a visit occurred, a call connected, or a lead qualified |
| Website action | Form-completion event or purchase event | Actual event definition, deployed tag and destination | That the action represents a unique person or accepted lead |
| Lead submitted | Enquiry received by the advertiser | Form or CRM record, received time and duplicate policy | That the lead met the business qualification standard |
| Qualified lead | Enquiry meeting documented criteria | CRM stage, criteria, owner and qualification timestamp | That Google Ads attributed it to an eligible interaction |
| Sale or booked job | Completed transaction under a stated business rule | Order/booking record, status, value and time zone | That every sale should appear as an ad conversion |
One person may create several events in that path. For example, someone might request directions, later visit a site and submit a form. A local action and a form could both be useful signals without being duplicate events. Another person may submit two enquiries that the CRM later merges. The metric dictionary should state whether the business reports events, unique enquiries, people, accounts, qualified opportunities or closed sales.
Google describes local actions as interactions associated with a business location, and the reporting and bidding availability can depend on the action and campaign type. Check the current action-level documentation and the settings in the account; do not infer bidding eligibility from the total or assume every local action is treated alike. See Google Ads’ local action conversion guidance.
Make the next tracking test reproducible.
Use the ungated QA checklist to record event rules, consent, duplicate sends and the report you expect to change.
Read the tracking QA checklistOpens a practical guide. No email required.
Check the campaign goal and conversion columns#
A conversion action being marked Primary does not, by itself, settle whether a particular campaign uses it as an optimization goal. Google's primary and secondary action guidance explains that primary actions are used for the Conversions column and bidding when the applicable standard goal is selected. Secondary actions generally appear in All conversions for observation, while a selected custom goal can include actions that otherwise would be secondary.
For the affected campaign, capture these settings together:
- The exact conversion action, source, category, status and event definition.
- Whether it is Primary or Secondary, and whether that label changed during the date range.
- The campaign's selected standard or custom goal and its included actions.
- The report column: Conversions, All conversions, or another named measure.
- The action's count setting, attribution window and date basis.
- The account and campaign time zones, report filters, segments and extraction time.
- Any effective dates for a goal change, tag release, domain migration or import.
Then export action-level rows for a completed period. Google’s conversion goal documentation and Results reporting reference explain why column and goal selection matter. Retain screenshots or exports of the current configuration before making changes. A report with 436 conversions does not identify the action mix or bidding target unless the corresponding rows and campaign goal are visible.
Reconcile local actions, website events and CRM outcomes#
Build a table with one row per action. Avoid a single “lead” total until the event semantics are understood.
| Action | Source | Business stage | Reporting/bidding role | Reconciliation key |
|---|---|---|---|---|
| Directions | Google-hosted local surface | Local intent | Confirm action availability and campaign goal | Action type and attributed date; not a CRM person ID |
| Call interaction | Ad, website or call system, depending on setup | Call intent or call outcome | Confirm the configured call action and qualification rules | Call record or platform action ID where available |
| Website form submit | Website tag or linked event | Enquiry received | Confirm the successful form boundary and campaign goal | First-party enquiry ID, with duplicate rule |
| Offline qualified lead | CRM import | Lead meets stated criteria | Confirm upload action, matching key and attribution state | CRM lead ID plus upload result; store private identifiers securely |
| Closed sale | Commerce/CRM outcome | Transaction completed | Decide whether and how the campaign uses this action | Order/opportunity ID, status and currency |
These keys will not always join perfectly. Google Ads attribution, privacy restrictions, cross-device behavior, ad interaction dates, CRM timestamps and business identity rules can produce unmatched records. Report the unmatched population rather than assigning every unjoined lead to an ad or calling it a tracking failure.
Use a fixed, completed date range and keep the time zone visible. If a standard campaign report is organized by ad interaction date while the CRM uses lead-received time, compare the right date basis or document the remaining difference. If the report includes more than one conversion source, segment by action before considering a total. Where an offline import is involved, use its row-level diagnostics and the separate offline conversion troubleshooting guide; the campaign summary alone cannot prove that every uploaded lead was accepted and attributed.
Audit a domain migration without assuming it explains the gap#
A domain migration can affect the website action path, but the timing alone does not prove causation. Test the live journey from the landing page through a successful form response and check whether the intended website event fires once at the real success boundary. A submit-button click is not necessarily a completed submission. Record the released GTM/container version, destination ID, form route, consent state and test time.
Compare the old and new domains for:
- The live Google tag or integration and its destination/action identifiers.
- The form's actual success route or server response, including redirects and embedded forms.
- Cross-domain or referral behavior that could change session attribution, where applicable.
- Consent configuration and any tag blocking or delayed event dispatch.
- Duplicate mechanisms, such as a native Ads tag plus an imported Analytics action for the same outcome.
- Offline imports, including whether the imported action represents a later funnel stage rather than another form submission.
A debug preview can help test a draft container, but it does not show that the same configuration is on the published site. Use the actual deployed journey and a safe test context. For a phone event, distinguish a phone-link tap, a connected call and a qualified call; the specific collection route belongs in the Google Ads phone-call measurement guide.
Hypothetical example: why 400 is not automatically 400 leads#
Assume an account report shows 400 conversions: 250 directions actions, 60 call interactions, 55 website form submissions and 35 imported qualified leads. The CRM contains 48 unique submitted enquiries, of which 19 pass a documented qualification rule. These are hypothetical figures, not AdProof customer results.
The correct first conclusion is that the account contains several action populations and the CRM contains distinct business-stage populations. The figures alone do not show that 381 Ads conversions are invalid or duplicated. Some actions may represent different stages; some enquiries may be un-attributed; one person may create multiple actions; and the selected campaign goal may include only part of the total. The next checks are to segment the Ads columns by conversion action, inspect the campaign goal, compare form IDs under a declared duplicate rule, and review the import row results for the 35 qualified-lead actions.
If the campaign is intended to optimize toward qualified leads, prepare a separate configuration decision after validating that the imported action accurately represents that stage and is selected in the campaign goal. Do not switch goals solely to make Ads equal CRM counts. Preserve the current settings and effective timestamp; changing goals changes what the campaign is instructed to optimize for, while a before/after result also depends on traffic, attribution maturity and other conditions.
Use a safe reconciliation sequence#
- Freeze the evidence. Save the report, columns, filters, selected campaign, account time zone and completed date interval.
- Segment by action. Export Conversions and All conversions by action and day. Preserve local actions, website actions and offline imports as separate rows.
- Inspect actual goal membership. Check whether each action is Primary or Secondary, whether its standard goal is selected and whether a custom goal changes the campaign's included actions.
- Verify the website event. Test one successful form journey on the published site. Confirm the event corresponds to a successful business action and does not also fire on validation error or page reload.
- Reconcile first-party outcomes. Count enquiries and qualified leads using documented CRM states, unique IDs and duplicate rules. Keep unknown attribution as unknown.
- Validate offline rows. Preserve upload batch and row results, conversion timestamps, time zones and matching keys. Use the upload diagnostics before retrying an import.
- Decide the intended optimization outcome. If the business wants the campaign to favor a later funnel stage, confirm that the action is valid, sufficiently observed for the account's needs and included in the selected goal. Have the account owner approve changes.
- Report the residual. Name each denominator, source, date basis and remaining unmatched share. Do not force the sums to reconcile by relabeling local actions as leads or attributing every CRM outcome to paid media.
Google Ads documents goals, conversion reporting and import behavior, but the account's settings and row-level records determine which explanation applies. An individual forum reply is not a substitute for that evidence.
For AdProof, use campaign/event delivery reporting only to check the ad-delivery population and time window covered by that reporting. It does not read or reconcile this Google Ads action map, prove that a lead qualified, or establish a CRM-to-ad attribution. Keep delivery, action attribution and business outcomes as linked but separately sourced evidence.
Frequently asked questions#
Do Google Ads local actions count as qualified leads?
No. A local action records a defined interaction with a business location. A qualified lead is a separate business outcome established by the advertiser's lead process. Preserve both measures if each is useful, and label them separately.
Does a Primary conversion action mean every campaign optimizes toward it?
No. Confirm that the campaign selects a standard goal containing the action. A custom goal can also include actions that are otherwise secondary, so inspect the campaign's actual configuration.
Should I remove local actions when CRM leads are lower?
Not solely because the counts differ. First determine what each action measures and whether the campaign should report or bid toward it. A local intent signal may be useful even when it is not a qualified lead.
Can I compare Ads conversions directly with CRM qualified leads?
Only after naming the actions, business stages, date basis, time zone, attribution and deduplication rules on both sides. Even after aligning them, unmatched outcomes can remain because the systems do not use identical populations or identifiers.
References#
- Google Ads, About local actions conversions.
- Google Ads, About primary and secondary conversion actions.
- Google Ads, About conversion goals.
- Google Ads, Results reporting.
- Google Ads, Fix discrepancies and errors in offline conversion imports.
Make the next tracking test reproducible.
Use the ungated QA checklist to record event rules, consent, duplicate sends and the report you expect to change.
Read the tracking QA checklistOpens a practical guide. No email required.
