Google Officially Confirms Local Inventory Ads Enabled by Default for All Shopping Campaigns Beginning August 31

The digital advertising landscape is set for a significant structural shift as Google officially confirms that Local Inventory Ads (LIA) will be enabled by default for all Shopping campaigns starting August 31. This announcement, detailed via the Google Ads Developer Blog, follows a preliminary notification sent to advertisers last week and marks a definitive move by the search giant to integrate physical storefront data more deeply into its core e-commerce advertising products. The update effectively removes the manual opt-in requirement for local product visibility, signaling a broader strategy to streamline omnichannel marketing across the Google Ads ecosystem.

For years, Local Inventory Ads have served as a vital bridge between online search queries and brick-and-mortar sales. By displaying real-time product availability, store hours, and distance to the nearest location, LIAs allow retailers to capture high-intent "near me" traffic. Previously, this feature required a conscious configuration by account managers or developers. However, the upcoming change will automate this process, ensuring that any Shopping campaign with access to a local product feed will automatically serve those products to nearby users unless specific preventative measures are taken.

The Technical Evolution of Shopping Settings

At the heart of this transition is a change to the Google Ads API and the way ShoppingSetting configurations are handled. Under the current system, advertisers maintain granular control over whether their Shopping campaigns display local products by toggling the enable_local field. Setting this value to true activates the local inventory feed, while false keeps the campaign strictly focused on e-commerce and home-delivery offerings.

Starting August 31, Google will transition this field to a default true state for all Shopping campaigns. The implications for developers are immediate and require a review of existing codebases. For those utilizing Google Ads API v25.1 or later, any attempt to programmatically set enable_local to false will result in a SettingError.VALUE_NOT_SUPPORTED_FOR_CAMPAIGN_TYPE error. For developers operating on versions earlier than v25.1, the API will technically accept the false command to avoid breaking legacy integrations, but the instruction will be silently ignored. In these cases, Google will treat the value as true, effectively overriding the advertiser’s intent within the campaign settings.

This technical shift aligns the traditional Shopping campaign structure with Performance Max for Retail. Performance Max, Google’s AI-driven campaign type, already operates with Local Inventory Ads enabled by default. By mirroring this behavior in standard Shopping campaigns, Google is creating a more uniform experience for retailers, though it does so at the cost of traditional manual control.

Chronology of the Rollout

The path to this mandatory enablement has been relatively swift, reflecting Google’s confidence in the value of local inventory data.

1. Early 2024: Google begins emphasizing the "Omnichannel" approach in its quarterly updates, encouraging retailers to link their Google Merchant Center (GMC) local feeds with Performance Max.
2. Late July 2024: Private notifications are dispatched to high-volume advertisers and agency partners, warning of a shift in default behaviors for Shopping campaigns.
3. August 2024: Google publishes a formal update on the Google Ads Developer Blog, providing the August 31 deadline and outlining the specific API error codes developers can expect.
4. August 31, 2024: The global rollout takes effect. All existing and new Shopping campaigns will have the "Local products" setting enabled by default.

Understanding the Importance of Local Inventory Data

The decision to mandate LIA enablement is supported by a wealth of consumer behavior data. According to industry benchmarks, approximately 80% of shoppers are more likely to visit a physical store if they can confirm a product’s availability online beforehand. Furthermore, "near me" searches have seen a multi-hundred-percent increase over the last five years, evolving from simple "restaurants near me" queries to specific product searches like "ergonomic office chairs in stock near me."

By making LIAs the default, Google is essentially forcing a "best practice" on the industry. From Google’s perspective, a Shopping campaign that ignores local inventory is an incomplete representation of a retailer’s value proposition. For the consumer, the change results in a more relevant search experience where they can choose between waiting for a shipment or picking up an item immediately. For Google, this increases the utility of its search engine as a shopping tool, competing more effectively against Amazon, which lacks a comparable network of diverse physical retail partners for immediate local pickup across all categories.

Strategic Implications for Advertisers and Retailers

While the shift toward local integration is generally viewed as a positive for conversion rates, it introduces complexities in campaign management, budget allocation, and inventory accuracy. Advertisers who have historically separated their "Online-Only" and "Local-Only" campaigns to manage different Return on Ad Spend (ROAS) targets may find their strategies disrupted.

Local Inventory Ads often carry a different cost-per-click (CPC) and conversion profile than standard Shopping ads. A user clicking on a local ad may not purchase online but may visit the store and buy the product—a conversion that is harder to track without robust Store Visit conversions or offline conversion imports. By merging these by default, Google is pushing advertisers toward a more holistic view of "Total ROAS," which includes both digital and physical sales.

However, this "forced" enablement could lead to inefficiencies if a retailer’s local data is inaccurate. If a campaign displays an item as "in-stock" at a nearby store when it is actually sold out, it creates a negative customer experience and wasted ad spend. Therefore, the burden of data integrity in the Google Merchant Center becomes even more critical after August 31.

Methods for Disabling Local Inventory Serving

Recognizing that some advertisers have legitimate business reasons to keep local inventory out of specific campaigns—such as limited-time online exclusives or specific regional logistics constraints—Google has provided two primary workarounds. The shift is effectively moving control away from a simple "on/off" switch in campaign settings to a more nuanced "filtering" approach.

1. Inventory Filtering via Campaign Settings
Advertisers can use the "Inventory Filter" feature within the Shopping campaign settings. By setting filters based on attributes such as "Channel" or "Custom Labels," an advertiser can restrict a campaign to only serve "Online" products. This allows the enable_local setting to remain true at the campaign level while effectively blocking local products from participating in the auction.

2. Removal of Local Product Feeds
The most absolute way to prevent local products from serving is to remove the Local Product Feed or the Local Product Inventory Feed from the linked Google Merchant Center account. Without a source of local data, the campaign will have no local products to display, regardless of the default settings. However, this is a "nuclear option" that affects the entire account rather than individual campaigns.

Broader Impact on the Digital Marketing Ecosystem

This update does not apply to all campaign types. Google confirmed that the enable_local field will continue to function as usual for Display, Video, Search, and Demand Gen campaigns. The focus remains strictly on Shopping, which is the primary vehicle for product-based discovery.

Industry analysts suggest that this move is a precursor to further automation in the retail space. As Google continues to push "Gemini-powered" advertising solutions, the requirement for manual configuration is being systematically removed in favor of "goal-based" advertising. In this new paradigm, the advertiser provides the assets (the product feed and store locations), and Google’s algorithms determine the best way to serve that information to the user—whether that be an e-commerce link or a local store map.

Furthermore, this change places additional pressure on smaller retailers who may not have sophisticated inventory management systems. To compete in a world where LIA is the default, small businesses must ensure their digital inventory matches their physical shelves in near real-time. This may drive a secondary market for inventory-syncing software and POS (Point of Sale) integrations that feed directly into the Google Merchant Center.

Analysis of the "Default-On" Strategy

Google’s transition to "default-on" settings is a recurring theme in its platform’s evolution. Similar transitions occurred with "Close Variants" in keyword matching and the move from Expanded Text Ads to Responsive Search Ads. In each instance, the goal was to increase the volume of data available to Google’s machine learning models.

By ensuring that local inventory data is always "available" to the auction, Google can more effectively test the impact of local vs. online messaging for every user. For example, if a user is searching for a heavy appliance, Google’s AI may determine that a local inventory ad with a "Pick up today" badge is more likely to result in a conversion than an online ad with a five-day shipping estimate. Without LIA enabled, the algorithm is blind to the local option. With LIA enabled by default, Google can optimize the user experience based on real-time proximity and intent data.

Conclusion and Next Steps for Account Managers

As the August 31 deadline approaches, advertisers and agency partners should conduct a comprehensive audit of their Shopping campaigns. The priority should be identifying campaigns where local inventory was intentionally disabled and determining if that exclusion remains necessary.

If the exclusion is necessary, teams must implement inventory filters immediately to avoid a sudden influx of local traffic and potential budget shifts. Simultaneously, developers must update any automated scripts or third-party management tools that interact with the Google Ads API to ensure they do not trigger errors by attempting to pass the enable_local = false command.

Ultimately, Google’s official confirmation of this change underscores a future where the distinction between "online" and "offline" retail is increasingly irrelevant. For the modern advertiser, success will depend less on toggling individual settings and more on the quality and accuracy of the data feeds they provide to the Google ecosystem. Beginning August 31, the local storefront will no longer be an optional add-on; it will be a foundational component of the Google Shopping experience.