How Do I Fix the ‘Account Not Enabled for Enhanced Conversions for Leads’ Error?
Quick Answer: The ‘account not enabled for enhanced conversions for leads’ Data Manager API error means the feature is switched off in the destination Google Ads account — a 4-step toggle fix handles it (Google Ads Help, 2026). Enable it under Goals, Conversions, Settings, accept the customer-data terms, and validate with a dry run before sending production records. From June 15, 2026 all leads uploads must use the Data Manager API, so getting this right now prevents a hard cutoff later.
In this article
- Why do I get ‘destination account not enabled for enhanced conversions for leads’?
- How do I turn enhanced conversions for leads on?
- Do I need to accept terms before it works?
- Why does a first-party-only upload fail without a click ID?
- How does the fast-fail model affect this error?
- How do I test the fix without risking live data?
- Which fields does Google say I must send?
- When must leads uploads use the Data Manager API at all?
Why do I get ‘destination account not enabled for enhanced conversions for leads’?
The error means enhanced conversions for leads has not been turned on in the destination Google Ads account’s conversion settings. Google’s Data Manager API validates the account state before it accepts any upload, and if the toggle is off, the entire request is rejected — not just the individual record.
This trips up teams migrating from the legacy Google Ads API because the old endpoint never checked for this setting. The Data Manager API is stricter: it enforces enablement at the account level before processing a single conversion. If you’re seeing this error for the first time in 2026, it’s almost certainly because you’ve moved to the new API without flipping the switch first.
The fix itself takes under a minute. The tricky part is knowing which switch to flip — it’s buried three levels deep in the Google Ads UI.
The error fires because enhanced conversions for leads is toggled off in the destination Google Ads account (Google Ads Help, 2026).
How do I turn enhanced conversions for leads on?
In Google Ads you follow 4 steps — Goals, Conversions, Settings, then expand Enhanced conversions for leads and check the box (Google Ads Help, 2026). That single checkbox tells Google the account is ready to receive hashed first-party data through the Data Manager API.
Here’s the thing — this setting lives in the account-wide conversion settings, not inside a specific conversion action. That means you enable it once for the entire account, and every conversion action in the account can then receive enhanced leads data. You don’t need to toggle it per campaign or per conversion.
If the checkbox is greyed out, check that you’re using an Admin or Standard role. View-only users can’t modify conversion settings. MCC-level admins can also toggle this for child accounts, which matters if you’re managing leads uploads across a portfolio.
Related: Google Data Manager API Just Became the Mandatory Ingestion Layer for Offline Conversions
Do I need to accept terms before it works?
Yes — you must opt in and accept the customer-data terms of service before enhanced conversions for leads will accept uploads. The terms appear as part of the enablement flow, and until you accept them, the API treats the account as unenabled and rejects every request with the same error.
This catches out automated setups. If someone enabled the checkbox via the Google Ads API or a script without going through the UI, the terms may not have been accepted. The API has no endpoint to accept terms programmatically — it must be done through the Google Ads web interface. A human has to click through.
Once accepted, the terms persist and don’t need re-acceptance unless Google updates them. Check the conversion settings page to confirm both the checkbox and the terms indicator show as active.
Why does a first-party-only upload fail without a click ID?
A GCLID is required if you are not using a tag to collect user-provided data, so a bare email-only upload can be rejected. Without the GCLID, Google has no way to tie a hashed email address back to a specific ad click, which is the entire attribution chain.
There are two routes into enhanced conversions for leads. The first uses a website tag (Google’s global site tag or GTM) to capture hashed form data at submission time — that tag also captures the GCLID automatically. The second route skips the tag entirely and uploads data directly through the API. If you take the tag-free route, you must include the GCLID in every record because nothing else is capturing it.
Translation: if your CRM is sending email-only records without a GCLID, and you haven’t deployed a tag, the upload fails at validation — before it even hits the enablement check. Fix the GCLID gap first, then confirm the account enablement.
How does the fast-fail model affect this error?
Under the Data Manager API’s fast-fail model, all records in a request fail if any 1 record errors (Google for Developers, 2026). One unenabled destination blocks the entire batch — you don’t get partial success, and you don’t get a list of which records would have passed.
This is a deliberate design choice. The legacy API processed records individually and returned per-record errors, so a batch of 500 conversions might come back with 3 failures and 497 successes. The Data Manager API doesn’t work that way. It validates the request-level preconditions — like account enablement — before touching any individual record.
The practical consequence: you cannot work around the enablement error by filtering records or retrying subsets. The entire batch will keep failing until the account-level toggle is on. Fix the root cause, not the payload.
Under the Data Manager API’s fast-fail model, 1 bad record blocks the entire batch (Google for Developers, 2026).
Related: Google Ads Data Manager API Launched — Why Plugin-Based Enhanced Conversions Will Stop Working
How do I test the fix without risking live data?
Send the request with validateOnly set to true to confirm the destination accepts it before sending production conversions (Google for Developers, 2026). This dry-run flag runs every validation check — including the enhanced conversions for leads enablement — without writing any data to the account.
A successful dry run means the real send will pass the same gates. A failed dry run gives you the exact same error messages production would, so you can debug without polluting your conversion data with test records.
Here’s the thing — the validateOnly flag checks both account-level settings and record-level schema, so it catches the enablement error AND any malformed fields in one call. Run it after enabling the toggle and before pointing your production pipeline at the new endpoint. One clean dry run confirms everything from permissions to field formatting.
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
Which fields does Google say I must send?
Google’s upgrade guide lists 4 key fields: a GCLID, hashed user-provided data, a conversion name, and a conversion time (Google Ads Help, 2026). Missing any one of these triggers a different validation error from the Data Manager API.
| Field | What it is | Error if missing |
|---|---|---|
| GCLID | The ad click identifier captured from the URL or tag | Attribution failure — conversion can’t be tied to a click |
| Hashed user data | SHA-256 hash of email, phone, or both | Identity resolution failure — no match to Google’s user graph |
| Conversion name | Must match an existing conversion action in the account | Unknown action error — the API doesn’t auto-create actions |
| Conversion time | ISO 8601 timestamp of the offline event | Validation error — missing or malformed timestamp |
The hashed user-provided data deserves extra attention. Google requires SHA-256 hashing with no salt, applied to a trimmed and lowercased email address. A common mistake is hashing the raw form input — including trailing spaces or mixed casing — which produces a different hash and breaks the identity match silently. The upload succeeds but the conversion never attributes.
When must leads uploads use the Data Manager API at all?
From June 15, 2026 enhanced conversions for leads uploads are blocked in the Google Ads API and must use the Data Manager API (Google Ads Help, 2026). After that date the legacy endpoint returns a hard error — not a deprecation warning, not a soft redirect. It stops.
If you’re still uploading through the Google Ads API’s UploadConversionAdjustments method or any plugin that wraps it, you have a fixed deadline to migrate. The same applies to CSV uploads through the Google Ads UI — they’re being rerouted to Data Manager under the hood, but the schema requirements change.
Let that sink in. Every CRM integration, every Zapier workflow, every custom script uploading leads conversions through the old API will break after June 15, 2026. The enablement error you’re fixing now is the first of several Data Manager API requirements you’ll need to satisfy — but it’s the one that blocks everything else.
From June 15, 2026 leads uploads must use the Data Manager API — the Google Ads API stops accepting them (Google Ads Help, 2026).
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
Key Takeaways
- Enable the toggle first: the error means enhanced conversions for leads is off — fix it in Goals, Conversions, Settings in 4 steps.
- Accept the terms: the customer-data terms must be accepted through the web UI before the API will process uploads.
- Fast-fail blocks everything: 1 invalid record or 1 unenabled destination rejects the entire batch under the Data Manager API.
- Dry-run before going live: use
validateOnly: trueto catch enablement and schema errors without writing data. - 4 required fields: GCLID, hashed user data, conversion name, and conversion time — miss any one and the upload fails.
- June 15, 2026 is the hard cutoff: leads uploads must move to the Data Manager API before the legacy endpoint shuts down.
The error means enhanced conversions for leads has not been turned on in the destination Google Ads account’s conversion settings. Google’s Data Manager API checks that the feature is active before accepting any upload, and rejects the entire request if the toggle is off. The fix is a one-time toggle in Goals, Conversions, Settings — no code change required.
In Google Ads, go to Goals, then Conversions, then Settings. Expand the Enhanced conversions for leads section and check the box. That’s 4 steps total (Google Ads Help, 2026). You also need to accept the customer-data terms of service the first time you enable it.
Yes — you must opt in and accept the customer-data terms of service before enhanced conversions for leads will accept uploads. The terms appear as part of the enablement flow. Until you accept them, the API treats the account as unenabled and rejects every request with the same error.
A GCLID is required if you are not using a tag to collect user-provided data, so a bare email-only upload can be rejected. When there is no tag on the site passing hashed form data to Google, the GCLID is the only link between the ad click and the downstream conversion. Without it, Google cannot attribute the conversion.
Under the Data Manager API’s fast-fail model, all records in a request fail if any 1 record errors (Google for Developers, 2026). That means one unenabled destination blocks the entire batch — you don’t get partial success. Fix the enablement toggle first, then resend the full batch.
Send the request with validateOnly set to true to confirm the destination accepts it before sending production conversions. This dry-run flag runs every validation check — including the enhanced conversions for leads enablement — without writing any data to the account. A successful dry run means the real send will pass the same gates.
Google’s upgrade guide lists 4 key fields: a GCLID, hashed user-provided data (typically an email address hashed with SHA-256), a conversion name that matches an existing conversion action, and a conversion time (Google Ads Help, 2026). Missing any one of these triggers a different validation error.
From June 15, 2026 enhanced conversions for leads uploads are blocked in the Google Ads API and must use the Data Manager API (Google Ads Help, 2026). After that date the legacy endpoint returns a hard error, so any CRM or plugin still using the old API stops reporting conversions entirely.
References
- Google Ads Help (2026). Upgrade offline conversion import to enhanced conversions for leads. Source
- Google for Developers (2026). Steps to upgrade to the Data Manager API. Source
- Google for Developers (2026). Google Ads offline conversions (Data Manager API). Source
- Google Ads Help (2026). About offline conversion imports. Source