The digital advertising landscape is undergoing a rapid evolution, particularly for retail brands that bridge the gap between e-commerce and physical brick-and-mortar stores. In a significant update designed to streamline retail campaigns, Google has officially confirmed that Local Inventory Ads (LIA) will be enabled by default for all Shopping campaigns starting August 31st. This update, first shared with advertisers via notifications and later detailed on the official Google Ads Developer Blog, represents a major shift in how product inventory is managed and served across Google’s network.
For search marketers, e-commerce managers, and software developers building on the Google Ads API, this change demands immediate attention. After the transition date, the ability to turn off Local Inventory Ads via a simple campaign-level setting will be removed. Organizations that rely on strict separation between their digital store budgets and physical store promotions must adapt their workflows and campaign structures to prevent unwanted local product delivery and potential budget discrepancies.
Understanding Google Local Inventory Ads (LIA)
To fully grasp the implications of Google’s latest update, it is helpful to understand the role Local Inventory Ads play in modern search engine marketing. Local Inventory Ads allow brick-and-mortar retailers to showcase their in-store products and store information to nearby shoppers searching on Google. When a user searches for a product available close to their location, an LIA can appear, displaying the item’s price, in-store availability, store hours, and distance to the nearest physical location.
Clicking on a Local Inventory Ad typically directs the shopper to a Google-hosted local storefront page or directly to the merchant’s own site with local store availability highlighted. This format is incredibly valuable for driving foot traffic, facilitating “Buy Online, Pick Up In Store” (BOPIS) services, and capturing high-intent local shoppers who are ready to make immediate purchases.
Historically, managing LIAs required active participation from the advertiser. Brands had to upload a local product inventory feed to Google Merchant Center, link it to their Google Ads account, and explicitly opt-in to display local inventory within their Google Shopping campaigns. With Google’s upcoming change, this opt-in model is officially transitioning to an opt-out framework through alternative configuration methods.
The Technical Shift: What is Changing on August 31st?
Beginning August 31st, Google will automatically activate the “Local products” feature across all active and newly created Shopping campaigns. This change effectively aligns traditional Shopping campaigns with Performance Max for Retail campaigns, which have featured Local Inventory Ads by default since their inception.
Under the old configuration model, developers and advertisers used the Google Ads API to explicitly set the enable_local boolean field to true within a campaign’s ShoppingSetting. This action informed Google’s ad-serving engine to pull from both the online product feed and the local inventory feed when displaying search results.
Following the August 31st update, the following changes will go into effect:
- Every Google Shopping campaign will have Local Inventory Ads enabled by default.
- The
Campaign.ShoppingSetting.enable_localfield will be completely ignored by Google’s backend systems. - Google’s ad server will automatically treat the
enable_localparameter astrue, regardless of the actual value submitted via the API or set in manual campaign uploads.
This structural change simplifies campaign setup for retailers who want maximum reach across both digital and physical touchpoints. However, it also removes a simple toggle control that thousands of enterprise advertisers have relied on to segment their online-only and offline-only retail campaigns.
Developer Implications and Google Ads API Behavior
For developers, system integrators, and AdTech providers, this update requires direct code audits. Depending on the version of the Google Ads API your platform currently targets, attempting to set or modify the local inventory configuration will trigger different behaviors.
Behavior in Google Ads API v25.1 and Later
If your development workflow or advertising software utilizes Google Ads API version v25.1 or any subsequent versions, you must update your code to stop attempting to set the enable_local field to false. When the change goes live, any API request attempting to write a false value to this property will be rejected by Google’s servers. The API will return the following error code:
ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT
To avoid failed API calls, broken campaign creation scripts, and synchronization errors within your proprietary tools, developers should remove the logic that pushes enable_local = false during the Shopping campaign creation or modification process.
Behavior in Legacy API Versions (Prior to v25.1)
For development environments running on legacy versions of the Google Ads API (prior to v25.1), existing code will continue to execute without throwing direct API errors. However, any attempts to set enable_local to false will be silently ignored by Google. The system will process the API request successfully, but it will treat the parameter as true, automatically enabling Local Inventory Ads for the target Shopping campaign.
How to Prevent Local Products from Serving
While Google’s goal is to maximize ad coverage and simplify setups, many enterprise advertisers require isolated campaign structures. For instance, a brand might use separate budgets, targeting rules, and ROAS (Return on Ad Spend) targets for online sales versus in-store promotions. If your business strategy dictates that certain Shopping campaigns must remain online-only, you cannot rely on the default campaign settings anymore.
Fortunately, Google is shifting control away from a broad campaign-level switch to more granular inventory filtering methods. Advertisers have two primary alternatives to prevent local products from serving in specific Shopping campaigns.
Option 1: Using CampaignCriterionService and Product Channel Settings
The most precise technical method to enforce online-only delivery is to define a listing scope using the CampaignCriterionService. By targeting this service, you can restrict the campaign’s eligible items based on the product channel.
To restrict a campaign to digital-only inventory, developers can programmatically set the product_channel attribute to ONLINE. By explicitly defining the scope to filter out local product channels, the campaign will ignore any physical store inventory feeds linked in Google Merchant Center, effectively keeping the campaign limited to e-commerce delivery.
Option 2: Utilizing the Google Ads UI Inventory Filter
For search engine marketing (SEM) specialists and managers who prefer using the web interface rather than writing custom code, Google Ads provides an native inventory filter in the campaign settings dashboard.
By navigating to the settings of a specific Shopping campaign, advertisers can apply an inventory filter that excludes physical store products. This configuration lets you segregate budgets dynamically, ensuring that your designated online campaigns do not spend capital driving physical store visits, while dedicated local campaigns can focus entirely on offline consumer actions.
What is Not Affected by the Update
It is important to note that this update is highly targeted and does not impact every campaign type across the Google Ads platform. The default enablement and the deprecation of the enable_local toggle apply exclusively to standard **Shopping campaigns**.
The enable_local field will continue to function normally and remain fully supported for other campaign types, including:
- Performance Max Campaigns: These multi-channel campaigns will still process local configurations dynamically based on campaign goals.
- Demand Gen Campaigns: These visually-rich, audience-focused campaigns will retain their existing configurations without forced overrides to the local inventory parameters.
Why Google is Shifting to Default Local Inventory Ads
This strategic move by Google highlights a broader trend toward automation, consolidated bidding structures, and omnichannel commerce. In the modern retail environment, consumers rarely follow a linear path to purchase. A shopper might research a product on their mobile device while commuting, check if it is available at a nearby storefront, and then make a decision to purchase in-person or buy online later that evening.
By enabling Local Inventory Ads by default, Google is helping merchants present a more complete representation of their product availability. When Google’s algorithms have access to both online and physical inventory data, they can optimize ad delivery more effectively, showing the most relevant ad format based on the searcher’s physical proximity, past behaviors, and search intent.
Additionally, this shift simplifies the onboarding experience for newer or smaller retailers who may not have the technical resources to navigate complex API settings or deep campaign configurations. By lowering the barrier to entry for LIA adoption, Google encourages more local businesses to link their physical retail presence with digital search, capturing localized market share that might otherwise go to major e-commerce marketplaces.
Action Checklist for Digital Advertisers
To ensure a smooth transition ahead of the August 31st deadline, retail advertisers and digital marketing agencies should complete the following steps:
- Audit Existing Shopping Campaigns: Identify all active Google Shopping campaigns that currently have Local Inventory Ads disabled. Determine if these campaigns need to remain online-only or if they can benefit from localized ad delivery.
- Update API Codebases: If your team utilizes custom-built bidding platforms, campaign creators, or third-party search management tools, ensure developers remove the
enable_local = falseparameter to preventOPERATION_NOT_PERMITTED_FOR_CONTEXTerrors. - Implement Product Channel Filters: For campaigns that must remain strictly online, update your configurations using the
CampaignCriterionServiceor apply native inventory filters to exclude local channels. - Evaluate Merchant Center Feeds: Verify that your local product inventory feeds in Google Merchant Center are accurate, updated, and correctly linked to Google Ads to prevent serving out-of-stock items or incorrect pricing to nearby shoppers.
- Monitor Performance Post-Launch: Keep a close eye on campaign performance, click-through rates (CTR), and CPCs after August 31st to assess how the automated enablement of LIAs affects your overall ad delivery metrics.
As Google continues to advance its retail advertising ecosystem, staying ahead of structural API and campaign updates is essential. By taking proactive steps today, you can maintain seamless operations, protect your marketing budgets, and effectively target consumers wherever they choose to shop.