Offline conversion import errors in Google Ads
CRM or file uploads to Google Ads come back with errors such as This click is too old, Conversion date precedes click date or CLICK_NOT_FOUND, or the upload succeeds but few or no conversions appear in reports.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Start with the offline data diagnostics for the conversion action, which group the errors by type. The most frequent causes are leads stored without a GCLID, clicks older than 90 days, conversion times in the wrong time zone, and uploads to an action that isn't an import action in the account that owns the click. Since June 15, 2026, new API integrations must use the Data Manager API, so new setups calling the Google Ads API fail with CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE.
1. Leads are stored without a valid GCLID
Offline click imports match on the Google click ID. It only exists when auto-tagging is on, and it has to be captured on landing, carried through the form and saved on the CRM record. Many CRMs end up with blank, truncated or lower-cased values, which Google can't match because the GCLID is case sensitive.
How to check
- 1In Google Ads, open
Account settingsand confirmAuto-taggingis on. - 2Pull recent paid search leads from the CRM and check how many have a GCLID, and whether values keep their original case and length.
- 3Test the form with a
gclidin the landing URL, browse to a second page, then submit. Confirm the CRM record receives the value. - 4For API uploads, Google says to treat
CLICK_NOT_FOUNDas a warning unless it affects most conversions.
How to fix
- 1Store the GCLID in a first-party cookie or local storage on landing and write it to a hidden field on every form, as Google's setup guide describes.
- 2Map it to a dedicated CRM field that workflows can't overwrite or reformat.
- 3Also capture
gbraidandwbraid, and send the email so enhanced conversions for leads can match when the GCLID is missing.
2. The click is older than the import window or the conversion window
Google retains GCLIDs for 90 days, so a conversion uploaded more than 90 days after the click can't be imported. The click also has to fall inside the conversion action's click-through window. For enhanced conversions for leads matched on personal data, Google's FAQ gives a 63-day limit.
How to check
- 1Read the upload results or diagnostics for
This click is too old for its conversion to be imported,Identifiers or iOS URL parameters are too oldor the API errorEXPIRED_EVENT. - 2Compare the click date stored in the CRM with the upload date for rejected rows.
- 3Hover over the conversion action in
Goals>Summaryand note its click-through conversion window.
How to fix
- 1Upload at least daily, as Google recommends, rather than in monthly batches.
- 2For long sales cycles, import an earlier stage, such as a qualified lead, that happens within the window.
- 3Lengthen the action's click-through window if needed. It doesn't rescue clicks that already expired.
3. Conversion time format or time zone is wrong
If the conversion time is read in the wrong zone it can land before the click, producing Conversion date precedes click date or CONVERSION_PRECEDES_EVENT. Daylight saving changes cause the same problem when a fixed offset is used.
How to check
- 1Find rejected rows and compare the uploaded conversion time with the click time.
- 2For file uploads, check the
Parameters:TimeZonerow and that times use an accepted format such asyyyy-MM-dd HH:mm:ss. - 3For the Google Ads API, check
conversion_date_timeusesyyyy-mm-dd HH:mm:ss+|-HH:mm. For the Data Manager API, checkevent_timestampuses RFC 3339 in JSON.
How to fix
- 1Set a time zone ID such as
America/Chicagoin file uploads, which Google recommends to avoid daylight saving errors. - 2Export CRM timestamps with an explicit offset, then re-upload the corrected rows.
4. The conversion action isn't set up for imports, or is in the wrong account
Uploads need an enabled import conversion action in the conversion account that owns the click. Errors like No Google Ads conversion types were defined, We cannot find this conversion name in the target account, NO_CONVERSION_ACTION_FOUND or INVALID_CONVERSION_ACTION_TYPE all point here. Uploading under a manager account adds cross-account conversion tracking to the picture.
How to check
- 1In
Goals>Summary, add theConversion sourcecolumn and confirm the action showsImport from clicks. - 2For file uploads, compare the
Conversion Namecolumn with the action name exactly, including capitalization. - 3If uploading through an MCC, check whether the client account uses cross-account conversion tracking and which account owns the action.
- 4Check when the action was created. Google says to wait 4–6 hours after creating it before uploading (
TOO_RECENT_CONVERSION_ACTIONin the API).
How to fix
- 1Create the action through
+ Create conversion action>Conversions offline, connect the data source, and use that exact name in uploads. - 2Upload to the account that owns the conversion action. In the Data Manager API, the
operating_accountmust be the conversion customer.
5. Duplicates, too-recent clicks and missing consent
Google treats the same GCLID, conversion name and conversion time as a duplicate and counts only the first. Clicks less than about 6 hours old come back as Click too recent. In the API, uploads without the consent field may not be attributable for regulated traffic.
How to check
- 1Look for
CLICK_CONVERSION_ALREADY_EXISTS,DUPLICATE_CLICK_CONVERSION_IN_REQUESTorDUPLICATE_ORDER_IDin API responses, or duplicate rows in the file. - 2Check whether rejected rows have very recent clicks.
- 3Check whether your API payload sets
consent.ad_user_data, or whether account defaults exist underTools>Data Manager>Consent settings.
How to fix
- 1Send a unique
order_id(Google Ads API) ortransaction_id(Data Manager API) per conversion, and ignore duplicate errors on retries that already succeeded. - 2Delay uploads so clicks are at least 6 hours old, or retry them in the next run.
- 3Pass the consent status you collected with the lead, and leave it out rather than guessing when it's unknown.
6. The upload path is legacy or blocked: Data Manager vs Google Ads API
Google now labels file-based offline conversion import as legacy and recommends Google Ads Data Manager. From June 15, 2026, the Google Ads API stopped accepting new adopters of offline conversion imports and enhanced conversions for leads. Projects without upload activity between December 2025 and June 2026 get CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE.
How to check
- 1Check API responses or the integration's logs for
CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. - 2In Google Ads, go to
Tools>Data managerand see whether the client's CRM is connected there, and useManage and Viewon the connection for run status. - 3If you rely on API retractions, note that the Data Manager API does not support them.
How to fix
- 1For new or rebuilt integrations, send events to the Data Manager API with
IngestEvents, mappinggclidtoad_identifiers.gclid,order_idtotransaction_idandconversion_date_timetoevent_timestamp. - 2For no-code setups, connect the CRM or file source through Data Manager instead of manual legacy file uploads, and check the lookback for your source in Google's guide.
- 3Use
validateOnlyto test payloads, andrequestStatus.retrieveto check processing status and diagnostics.
Stop it happening again
- Audit GCLID capture rates in the CRM every month and alert when paid leads arrive without one.
- Upload at least daily with explicit time zones and unique order or transaction IDs.
- Check offline data diagnostics, not campaign reports, to confirm import health, since the UI doesn't report by import date.
- Plan new integrations on the Data Manager API and keep legacy file imports only where a migration is scheduled.
- Send user-provided data with each conversion so enhanced conversions for leads can match when the click ID is missing.