Signal · Regulation & Trade
Enabling Local Inventory Ads by Default for Shopping Campaigns starting on August 31, 2026
What the source reported
Source-reported<h2>What is changing?</h2> <p> On <strong>August 31, 2026, </strong>we are aligning <a target="_blank" href="https://developers.google.com/google-ads/api/docs/shopping-ads/create-campaign?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog">Shopping campaigns</a> with <a target="_blank" href="https://developers.google.com/google-ads/api/performance-max/retail?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog">Performance Max for Retail campaigns</a> by enabling <a target="_blank" href="https://support.google.com/merchants/answer/14615117?hl=en">Local Inventory Ads</a> (LIA) by default. Previously, developers and advertisers had to explicitly set the <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/Campaign.ShoppingSetting?hl=en&utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog#enable_local">enable_local</a></code> field to <code>true</code> within a campaign's <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/Campaign.ShoppingSetting?hl=en&utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog">ShoppingSetting</a></code> in order to serve products in their LIA feed. </p> <p> With this change, the <code>Campaign. ShoppingSetting.enable_local</code> field will no longer have any effect on Shopping campaigns. The Google Ads API backend will automatically override this value to <code>true</code> for all Shopping campaigns, effectively turning on the "Local products" setting behind the scenes. </p> <h2>What you need to do</h2> <p> For <strong>v25.1 and future versions</strong>, you’ll need to <strong>update your code to avoid setting <code>enable_local</code> to <code>false</code></strong>, otherwise you will see a <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/ContextErrorEnum.ContextError?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog#operation_not_permitted_for_context">ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT</a></code> error. For any versions prior to v25.1, no immediate code changes are required, and any requests to mutate the <code>enable_local</code> field for a Shopping campaign will treat the value as <code>true</code>. </p> <p> If you previously relied on setting <code>enable_local</code> to <code>false</code> to prevent local offers from serving in specific Shopping campaigns, you should instead use the <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/CampaignCriterionService?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog">CampaignCriterionService</a></code> to add a <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/ListingScopeInfo?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog#dimensions[]">listing scope</a></code> with <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/ListingDimensionInfo?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog#product_channel">product_channel</a></code> set to <code><a target="_blank" href="https://developers.google.com/google-ads/api/reference/rpc/v24/ProductChannelEnum.ProductChannel?utm_campaign=adr-default-lia-aug2026&utm_source=googleblog-adsdevs&utm_medium=blog#online">ONLINE</a></code>, or use the "Inventory filter" section in the campaign settings UI to filter out local inventory and silo budgets by channel (Online vs. Local). </p> <p> Note that this change <strong>only applies to Shopping campaigns</strong>. The <code>enable_local</code> field will continue to function as before for other supported campaign types, such as Performance Max and Demand Gen. </p> <p> If you have any questions or want to discuss this post, please reach out to us on our <a target="_blank" href="http://goo.gle/ads-and-measurement-discord">“Google Advertising and Measurement Community” Discord server</a>. </p> <p><span class='byline-author'><img width="40" height="40" src="https://blogger.googleusercontent.com/img/a/AVvXsEhMd1fdKsHQ-Ld1S2S7p1QnHKGIsAxgkzDAnAZ4Ennu3TL968-LZlrDhnCAtVhhh-UUMIKK6ecAadUoYY2_S-nU6HNVWDZK4vE28WYzIilQUhe8Fh_FMOaFo5sahlfpyIV7j_sR8xS-HtM_KU_deoWN91Y3dk21HE65O2lzO4fd8aOAFTxqpd2-rVhO5XM" style="vertical-align: middle; border:none;"/> - Dora Sun - Google Ads API Team</span></p>
- Publication
- Google Ads Developers Blog · Government/Regulator
- Published
- 20th July 2026
- Original report
- ads-developers.googleblog.com
ProcIntel stores what the source published in its feed — a headline, a summary and a link. It does not store or reproduce the full article.
What ProcIntel recorded
ProcIntel-derived- Category
- Regulation & Trade
- Geography
- United States
- Organisations
- None identified
- Collected
- 3rd October 2026 · 08:09
Initial assessment ProcIntel's automatic, provisional read of this individual Signal -- Initial Significance and Initial Confidence, computed deterministically before any Event extraction or human review.
A provisional, automatically computed reading of this individual Signal, before Event extraction or human review. Not a final rating.
Initial Significance Material (41.0/100). Strongest contributor: Procurement Impact (27.0/30 points). Limiting factor: Likely Event Severity (3.0/30 points). Initial Confidence Moderate (51.5/100, data sufficiency: Partial). Strongest contributor: Source Authority (40.0/40 points). Limiting factor: Corroboration (2.5/25 points).
- Strongest contributor
- Procurement Impact
- Limiting factor
- Likely Event Severity