In short: Google Ads enhanced conversions for leads can connect a website lead with a later CRM outcome using first-party data and supported identifiers. That can improve matching and measurement, but it does not turn a form fill into a qualified opportunity or prove that an ad caused revenue. Choose one real CRM milestone, map it consistently, validate data use and imports, and only then decide whether it should guide bidding.
A typical B2B path starts when someone submits a form and continues after a salesperson reviews the request. The CRM may later record a qualified lead, a sales opportunity, or a converted customer. If the campaign only receives the original form submission, it cannot distinguish those outcomes. The answer is to send back a well-defined CRM event, not to rename every form fill as a qualified lead.
1. Choose the CRM milestone before opening Google Ads
Start with the decision you want the campaign to support. If the team needs more sales-ready inquiries, define the exact criteria for a Qualified Lead. If it needs to optimize toward completed business, define when a Converted Lead is recorded. Google’s Data Manager guidance recommends these as conversion goal categories when they match the event being measured.
Create a distinct conversion action for each meaningful offline event. A lead becoming qualified and an opportunity becoming a customer are different stages; combining them makes it harder to tell what the campaign is learning. Make sure a CRM status change represents a real transition and has a clear owner. Repeated syncs, reopened records, and duplicate contacts should not create extra outcomes.
If the CRM does not have a reliable stage definition, fix that first. The conversion data dictionary guide explains how to document an event, its record grain, and its owner before adding another field to reports.
2. Map the browser capture to the later CRM event
Enhanced conversions for leads uses first-party information from a lead form to help match a later offline conversion to an ad interaction. In a tag-based setup, the Google tag or Google Tag Manager can capture user-provided data such as an email address or phone number and hash it before transmission. The CRM import then needs a consistent way to connect the outcome to the original lead.
Keep the Google Click ID (GCLID) whenever it is available. Google says it is required when no tag is collecting user-provided data, and recommends continuing to send existing GCLIDs even when the tag also captures first-party data. Use an identifier that your team can maintain consistently: Google recommends email because it is usually unique and less likely to be reformatted in a CRM. Phone numbers need a country code.
Keep the original CRM value and event history intact. Avoid turning a changed email, shared inbox, or account-level address into a confident person-level match. Document which source fields are used, how they are normalized, and who owns the mapping. Google’s implementation checklist also calls for uploading all conversions for the selected event, including those not attributed to Google Ads. Do not pre-filter the event file to only records that already have a known Google click identifier.
For repeatable uploads, define how the system recognizes a retried event so a sync does not count it twice. The guide to using a stable order ID for offline conversions covers that separate deduplication problem.
3. Confirm the current upload path before connecting systems
Google’s enhanced-conversion settings and offline-upload paths changed during 2026. The web and lead settings were combined into one account-level control, while Google also announced changes to legacy offline upload access in June. Some older setup guides describe screens or API routes that may no longer match a particular account.
Before building a workflow, check the current Data Manager setup guide, implementation checklist, and settings update notice. Confirm that auto-tagging is enabled, the applicable customer data terms are accepted, and the chosen data source is supported for your account. If a developer is maintaining an existing Google Ads API upload, verify current eligibility and the recommended Data Manager route before changing it.
The website tag and CRM import serve different parts of the path. Test the form on every relevant landing page, including embedded forms and cross-domain journeys. Then confirm that the CRM event uses the same identifiers and conversion action expected by the import. A successful form tag alone does not prove that later sales stages are reaching Ads.
4. Treat data use and consent as part of the design
Use first-party customer information collected directly from people who interact with the business. Google’s Customer Data Policies require appropriate customer disclosures, consent where legally required, compliance with applicable privacy rules, and use of Google’s approved interfaces. Google also restricts measurement for sensitive categories.
Hashing changes the format of data used for matching; it does not replace the required disclosure, consent, or access controls. Limit the fields sent to what the implementation needs. Check that the people who can export or configure the data understand which CRM fields will be sent, to which Google Ads account, and for what measurement purpose. This is an operational checklist, not a legal determination for a particular region or business.
5. Validate imported records before changing bidding
Test the path from a form submission to the CRM event and then to the Google Ads diagnostics report. For a small sample, compare the lead record, the actual stage-change time, the conversion action name, the identifiers sent, and the import result. Check duplicates, missing values, time zones, and whether changes to a CRM record create unintended repeat events.
Google’s checklist recommends keeping a new enhanced-conversions-for-leads action secondary for the first two to three weeks while the team reviews setup and diagnostics. Secondary actions are generally reported for observation rather than used for bidding; check whether the campaign has a custom goal, because custom goals can use secondary actions for bidding. Google’s primary and secondary action guide explains that distinction.
Set an upload owner and a practical delay limit. Google currently says enhanced lead conversions uploaded more than 63 days after the associated last click will not be imported; check the current offline conversion guidelines when setting your own service window. Review the diagnostics report and compare the imported events with the CRM’s eligible event count. If they diverge, investigate the mapping or feed before interpreting campaign performance. The conversion reconciliation guide gives a broader method for comparing system counts.
6. Promote the event only when it is a usable bidding signal
A primary conversion action is included in Google Ads’ “Conversions” column and can be used for bidding when the campaign uses the goal that contains it. A secondary action is usually for observation and appears in “All conversions.” Do not make both a form submission and a later qualified outcome primary if that would reward the same business journey twice.
Consider using a qualified or converted lead for bidding only after CRM definitions, matching, import coverage, and diagnostics are stable. The event also needs enough volume and a clear relationship to the campaign’s objective. If those conditions are not met, keep the event for analysis and improve the data path before changing targets. A higher match rate is not evidence that the campaign created incremental revenue; a separate experiment may be needed. See the guide to holdout tests when platform attribution is not enough.
Enhanced conversions for leads launch worksheet
- CRM stage to send back: ______
- Criteria and owner for that stage: ______
- Conversion action name and goal category: ______
- Form pages and tag method: ______
- Identifiers captured and preserved: ______
- Consent, disclosure, and approved data route: ______
- Import owner, retry rule, and upload window: ______
- Sample records and diagnostics to review: ______
- Conditions for moving from secondary to primary: ______
Enhanced conversions for leads can add a useful connection between a form and a later CRM outcome. It works best when the CRM event is real, the matching path is consistent, data use is permitted, and the team checks the complete record flow before asking bidding to rely on it.
If Google Ads and CRM report different qualified outcomes, review the event definition, data path, and reconciliation rules together.
Sources and scope
- Google Ads: Using Data Manager with enhanced conversions for leads — current setup options and qualified or converted lead conversion goals.
- Google Ads: Enhanced conversions for leads implementation checklist — prerequisites, data capture, event uploads, diagnostics, and the initial secondary-action recommendation.
- Google Ads: Customer Data Policies — first-party data, disclosure, consent, and restricted categories.
- Google Ads: Primary and secondary conversion actions — reporting and bidding behavior for each action type.
- Google Ads: Offline conversion import guidelines — upload timing and duplicate handling.
- Google Ads: Updates to enhanced conversions settings — 2026 changes to settings and legacy upload access.
The Google Ads interface and upload guidance can change. Check the current account-specific instructions before implementing a connector or API migration. These references describe platform behavior; they do not establish that an ad caused a CRM outcome. Accessed October 9, 2026.
How did this article land?
Choose one reaction. You can change it anytime.