# Google will extract landing-page images for new Performance Max campaigns by default — even when accounts opt out From December 4, Google Ads will default new Performance Max campaigns to website-image extraction even where the advertiser disabled Dynamic Image Extensions at account level. API integrations must explicitly opt out per campaign. Google is changing the default for Performance Max image extraction on December 4, 2026. Existing campaigns keep their settings, but new campaigns will opt in regardless of an account-level opt-out; agencies and SaaS ad tools need a campaign-level override and careful handling of repeated asset settings. - Status: Active - Published: 2026-10-26T20:19:35+13:00 - Updated: 2026-10-26T20:19:35+13:00 - Categories: Web Development, Marketing & Distribution, Developer Tools, Paid Acquisition - Tags: advertising automation, Google Ads, Google Ads API, Performance Max - Canonical HTML: https://beyondthe.news/dossiers/google-performance-max-image-extraction-december-2026-campaign-opt-out ## What changed On October 21, 2026, Google announced that from December 4, 2026 the GENERATE_IMAGE_EXTRACTION asset automation setting will default to OPTED_IN for newly created Performance Max campaigns in Google Ads, Ads Editor and the Google Ads API. Until now, campaigns with no explicit setting inherited the account-level Dynamic Image Extensions choice. The new default applies even when isImageExtractionAdExtensionEnabled is false at account level. Existing campaigns retain their configurations. Advertisers who do not want their landing-page images used must explicitly set GENERATE_IMAGE_EXTRACTION to OPTED_OUT on each new campaign. ## Why it matters A previously trusted account-level safety preference will no longer govern new campaigns. Agencies, ad-automation SaaS products and in-house API integrations that create Performance Max campaigns may unexpectedly allow Google's automated asset system to take images from landing pages. That raises practical brand-control and commercial-image-rights questions; an API tool must encode the opt-out as a campaign property rather than assuming the account default protects customers. It is a timed migration task, not merely a new creative option. ## Account-level opt-outs no longer control new campaigns Google says the new OPTED_IN default will apply to Performance Max campaigns created on or after December 4, regardless of the account-level Dynamic Image Extensions setting. Existing campaigns are not automatically changed. The setting affects Google's ability to select high-resolution images from the advertiser's landing pages for ads across its inventory, including Search, YouTube, Display, Discover, Gmail and Maps. ## API integrations need an explicit campaign-level decision In the Google Ads API, set asset_automation_settings on the Campaign resource with asset_automation_type GENERATE_IMAGE_EXTRACTION and asset_automation_status OPTED_OUT when a customer declines extraction. This is a campaign setting, not a global account flag. Integrations that clone templates or create campaigns in bulk should audit their creation payloads and test the resulting state before December 4. ## Updating a campaign can overwrite unrelated asset settings Google warns that asset_automation_settings is a repeated field: sending a new set replaces the entire array, rather than merging one entry. Before updating an existing campaign, retrieve all current settings, modify the image-extraction entry, and include the other desired settings such as text automation. A partial update can silently clear other asset-automation preferences. ## The source material and evidence boundary Google's October 21 developer notice provides the effective date, affected interfaces and REST example. PPC Land independently explains the account-versus-campaign implications and the six-week implementation window. Google's notice does not claim existing campaigns will be forcibly switched on, and this dossier does not imply all extracted images are automatically used in every ad. ## Key details - Announced October 21, 2026; effective December 4, 2026 for newly created Performance Max campaigns. - New default: GENERATE_IMAGE_EXTRACTION = OPTED_IN even if account-level Dynamic Image Extensions are disabled. - Explicit campaign-level OPTED_OUT is required to prevent extraction on new campaigns. - Existing campaigns retain their current configuration. - API updates to repeated asset_automation_settings replace the array; preserve other settings. - Google advises advertisers to confirm commercial usage rights for landing-page images. ## Builder takeaways - Audit all Performance Max creation code, templates and bulk import paths for explicit image-extraction settings. - Add a clear per-customer choice and persist it at the campaign level; do not treat account-level opt-out as authoritative after December 4. - For updates, read and round-trip the full asset_automation_settings array to avoid overwriting unrelated automation preferences. - Check rights and licences for images published on landing pages before allowing automated extraction. ## What to watch - Whether Google publishes further migration examples or auditing tools before December 4. - Whether client libraries and campaign-management SaaS tools expose an explicit extraction opt-out by the deadline. - Any change in Google Ads policy or enforcement regarding commercial rights to extracted landing-page imagery. ## Uncertainties - Google does not quantify how many existing integrations rely on inherited account-level settings. - The announcement does not promise that every eligible extracted image will be served; eligibility and creative selection remain conditional. - The impact depends on each advertiser's account settings, campaign creation workflow and rights to site imagery. ## Sources - [Upcoming changes to image extraction in Performance Max campaigns starting December 4, 2026](https://ads-developers.googleblog.com/2026/10/upcoming-changes-to-image-extraction-in.html) — Google Ads Developer Blog · primary announcement and API guidance · 2026-10-21T00:00:00+13:00. Effective date, account override, campaign REST example and repeated-field update caution. - [Google turns on PMax image extraction by default from December 4](https://ppc.land/google-turns-on-pmax-image-extraction-by-default-from-december-4/) — PPC Land · independent specialist reporting · 2026-10-21T00:00:00+13:00. Independently examines opt-out implications, prior defaults and developer migration deadline. - [Asset automation type API diff](https://developers.google.com/google-ads/api/diff-tool/v22/versus-v21/diffs/enums/asset_automation_type) — Google for Developers · primary API reference · 2026-07-20T00:00:00+12:00. Confirms enumeration for GENERATE_IMAGE_EXTRACTION and campaign automation types.