Enhanced conversions for leads, without the black box.

Enhanced conversions for leads is Google’s upgraded form of offline conversion import. It uses first-party data such as an email address or phone number from the website lead and the later offline event to strengthen the match back to an advertising interaction. Google hashes the user-provided data used for matching.

It is useful when the action that matters happens after the web session: a lead becomes qualified, a consultation is booked, an opportunity advances, or a sale closes in a CRM or another internal system.

It is not a substitute for offline conversion tracking as an operating discipline. It will not define your lead stages, fix missing CRM timestamps, distinguish a real submission from a phantom event, or decide which stage Smart Bidding should use. It improves the attribution layer inside a wider system.

Google now combines enhanced conversions for web and leads under one account-level setting, but the measurement use cases remain different. Enhanced conversions for web strengthens an online conversion recorded by the site. Enhanced conversions for leads connects a web lead to a meaningful event recorded later. See Google’s current overview of enhanced conversions for leads.

1. The ad interaction

   A Google ad click or eligible interaction creates attribution information. Auto-tagging and the conversion linker help preserve available click data on the advertiser’s domain.

2. The website lead

   The form captures first-party data, usually an email address or phone number. The Google tag or Google Tag Manager sends the user-provided-data event after a successful submission, while the application stores the lead and available ad identifiers.

3. The system of record

   The CRM or lead system receives the lead, keeps the identifier bridge, and records each meaningful lifecycle change with an accurate timestamp. A spreadsheet can work technically, but the system still needs ownership and repeatable definitions.

4. The offline event

   A business rule determines that the lead is qualified, converted, or has reached another defined stage. That event—not a later export date—receives the conversion time.

5. The import and attribution result

   Data Manager or the Data Manager API sends the event to the correct Google Ads conversion action. Google attempts to match it using the supplied ad and user identifiers, then reports accepted events in the account.

If any handoff breaks, the import can be technically “configured” and still be operationally useless. A tag may fire without data. The CRM may overwrite the original source. A stage may be applied inconsistently. An accepted import may represent the wrong event.

A downstream event with a stable definition

Choose an event that the business can identify consistently. Google recommends the qualified lead or converted lead goal for enhanced conversions for leads. Create a separate conversion action for each lifecycle stage rather than combining qualified leads and closed sales into one action; this preserves reporting clarity and lets bidding target one stage intentionally. Google explains the distinction in its offline conversion import FAQ.

A lead record that survives the handoff

The destination system needs the lead’s source identifiers, first-party match data, lifecycle stage, and event time. Preserve GCLID whenever available. Google also recommends supplying user-provided data and available GBRAID or WBRAID values, rather than treating these as mutually exclusive choices.

Website tagging at the successful lead event

Use the Google tag or Google Tag Manager on the relevant form flow, with auto-tagging enabled. The user-provided-data event should run after a real successful submission—not on page load, validation failure, or a button click that never created a lead. For Tag Manager implementations, Google calls for a conversion linker and documents automatic, manual, and code/data-layer collection methods in its GTM setup guide.

The same first-party field at both ends

Email is often the most stable lead identifier, and phone can improve coverage when collected and formatted consistently. If your own code normalizes and hashes the data, Google specifies trimmed lowercase text, E.164 phone formatting, and hex-encoded SHA-256. If the Google tag or Tag Manager receives unhashed data through the supported configuration, Google performs the hashing.

Policy, consent, and access controls

Accept the applicable Customer Data Terms and confirm that collection and use comply with Google’s customer-data and consent policies. Hashing is not a substitute for consent, disclosure, minimization, retention controls, or limiting CRM and upload access to the people who need it.

A conversion cycle inside the import window

Google’s current guidance allows GCLID-based offline events up to 90 days after the associated click and enhanced-conversion lead events using personally identifiable information up to 63 days. If the sale closes later, choose a meaningful intermediate event that happens inside the supported window rather than falsifying the conversion time.

A lifecycle map should document the event, entry rule, timestamp source, owner, expected delay, conversion action, value, and whether it belongs in the primary Conversions column.

1. New lead

   The website confirms a genuine submission and creates the CRM record. Keep this action for funnel visibility, but do not assume it is the best bidding signal.

2. Qualified lead

   The business confirms fit using explicit criteria. This is often the first offline event with enough volume and quality to support optimization.

3. Appointment or showroom visit

   The prospect takes a deeper step. Track it separately if the definition is reliable and the volume is sufficient to be useful.

4. Converted lead or closed sale

   The chosen commercial outcome occurs. Include an honest value when the system can provide it consistently; otherwise avoid invented values that imply precision the CRM does not have.

The correct primary action depends on volume, delay, and business meaning. A closed sale may be the truest event but too sparse or delayed for stable bidding. A qualified lead may be earlier but more frequent. The decision belongs in a documented bidding plan, not inside the tag configuration.

See how this mapping worked in practice in our high-ticket B2C offline conversion tracking case study.

Data Manager connections

For many advertisers, Google Ads Data Manager is the simplest route. It can connect supported CRMs, databases, cloud storage, SFTP, HTTP, and files, then map source fields to Google Ads conversion actions. A connection is easier to operate than a custom service when the source system and transformation requirements fit the available connector.

Data Manager API

Use the Data Manager API when a custom server-to-server workflow is warranted: multiple internal systems, event transformations, programmatic scheduling, stronger observability, or agency-scale routing. Google’s current developer guide supports sending both offline conversions and enhanced conversions for leads through the Data Manager API.

Since June 15, 2026, Google has restricted Google Ads API offline-upload access for developer tokens without qualifying prior use and directs migrations toward Data Manager API. New custom work should target Data Manager API; an existing allowlisted Google Ads API workflow should be treated as a legacy integration with a migration plan. See Google’s API deprecation and access-restriction notice.

The migration is not a mechanical endpoint swap. Data Manager API uses different credentials and an event-ingestion model, and it rejects an entire request when validation fails rather than returning Google Ads API-style partial failures. Google provides an official field-mapping guide for offline conversions.

Google tag or Google Tag Manager on the site

The website side still matters whichever import route you choose. Select one supported user-data collection method, make the data available only at the valid lead event, test dynamic forms and iframes deliberately, and publish only after Preview or Tag Assistant shows the expected event and fields.

Identifiers and deduplication

Send GCLID and user-provided data together whenever available. Preserve GBRAID and WBRAID where present. Supply a unique order ID or transaction ID for the event so reprocessing does not create duplicate conversions, and use the same identifier when the same event is sent through more than one source. Google documents its current identifier recommendations in the offline-import upgrade guide and its deduplication guidance.

1. Inventory every current conversion

   Trace tags and imports to the action that triggers them. Remove or demote phantom, duplicate, test, and low-value actions before adding another signal.

2. Write the event contract

   For each stage, specify its rule, source field, timestamp, owner, value, unique ID, expected volume, and conversion-action destination.

3. Test identifier persistence

   Follow a controlled lead from landing page through form payload and CRM record. Confirm that ad identifiers and the same email or phone field remain available at the offline stage.

4. Configure tagging and ingestion

   Enable the account setting and terms, deploy the supported user-data event, create separate conversion actions, connect the source, and map the fields.

5. Run controlled test records

   Use known timestamps and identifiers. Confirm that the website event fires once, the CRM stage is applied once, and the import result is accepted by the intended account and action.

6. Reconcile before cutover

   Compare accepted events with CRM records by conversion time and stage. Keep new actions secondary during the observation period rather than changing bidding on launch day.

7. Move bidding deliberately

   After enough clean data and at least one to two normal conversion cycles, decide which action belongs in the primary Conversions column and document the campaign-level goal change.

Google’s implementation checklist recommends initially keeping the new enhanced-conversion action secondary for roughly two to three weeks. The exact observation period should also reflect the advertiser’s own sales delay and event volume.

Validate the website event

• Use Tag Manager Preview or Tag Assistant to submit a controlled lead.
• Confirm that the user-provided-data event fires after successful submission and only once.
• Inspect whether the expected email or phone field reached the tag.
• If supplying pre-hashed values, verify normalization and hex SHA-256 formatting.
• Test consent states, dynamic forms, embedded forms, and cross-domain flows separately.

Validate the import

• Review connection runs or API request diagnostics, not just the scheduled-job status.
• Record rejected rows and error reasons with an owner and retry policy.
• Confirm the conversion action and account receiving the event.
• Compare CRM event time with the uploaded timestamp and account time zone.
• Use unique event IDs and verify that reruns do not inflate totals.

Reconcile the reporting

Google recommends comparing the upload result with the “All conv. (by conv. time)” column segmented by conversion action. That view aligns reporting to the actual conversion time in the upload, making it more useful for reconciliation than a click-date view. The enhanced conversions for leads diagnostics report also surfaces missing tags, absent or malformed user data, no attempted imports, and matching problems.

Reconcile in cohorts: CRM events eligible for import, attempted events, accepted events, and events visible in Google Ads. Do not expect those numbers to be identical without accounting for rejected records, unmatched leads, consent, attribution eligibility, and reporting delay.

Enhanced conversion data is first-party customer data. Build the implementation with privacy and operational controls from the beginning:

• Collect and send only fields needed for the documented measurement purpose.
• Apply the consent requirements relevant to the user and jurisdiction.
• Do not send prohibited or sensitive-category data.
• Limit raw-data access in the tag manager, CRM, exports, and ingestion service.
• Document retention, deletion, credential rotation, and incident ownership.
• Keep stage definitions and upload logic under change control.
• Review diagnostics and reconciliation on a recurring schedule.

This guide describes measurement architecture, not legal advice. The advertiser remains responsible for its disclosures, permissions, Google policy compliance, and applicable law.

1. Inventory and clean up all existing Google Ads conversion actions.
2. Define qualified lead, converted lead, and any intermediate stage in writing.
3. Create a separate conversion action for each imported lifecycle stage.
4. Choose the one stage bidding may eventually use; leave the others secondary.
5. Accept the applicable Customer Data Terms and verify consent handling.
6. Enable auto-tagging and validate the conversion linker or Google tag coverage.
7. Capture email or phone at the successful lead event using a supported method.
8. Preserve GCLID, GBRAID, or WBRAID when available through the CRM handoff.
9. Store a reliable event timestamp, stage, source identifier, and unique event ID.
10. Select and configure a Data Manager connector or Data Manager API workflow.
11. Map conversion action, event time, identifiers, value, currency, and consent.
12. Run controlled leads through every form and sales path.
13. Inspect tag diagnostics, connection/API results, rejections, and matches.
14. Reconcile eligible CRM events to attempted, accepted, and reported conversions.
15. Upload daily where possible and monitor failures on every run.
16. Observe clean data for normal conversion cycles before changing primary goals.
17. Document ownership for definitions, tags, CRM automation, imports, and reporting.

Technical details in this guide were checked against these official sources on August 19, 2026:

• Google Ads Help: About enhanced conversions for leads
• Google Ads Help: Configure Google Tag Manager for enhanced conversions for leads
• Google Ads Help: Offline conversion imports FAQ
• Google Ads Help: Enhanced conversions for leads diagnostics
• Google Ads Help: Upgrade offline conversion imports
• Google Developers: Google Ads offline conversions with Data Manager API
• Google Developers: Data Manager API field mappings
• Google Developers: Google Ads API deprecations and access restrictions