Google Ads
The Demand Gen Lead Form Field Is Gone. Remove the Dead Dependency Before the Next Build.

Updated: November 11, 2026
Google Ads API v26 removes DemandGenMultiAssetAdInfo.lead_form_only. Even if a campaign no longer needs the value, serializers, templates, validation rules and stored payloads can continue sending it. Search code, configuration, saved drafts, bulk tools and vendor mappings. Record every dependency before changing the production builder.
A removed field can survive in many layers
Google Ads API v26 removes DemandGenMultiAssetAdInfo.lead_form_only. Even if a campaign no longer needs the value, serializers, templates, validation rules and stored payloads can continue sending it.
Search code, configuration, saved drafts, bulk tools and vendor mappings. Record every dependency before changing the production builder.
Separate old intent from the dead implementation
Document what the field represented in your workflow. If it controlled a business rule, decide which currently supported setting or validation owns that rule now.
Do not replace the field with a similarly named property without official support. Removing an obsolete technical flag should not silently remove the team’s lead-form eligibility review.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Owner | Named reviewer and decision | Unclaimed change |
| Configuration | Saved source state | Cannot reproduce |
| Validation | End-to-end fixture | Partial success accepted |
| Threshold | Success and rollback rule | Result reinterpreted |
| Evidence | Public or reporting read-back | Configured mistaken for delivered |
Test create, update, clone and read paths
A clean create request does not prove an old campaign can be cloned or updated. Exercise each operation with known fixtures and compare the final API object.
Include low-frequency templates and paused campaigns. Retired fields often reappear when teams duplicate an older successful setup.
Reconcile connector behavior
Confirm whether each connector drops the field, returns a validation error or fails before making the request. Add explicit logging so a generic build failure can be traced to the unsupported property.
Compare response errors and successful object counts before and after release. Alert when a tool claims success but creates fewer ads than requested.
Release without changing campaign strategy
Remove the dependency in a narrow deployment. Keep budget, bidding, assets, audience and conversion settings unchanged so the migration result remains interpretable.
After release, create and update a controlled ad, inspect the live object and document the supported configuration that replaces the old implementation assumption.
Connect the control to the wider system
Use this process alongside the Demand Gen activation cutover checklist. The platform setting, creative promise, measurement rule and downstream experience should describe the same decision.
Pre-launch checklist
- Write the decision and owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the next review before material spend accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation.
Repeat the test on mobile and with one adverse condition. Resolve differences in the campaign brief and measurement plan before launch.
Set the review cadence before launch
Assign a monitoring owner, review frequency and evidence threshold before the change is released. Preserve the pre-change baseline and avoid silently editing the definition after results arrive. This turns the launch into a measurable operating decision instead of a one-time interpretation of platform guidance.
At the first review, reconcile the source platform, public experience and one downstream business system. Close the change only when all three support the same conclusion, and record any limitation that future analysts must preserve.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What evidence should be preserved?
Keep the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
