How do you import offline conversions into Google Ads?
Direct answer: Capture an ad identifier and consented first-party lead data when the form is submitted, preserve both in the CRM, define a distinct conversion action for each meaningful sales stage, then upload the stage outcome with its time, value, currency, and a unique transaction ID. Validate the new feed before letting campaigns bid toward it.
An offline import connects an ad interaction to an outcome that happened later in a CRM, on a phone call, or after a sales conversation. The useful signal is not that a form fired. It is that the lead became qualified, booked, or reached another precisely defined business outcome.
Google describes enhanced conversions for leads as its upgraded offline-import method. It uses hashed first-party data alongside identifiers such as the Google Click ID to improve matching. Google recommends Data Manager for imports and supports direct CRM connections and APIs. Google Ads Help explains enhanced conversions for leads.
What information must follow the lead into the CRM?
The import can only match an outcome if the identifying trail survives the handoff from the website to the CRM. Preserve the Google Click ID when it is available. Also capture at least one permitted first-party field, such as email address or phone number, using the collection and consent process appropriate to the business.
Google says a Google Click ID is required when a tag is not collecting user-provided data. Even when the tag does collect it, Google recommends continuing to send the click ID to improve attribution to a specific ad click. Its setup guide also lists the conversion name and conversion time as required import fields, with order ID, value, currency, and consent among the recommended fields. The Google tag setup guide lists the required and recommended fields.
| Field | Why it matters | Failure to watch for |
|---|---|---|
| Click ID | Connects the CRM outcome to an eligible ad interaction | The landing page captures it, but the form or CRM drops it |
| Consented first-party data | Provides an additional matching path | Formatting or hashing differs between capture and upload |
| Conversion action | Names the exact stage being reported | Qualified and converted leads share one vague action |
| Conversion time | Records when the offline stage actually happened | The upload time is sent instead of the outcome time |
| Transaction ID | Supports deduplication and later adjustments | The same stage is uploaded more than once without a stable ID |
Which offline outcomes should become conversion actions?
Create actions only for stages the business can define and apply consistently. Google recommends qualified lead or converted lead as the goal for lead-generation advertisers measuring offline outcomes. One action might represent a sales-qualified lead. Another might represent a signed contract. Their names should match documented CRM criteria.
Do not invent an extra stage merely to send more conversions. A sales team that uses the word qualified differently from week to week cannot produce a stable optimization signal. The event definition must exist in operations before it exists in Google Ads.
This is also where the import guide separates from a conversion-value plan. The import answers whether Google Ads received the right event for the right lead. A value plan answers what that event is worth. Verify identity and stage logic first, then attach a defensible value.
How should the import be delivered?
Choose the simplest supported path that can run reliably. Google lists Data Manager, direct CRM connections such as HubSpot, and supported APIs as import methods. The implementation checklist says daily uploads are strongly recommended. Google's implementation checklist covers import methods and cadence.
The scheduled job should send every eligible event for the chosen stage, not a manually selected sample of Google Ads leads. Google's checklist says all conversions for the specified event should be uploaded, including outcomes not attributed to Google Ads. Matching determines which records can be credited.
- Define the event. Write the CRM rule for qualified or converted lead.
- Capture identity. Preserve the click ID and permitted first-party fields from the original lead.
- Create a separate action. Use an offline import source and the matching lead goal.
- Build the connection. Map CRM fields to the import fields in Data Manager, the CRM integration, or the supported API.
- Upload on a schedule. Send accurate outcome times, values where used, currency, consent, and stable transaction IDs.
- Review diagnostics. Inspect rejected rows, unmatched records, stale data, and changes in upload volume.
How do you prevent duplicates and correct bad outcomes?
A stable transaction or order ID should identify one lead-stage event. Do not reuse the same ID for different outcomes, and do not generate a new ID every time the same row is retried. Google's checklist recommends an order or transaction ID for deduplication when using an API or server-side Google Tag Manager.
If a recorded conversion later proves wrong, correct the existing record rather than uploading an offsetting fictional event. Google supports retractions that negate a conversion and restatements that change its value. Its API documentation recommends identifying an adjustment by order ID because that method is more durable than a click ID and timestamp pair. Google Ads API documentation explains conversion adjustments.
When is the feed safe to use for bidding?
Do not switch bidding as soon as the first successful row appears. A technically accepted upload can still contain wrong stages, duplicates, missing values, or a sharp mismatch with the CRM.
Google's implementation checklist recommends marking a new enhanced-conversions-for-leads action as secondary for the first 2 to 3 weeks. Its migration guide gives a second validation window: wait 1 to 2 conversion cycles or 4 weeks for data to accumulate before turning off the previous offline-import action. These are platform recommendations, not a promise of better performance. Google's migration guide describes the validation period.
During validation, compare imported counts with the CRM by day and stage. Check that conversion times reflect the business event, values and currencies match the source record, and duplicate rates remain controlled. Review offline-data diagnostics and investigate rejected records rather than silently excluding them.
What can make a working import stop?
- A form or landing-page release drops the click ID. The CRM still receives leads, but the matching field becomes blank.
- A CRM field is renamed. The connector continues to run while its source mapping stops producing data.
- The stage definition changes. Upload volume moves even though lead quality did not.
- Hashing or normalization changes. The website and offline record no longer provide comparable first-party data.
- A legacy upload path is left in place. Google announced that, from June 15, 2026, offline and enhanced-lead uploads would move to the Data Manager API, with non-allowlisted legacy Google Ads API uploads blocked. Google documents the 2026 settings and upload changes.
Monitor the feed as a production data pipeline. A successful login or connector status is not enough. The useful checks are fresh event volume, acceptance errors, match behavior, stage distribution, and agreement with the CRM source.
What should an offline-conversion audit prove?
A defensible audit follows one test lead from the ad click through the form, CRM record, stage change, upload, and Google Ads conversion action. It proves that each handoff preserved the right identifier and that the final event was counted once.
Barlo Digital also checks the reverse path. Starting from an imported action, we should be able to identify its CRM definition, upload source, timing rule, value basis, deduplication key, and the campaigns allowed to use it. If any part of that chain is ambiguous, bidding should not depend on the action yet.
Fair questions
Can we import offline conversions without a Google Click ID?
Enhanced conversions for leads can use consented first-party data for matching, but the setup depends on how the website tag is configured. Google says the click ID is required when a tag is not collecting user-provided data and recommends sending it whenever available. Preserve both paths when the implementation and consent basis support them.
Should a new qualified-lead action become primary immediately?
No. Keep the new action secondary while you compare it with the CRM and inspect diagnostics. Google's checklist recommends a 2 to 3 week initial observation period, while its migration guide recommends 1 to 2 conversion cycles or 4 weeks before retiring the previous import. Change bidding only after the feed is dependable.
What happens if a lead is uploaded twice?
A stable transaction ID gives the import a consistent deduplication key. Without one, retries and overlapping connectors can count the same business stage more than once. Map one identifier to one stage event, monitor duplicate behavior, and use a retraction or restatement when an accepted conversion needs correction.