Google Ads Shopping Defaults and Lead Form Access: An Audit Plan

Two Google Ads changes can put the same account at risk in opposite ways. Beginning August 31, Shopping campaigns gain local-inventory reach by default. At the same time, Lead Form assets may become accessible to advertisers previously excluded by a large spend requirement.

Treat both as access-control changes. One changes what your campaigns may serve; the other changes who may use a lead format. Neither removes the need for deliberate targeting, verified eligibility, and a reliable data handoff.

Key takeaways

• Every Shopping campaign will have the Local products setting enabled beginning August 31. An API value of enable_local=false will no longer prevent local inventory from serving.
• For an online-only Shopping campaign, enforce that intent with a listing scope whose product_channel is ONLINE, or exclude local inventory through the campaign’s Inventory filter.
• The $50,000 lifetime-spend requirement has disappeared from Lead Form eligibility requirements, but that does not guarantee immediate access in every smaller account.
• Plan new Lead Form assets around Search and Performance Max. Do not assume that an older Display or Video implementation remains supported without confirming it in the account.
• Choose lead delivery before launch. Manual CSV downloads cover 30 days, while Google retains the data for 60 days and API exports can reach back as far as 60 days.

Replace the local-inventory toggle with an explicit scope

The old Shopping control was simple: an integration could set Campaign.ShoppingSetting.enable_local to false. That value is becoming ineffective. Google will treat the setting as true for every Shopping campaign, regardless of the value an integration submits.

The dangerous case is not necessarily a visible campaign failure. It is false confidence. A configuration file may still contain enable_local=false, leading your team to believe that local inventory is excluded when Google is enforcing a different result.

• With Google Ads API v25.1 or later, attempting to set enable_local to false returns ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT.
• With versions earlier than v25.1, existing code may continue to run, but the false value is ignored and Google treats the setting as true.
• The change applies to Shopping campaigns. Do not automatically rewrite configurations for other supported campaign types: enable_local continues to function for Performance Max and Demand Gen.

Audit the intent of each campaign before changing code. A clean migration follows five steps:

1. Classify every Shopping campaign. Mark it as online only, local and online, or intentionally separated by inventory and budget. Do not infer intent from the current value of enable_local; that value may be an inherited template default.
2. Find every place that writes the old field. Check API integrations, campaign builders, bulk-operation scripts, internal templates, and automated account provisioning. Record the API version used by each workflow.
3. Move online-only enforcement into listing scope. Use CampaignCriterionService to create a listing scope with product_channel set to ONLINE. This makes the inventory boundary explicit instead of relying on a campaign setting Google will ignore.
4. Use the Inventory filter where campaign-level separation is easier to manage. Exclude local inventory there when a campaign must remain online only. If online and local products require separate budgets, preserve that separation through campaign structure and inventory filtering.
5. Validate the result, not merely the deployment. Confirm that each campaign’s effective inventory scope matches its classification. For v25.1 or later, also verify that no automation is generating the context error.

This is more than an API cleanup. Google is moving the meaningful control from a Boolean switch to inventory selection. Your campaign documentation, approval process, and automated tests should name the selected product channel directly.

Treat Lead Form access as provisional until the account confirms it

The disappearance of the $50,000 Google Ads spend requirement materially lowers the stated barrier to Lead Form assets. It does not prove that every qualifying smaller account has already received access. Do not promise the format in a media plan, client scope, or launch schedule until the intended account can create and attach the asset.

The remaining eligibility route centers on advertiser reputation and Advertiser Verification. The spend levels associated with that route are more than $1,000 per account or $15,000 across accounts. Treat those amounts as eligibility checks, not campaign objectives. Increasing spend solely to cross a threshold is not a sound substitute for confirming access.

Use this pre-launch check for each account:

1. Confirm Advertiser Verification. Identify whether it is complete and whether any unresolved account-status issue could affect reputation-based eligibility.
2. Test actual asset access. Have an authorized account user verify that the Lead Form asset is available in the account. A removed requirement is not the same thing as a universal rollout guarantee.
3. Confirm the campaign type. Search and Performance Max are the two currently listed options. Video is no longer listed. Display is also omitted from the supported overview, although a separate requirements passage still references it. Treat Display as unresolved until the account interface and current requirements agree.
4. Check each target country. Eligibility has expanded into more than two dozen additional countries, including Bahrain, Croatia, Estonia, Jordan, Kuwait, Morocco, Qatar, Serbia, Slovenia, and Tunisia. A multi-country account should validate availability market by market instead of reusing an old eligibility list.
5. Decide whether to use OTP verification. It is available as a lead-quality control. Measure its effect on both completed submissions and accepted leads rather than assuming that adding verification automatically improves the final pipeline.

This distinction prevents a common planning error: lower eligibility friction does not remove implementation constraints. Your account still needs the right status, a supported campaign type, an eligible country, and a lead-delivery process that works after the form is submitted.

Design the lead handoff before you activate the asset

Lead access is only useful when a submission reaches the person or system responsible for follow-up. Google supports manual CSV downloads, email notifications, Zapier, webhooks, and the Google Ads API. Choose a primary delivery method and a recovery path before the first live submission.

Google stores Lead Form data for 60 days, but manual CSV downloads remain available for only 30 days. API exports can access up to 60 days. Those are operational deadlines, not archival guarantees. Your CRM or another controlled business system should become the durable system of record.

Run a controlled handoff test before activation:

1. Submit a test through each campaign type and country configuration you intend to use.
2. Verify that every required field arrives in the correct destination and maps to the expected CRM field.
3. Confirm that the lead receives an owner and enters the intended follow-up workflow.
4. Document who investigates a failed email, Zapier run, webhook request, or API export.
5. Schedule reconciliation frequently enough that a failure cannot remain hidden beyond the 30-day manual-download window.

A notification is not the same as successful ingestion. Your acceptance test should end only when the submission appears in the destination system with the correct fields and owner.

Build one control sheet for defaults, eligibility, and retention

The durable fix is an account-level record of intended behavior. Keep it alongside your campaign launch checklist and include:

• Campaign name, type, market, and accountable owner.
• Intended Shopping inventory: online, local, or both.
• The enforcement layer: an ONLINE listing scope, an Inventory filter, or a documented mixed-inventory decision.
• Google Ads API version, integration owner, and the location of any remaining enable_local write operation.
• Advertiser Verification status and the date Lead Form access was confirmed in the account.
• The supported campaign type and country used for each Lead Form asset.
• Primary lead-delivery method, fallback method, and failure-monitoring owner.
• The 30-day CSV deadline, 60-day storage limit, and date of the latest successful handoff test.

Finish the Shopping review before August 31: remove unexplained uses of enable_local=false and replace every intentional online-only rule with an enforceable scope or filter. Then test Lead Form eligibility separately in each account. If access is present, activate it only after a complete submission reaches its assigned destination.

References

• Search Engine Land — Google confirms Local Inventory Ads will be enabled by default
• Search Engine Land — Google drops $50K ad spend requirement for Lead Form assets