Google Ads offline conversions: define the business event before you import it
Offline conversion tracking lets Google Ads use what happens after a lead. A trustworthy setup starts with a CRM outcome that is consistently defined, tied to the original lead and reproducible after import.
Reviewed 26 August 2026
What matters
- Write the business definition of the conversion before configuring the upload.
- Preserve GCLID and first-party lead identifiers when they are available.
- Give every event a source of truth, event time, deduplication key and correction policy.
- Use Google diagnostics to validate delivery and matching, then reconcile against the CRM.
- Do not give an unstable CRM stage authority over Smart Bidding.
Trace the event from click to feedback
Each handoff can preserve the event or quietly change it. Audit the chain in order rather than starting at the upload screen.
- 01Ad interactionGCLID and campaign context
- 02Lead captureFirst-party identifiers
- 03CRM recordIdentity survives the handoff
- 04Business outcomeQualified, sale or revenue
- 05ValidationTime, value and deduplication
- 06Google AdsReporting and bidding feedback
Write down what one conversion row means
A short event contract gives marketing, sales and engineering the same definition to test.
| Field | Example | Evidence to verify |
|---|---|---|
| Business event | Qualified lead | CRM rule used consistently by the sales team |
| Source of truth | CRM lifecycle stage | The system that owns the final state |
| Event time | qualified_at | Timestamp of the actual stage transition |
| Match data | GCLID + first-party data | Captured earlier and still linked to the lead |
| Deduplication | Stable order / transaction ID | The same event keeps the same key on retry |
| Value | Observed revenue or explicit weight | Origin, currency and meaning are documented |
| Correction | Restate or retract changed outcomes | Owner and rule are known before activation |
What an offline conversion actually does
Google Ads can observe the ad interaction and the website conversion, but the useful outcome often happens later. A CRM may qualify the lead days after the form submission. A payment system may record revenue later still. Offline conversion imports connect those later outcomes to the advertising interaction.
The import only becomes useful when the downstream event is stable enough to mean the same thing every time. The data path has to preserve identity, event time and value without turning CRM noise into a bidding signal.
How enhanced conversions for leads fits the measurement path
Google describes enhanced conversions for leads as the upgraded form of offline conversion import. It can use hashed first-party data, such as email or phone, together with identifiers such as GCLID to improve the match between the lead captured on the website and the later CRM outcome.
Google recommends including GCLIDs with uploaded events whenever they are available. Since 15 June 2026, Data Manager API is the path Google directs current and future offline-conversion and enhanced-conversion-for-leads uploads toward. Legacy Google Ads API uploads remain available only to developer tokens with qualifying prior usage. The CRM outcome still needs a defensible business rule before either transport is configured.
Check attribution after an upload is accepted
An upload can be accepted while the measurement is still incomplete. Matching can fail, user-provided data can be missing or malformed, a conversion action can be mapped incorrectly, or a row can be technically valid but economically misleading.
Use Google Ads diagnostics to confirm tagging, match data and imported conversions, then reconcile imported totals against the CRM source of truth. Diagnostics expose delivery and implementation issues. The CRM process still owns the definition of “Qualified lead” and the evidence that supports it.
Keep uncertain events out of bidding
A CRM field should not become an optimization input merely because it is available. Hold the event out of bidding while its definition, timing or correction behavior is still unstable. Google’s implementation checklist recommends validating new enhanced-conversion-for-leads actions before using them for Smart Bidding.
Activate the signal when the team can reproduce why a record qualified, trace the identifier used for matching and explain how retries or corrections affect the final count and value.
Diagnose the layer that failed
| Layer | Typical symptom | Evidence to inspect |
|---|---|---|
| Identity | CRM outcome exists but cannot be attributed | GCLID, user-provided data, lead ID and merge history |
| Event semantics | Conversion count rises but lead quality does not | CRM stage definition and who is allowed to change it |
| Timing | CRM event date and Google Ads reporting date do not line up as expected | conversion_time, timezone and the report column/date semantics |
| Deduplication | Retries inflate conversion count or value | Order / transaction ID stability across uploads |
| Value | ROAS looks precise but does not match finance | Revenue source, currency, weighting rules and refunds |
| Transport | Rows fail or diagnostics show implementation issues | Google Ads diagnostics, conversion action and import logs |
Google Ads can attribute conversion metrics to the ad-interaction date, while “by conv. time” columns use the conversion date. Confirm the report definition before treating a date difference as an import error.
Check the contract before Smart Bidding sees it
- DefinitionCan two people apply the event rule and reach the same answer?
- AuthorityIs there one source of truth for the outcome?
- IdentityCan the CRM record still be connected to the original lead and ad interaction?
- TimeDoes the event timestamp represent when the business outcome happened?
- DeduplicationWill a retry reuse the same stable event key?
- ValueIs the number revenue, margin, a deterministic weight or an estimate?
- CorrectionsWhat happens after cancellation, refund or disqualification?
- ReconciliationCan imported totals be checked against the CRM by event and date?
How enhanced conversions for leads connects the website and CRM
The 60-second video below is linked from Google’s current enhanced-conversions-for-leads documentation. It covers the platform mechanics; the event contract above covers the business decision.
AdzSignal
AdzSignal audits the business outcomes and values sent back to Google Ads, including duplicates, corrections and signal definitions.
Google documentation
Related guides
Need to check this in a real account?
We trace the relevant Google Ads, website and CRM evidence before recommending a tracking or bidding change.