Google Ads

The Old Enhanced Conversions Flag Is Gone. Your Account State Still Has to Be Read Correctly.

Privacy-safe conversion signals pass through verified gates into an account-level measurement control

Updated: October 29, 2026

Google Ads API v26 removed the old Enhanced Conversions for Leads boolean field. Update integrations to read the account-level enablement_setting, map every returned state explicitly and verify live behavior with upload diagnostics before changing production workflows.

What changed

The removed field answered a narrow yes-or-no question. Google now directs integrations to the enablement setting on the customer’s conversion tracking configuration. A richer state model can distinguish conditions that a boolean monitor would flatten or misread.

Map states before writing code

Question Required evidence Owner
Is the feature configured? Current account-level setting Ads administrator
Are uploads succeeding? Upload health and error distribution Data engineering
Are records matchable? Consent, normalization and hashing QA Measurement lead
Are conversions usable for bidding? Action status, primary setting and lag Media buyer

Separate configuration from performance

An enabled setting does not prove that lead uploads are timely, valid or useful. A successful upload does not prove that the correct conversion action is primary. Build three independent checks: account configuration, data pipeline health and campaign use.

Migration sequence

  1. Inventory every service, dashboard and alert that reads the removed field.
  2. Add the new state parser while the existing version still runs.
  3. Define how unknown, unavailable or transitional states are handled.
  4. Test against accounts with different configurations.
  5. Compare the new readback with the Google Ads interface and upload diagnostics.
  6. Upgrade the API client and deploy monitoring first.
  7. Remove the legacy field only after parity is proven.

Protect lead privacy

Enhanced Conversions for Leads relies on first-party information. Confirm consent, field normalization, hashing, access controls and retention rules. Keep raw personal data out of ordinary analytics logs and error messages.

Use MTC’s offline conversion migration guide to review the rest of the upload path, including timestamps, identifiers and downstream qualification.

Design useful alerts

An alert should say which customer account changed, the prior and current state, when the change was observed, whether uploads remain healthy and who owns the next action. Do not page a team merely because an unfamiliar enum appeared. Preserve the raw value and fail safely when the client library is older than the API response.

Read back after every administrative change

Account configuration can change outside the integration. Schedule a daily readback and record state history. Tie unexpected changes to audit logs when available. If enablement changes, check affected conversion actions, recent uploads and campaign bidding before assuming the feature was intentionally disabled.

Test against real account diversity

A single fully configured account is not enough. Use test cases for newly enabled accounts, accounts with incomplete setup, manager-account reporting, disabled configurations and accounts with healthy settings but failing uploads. The parser should produce a clear operational status for each case.

Keep version changes observable

Log the API version, client-library version, raw state and normalized internal state. During rollout, compare old and new monitoring in parallel. If results diverge, stop the migration and inspect the source values rather than allowing a silent default to overwrite the account record.

Build a runbook for state changes

For every state transition, define who checks account access, consent implementation, upload health and conversion-action configuration. Include the interface path used for human verification and the minimum evidence needed to close the alert.

Frequently asked questions

Does the v26 removal stop Enhanced Conversions?

No. It changes how an integration inspects the account-level setting.

Can upload success replace configuration monitoring?

No. Pipeline health and account configuration answer different questions.

Should unknown states be treated as disabled?

Usually not. Treat them as an explicit monitoring failure until the integration understands the state.

Sources

Published by Marketing That Clicks
Last reviewed October 29, 2026.