Google Ads
Enhanced Conversions Has One Setting Now. Your Audit May Still Read the Old One.

Updated: October 2026
Google Ads API v26 replaced the old enhanced-conversions-for-leads status field with a unified configuration that exposes both the account’s chosen setting and the effective setting. Update scripts and dashboards before treating a missing legacy field as disabled measurement. Then validate that the effective configuration, tags and uploaded records agree.
What changed in v26
The field enhanced_conversions_for_leads_enabled was removed from ConversionTrackingSetting. Google now directs integrations to enablement_setting, while effective_enablement_setting reports the configuration actually in effect. Both use the new EnhancedConversionsConfig enum.
This is more than a field rename. A configured preference and an effective state can diverge because of account hierarchy, eligibility, product configuration or rollout behavior. Audits should record both instead of compressing the account into a single true-or-false label.
Build a three-layer audit
| Layer | Question | Evidence |
|---|---|---|
| Configuration | What has the account requested? | enablement_setting |
| Effective state | What setting is actually applied? | effective_enablement_setting |
| Delivery | Are enhanced records matching? | Diagnostics and upload health |
Do not infer success from an enabled label
Enhanced Conversions depends on correctly collected, normalized and consented first-party data. An enabled account can still send empty values, format phone numbers inconsistently, omit country codes, hash data incorrectly, duplicate conversions or upload events outside the useful window.
Review conversion actions individually. Confirm which actions are primary, how leads are joined to CRM outcomes, and whether the optimization event reflects a qualified stage rather than the earliest form submission.
Compare configuration with observed health
For each conversion action, record recent upload volume, accepted records, match or diagnostic status, adjustment behavior, lag and downstream quality. A configuration export is a control-plane check; it is not evidence that the data plane is healthy.
Update migration logic safely
- Inventory every report, alert and script using the removed field.
- Add the new configured and effective fields in a test environment.
- Map every enum value explicitly, including unknown or unspecified states.
- Run old and new audits side by side where the older API is still available.
- Investigate accounts where configured and effective states differ.
- Retire the legacy field only after outputs reconcile.
Do not convert a missing value into “off.” That shortcut can create false alarms or cause automation to change an account that is already configured correctly.
Use exceptions that a marketer can act on
A useful alert says: “The account is configured for Enhanced Conversions, the effective state differs, and accepted qualified-lead uploads dropped 42% week over week.” A weak alert says only: “Enhanced Conversions disabled.” Include the affected customer, conversion action, last healthy date and recommended owner.
Pair the account audit with MTC’s offline conversion migration QA and consent diagnostics guide. Conversion settings, consent behavior and upload health belong in one measurement review.
Reconcile settings across manager accounts
Agencies should export the configured and effective values across every client account, then group exceptions by cause. Separate accounts that intentionally remain off, accounts waiting for implementation, accounts with a configuration mismatch and accounts that are enabled but unhealthy. This prevents a single compliance percentage from hiding different jobs.
Add ownership and a review date to the exception table. The implementation owner may need to fix tag collection; the CRM owner may need to repair identifiers; the media owner may need to change conversion goals. Re-run the audit after any ownership, consent-platform, tag or API migration rather than waiting for a performance decline.
Frequently asked questions
Is this only relevant to API users?
The breaking field change affects API integrations, but every advertiser benefits from comparing configured state with effective behavior and actual data quality.
Does “effective” mean conversions are matching successfully?
No. It describes the applied configuration. Matching, consent, formatting and upload diagnostics still require separate validation.
Should audits still separate web and lead workflows?
Yes. The account configuration is unified, but implementation paths, identifiers, timing and business outcomes remain different.
