Advertisement
Content Moved? Use Search to Locate
Artificial Intelligence Optimization. Training AI on factual data about your business.

Why Is My Google Ads Offline Conversion Upload Failing?

If your Google Ads offline conversion upload is failing, first identify the API method and inspect its complete response. An UploadClickConversions request that returns CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE points first to Google Ads API eligibility—not proof that the CRM lead data is invalid. That distinction matters: a request can be rejected before data quality is the issue, while an accepted import still may not become an attributed conversion or appear in the date range you expect.

This guide is for developers and lead-generation advertisers importing CRM-recorded leads. Since June 15, 2026, Google’s guidance directs new offline-conversion and enhanced-conversions-for-leads implementations to the Data Manager API. Existing integrations need to verify their own eligibility and migration path rather than assume that past or current CRM activity qualifies them to keep using the Google Ads API.

1. Trace the upload before changing it

For one failed request, record the upload path, the Google Ads API method or Data Manager API in use, the relevant Google Cloud project or developer-token identity, the Google Ads account, the conversion action, the request time, and the full response—including error details. Keep the corresponding upload log with those details. Do not share credentials or tokens in a support request or public discussion.

A dashboard label such as “failed” or “pending” is not enough to diagnose the cause. The exact method and response help separate an access or eligibility problem from a data, configuration, or reporting problem. If the response is not the allowlist error discussed below, use that actual error and Google’s import diagnostics to guide the next check; identifiers, timestamps, permissions, formatting, or conversion-action setup may need investigation, but the available evidence does not identify which one is responsible in a particular case.

2. Treat the allowlist error as an eligibility signal

Google’s Google Ads API guide to managing offline conversions documents CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE for affected UploadClickConversions requests. When you see it, investigate whether that specific integration can use the method before changing CRM fields or repeatedly retrying the same blocked request. The error does not establish that your lead data is valid or invalid; it identifies an API-access issue to resolve first.

Google’s eligibility descriptions are not worded identically. The API guide describes request history from December 17, 2025 through June 15, 2026. Google’s May 15, 2026 announcement about offline click conversion import support describes allowlisting by developer token and qualifying activity during December 2025 through May 2026. Those descriptions differ in date precision and how they frame the relevant identity. Do not merge them into one blanket eligibility rule or infer access from an advertiser’s current CRM activity. Check the exact project or token, its Google Ads API history and status, and the response from the integration; ask Google to clarify that integration’s status if the documentation does not settle it.

3. Choose the right API path

Google announced that, beginning June 15, 2026, the Google Ads API would stop accepting new adopters of offline conversion imports, including enhanced conversions for leads. Its announcement said previously adopted integrations could continue while integrating with the Data Manager API. That is not a promise that every previously active integration remains eligible indefinitely.

  • Eligible existing integration: follow Google’s Data Manager API migration guide and verify the identity and access history relevant to your integration. Do not treat a general description of legacy eligibility as confirmation for your project or token.
  • New or ineligible implementation: use the Data Manager API rather than repeatedly retrying a Google Ads API method that is blocked for your integration. The current Google Ads API guide directs new implementations to Data Manager.

Before migrating, check which Google Ads account owns the conversion action. Google’s migration guide says the Data Manager API operating account must be that owner. If the old Google Ads API integration operated through a manager, parent, or descendant account, confirm that the Data Manager API destination uses the conversion-action owner account. Resolve an account mismatch before interpreting a test upload as evidence about the lead data or attribution.

Hypothetical: CRM leads, but an allowlist error

A business records qualified leads in its CRM and sends them with UploadClickConversions. The request returns CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. The next step is to preserve the request and full response, then check the project or developer-token identity and its Google Ads API eligibility. The error alone does not show that the CRM’s lead fields are wrong. If access is unavailable, the business should assess the Data Manager API path; if a different error appears after resolving the access question, investigate that response separately.

4. Verify import health, attribution, and reporting separately

Work through distinct checkpoints rather than treating “upload succeeded” as the final result:

  1. Request response: Was the request accepted, or did the API return an error? Save the full response and match it to the request log.
  2. Upload health: Review the offline upload health and error counts for the relevant integration and period. Google’s offline conversion import troubleshooting guidance distinguishes upload errors from discrepancies discovered after successful uploads.
  3. Conversion-action diagnostics: For enhanced conversions for leads, open Google Ads and go to Goals > Summary, then select the relevant conversion action’s Diagnostics. Google’s enhanced-conversions-for-leads diagnostics report guide describes this route.
  4. Attribution and reporting: Check the conversion action’s reporting after allowing for the reporting basis and timing. Google says imported conversions are reported against the original click’s impression date, and time to appear varies by attribution model. A successful import response therefore does not necessarily mean that Google Ads attributed the conversion or that it will appear under the upload date.

Some enhanced-conversions-for-leads uploads can contain conversions that are not attributable to Google Ads. Google notes that these may show as Unknown clicks; that status alone does not demonstrate a general upload failure. Check it alongside the upload response, health information, and conversion-action diagnostics.

Verification checklist

  • Keep the request log and full error response alongside the upload method, account, conversion action, and project or developer-token identity.
  • For the allowlist error, verify the specific integration’s access history and status rather than inferring eligibility from current CRM activity.
  • For migration, confirm the Data Manager API operating account owns the conversion action.
  • Check offline upload health and error counts, then review conversion-action diagnostics.
  • Check conversion reporting with the original-click impression-date basis and attribution-model timing in mind.

When an imported action is used for bidding, missing or misclassified lead conversions can leave reporting or optimization signals incomplete or misrepresent which outcomes the account is measuring. Confirm that the CRM event and conversion action reflect the intended lead outcome before relying on that signal. Splinternet Marketing’s conversion tracking service can help implement the appropriate upload path, check account and conversion-action compatibility, and measure upload health and attribution as the setup is maintained. Which checkpoint is hardest to verify in your integration: API eligibility, account ownership, or attribution timing?

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.