Study first
Review the ideas behind the questions
Check the implementation details that decide whether offline lead data is usable. Focus on API access, conversion action type, customer data terms, identifier quality, and import diagnostics.
Choose the upload path before engineering starts
Offline lead measurement is an API and CRM workflow, not just a reporting label. The conversion action and upload route need to match current Google Ads API guidance.
- Developer tokens without prior offline upload use in the stated 2025-2026 window should move offline conversion workflows to Data Manager API.
- Click-based offline imports use a conversion action whose type is UPLOAD_CLICKS.
- Enhanced conversions for leads requires accepted customer data terms and the enhanced-conversions-for-leads setting to be enabled.
In Practice
API access is a launch dependency
A CRM export can be technically correct and still fail if the developer token is outside the supported upload path.
The conversion action type is not cosmetic
If the upload is for click-based offline leads, the conversion action needs the upload-clicks type so imported events land on the intended action.
Common mistakes
Starting CRM work before checking whether the API token can still use UploadClickConversions.
Check the developer-token access rule first and move restricted workflows to Data Manager API before building the export around the wrong endpoint.
Q&A
Which action type matters for click-based offline lead imports?
Use a conversion action with the upload-clicks type for click-based offline conversions and enhanced conversions for leads.
What should be checked before enhanced conversions for leads is built?
Confirm customer data terms are accepted and enhanced conversions for leads is enabled for the conversion customer.
Build the event with the right identifiers
The upload object needs the right conversion action, time, identifiers, and privacy handling. Missing or malformed fields make diagnostics harder and can block matching.
- A click conversion needs the conversion action resource name and a conversion date-time that is after the click and includes a time-zone offset.
- For enhanced conversions for leads, user-provided data should be normalized and hashed before import.
- When available, send the GCLID together with user identifiers to improve import performance.
In Practice
Timestamp checks come before reupload
If the conversion time is before the click or has no time zone, fix the CRM timestamp export before changing campaign settings.
Do not throw away usable identifiers
A CRM import that has both click IDs and user identifiers should not discard one source of matching data without a reason.
Common mistakes
Uploading only the CRM deal ID and expecting Google Ads to infer the conversion action and click.
Populate the required conversion action and supported identifiers, then upload the ClickConversion record through the supported import workflow.
Q&A
Should hashed user data replace the GCLID when both are available?
No. When a GCLID is available, the guide recommends sending it along with user identifiers.
Use diagnostics as an import health check
A successful request does not end offline measurement checks. Diagnostics help show whether recent imports are successful, pending, failed, or missing.
- Offline data diagnostics can be aggregated at account level or conversion-action level.
- Daily summaries cover the last 7 days, while job summaries cover the 7 most recent import requests.
- Offline data diagnostics are returned only when the request customer matches the customer recently used to import conversions.
In Practice
Job IDs make large imports easier to audit
If one process sends many requests, a chosen job ID can help tie diagnostic rows back to that import process.
Pending events are not final failures
When diagnostics show pending events, the review should allow for processing time before treating every pending row as a failed upload.
Common mistakes
Querying diagnostics from a child account when the manager account performed the import.
Query diagnostics from the same customer that recently imported the conversions, or the summaries may not be returned.
Q&A
What should a reviewer use to compare one large import job with diagnostics?
Use job summaries, and assign a job ID when one import process spans many requests.