Google Will Scrape Your Black Friday Banners Into PMax Ads From Dec 4
Google will switch on image extraction by default for every new Performance Max campaign created from December 4, 2026, according to a Google Ads API announcement reported by PPC Land. The account-level Dynamic images setting will stop protecting new campaigns, so accounts that opted out years ago will get landing page images in every new PMax campaign unless each one opts out on its own.
That second part is the bit I'd circle in red. Most advertisers who turned off Dynamic images did it once, at the account level, and then forgot about it, which is exactly what an account-level setting is supposed to let you do. After December 4, that switch still exists and still looks like it's doing something. For new PMax campaigns, it isn't.
The switch you trusted stops counting on new campaigns
Here's how it works today. Google's asset automation settings documentation lists the default for GENERATE_IMAGE_EXTRACTION as "the account-level Dynamic Image Extension control value." In plain English: if you said no at the account level, new campaigns inherited your no. Google's own help page on landing page images describes the same thing from the UI side, where new PMax campaigns get landing page images turned on only if the account is opted into Dynamic images.
From December 4, per PPC Land's write-up of the announcement, the campaign-level default becomes OPTED_IN regardless of what the account says. It applies across the API, the Google Ads UI and Google Ads Editor. Existing campaigns "will retain their current configurations," so nothing you're running today changes overnight. The exposure is everything you build after that date.
The account setting you rely on stops counting on December 4.
It's a bit like leaving a "do not disturb" sign on the door and then the hotel hires a new cleaning crew that was never told to read signs. The sign is still there. Nobody's checking it.
December 4 is an awkward week to flip this
Black Friday lands on November 27 this year. That means December 4 falls right in the stretch where a lot of accounts spin up new PMax campaigns for shipping-deadline pushes, last-minute gift guides, Boxing Day and January clearance. And it's also the week when plenty of landing pages are still wearing their Black Friday clothes, because nobody has had time to clean them up yet.
So picture what the extractor finds on a typical retail page in early December: a hero banner that says "40% off ends Monday," a countdown timer graphic, a lifestyle photo licensed from a stock library, maybe a creator's photo you got permission to use on your site (but only your site). Google says the system pulls high-resolution images to widen reach across Search, YouTube, Display, Discover, Gmail and Maps. It doesn't say it reads the date on your banner.
To be fair to Google, the help page says extracted images go through "automated and manual quality checks before they can serve." On paper, that sounds reassuring. And sometimes it probably is. But those checks seem to be about policy and image quality, not about whether your Cyber Monday offer expired nine days ago. A crisp, well-lit, totally compliant banner advertising a dead promotion will sail through, I'd guess.
Then there's the rights question, which I think gets underplayed. When you turn this on, Google's help page says "you're confirming that you own all legal rights to the images on your landing page" and that Google can use them for advertising. A lot of stock licenses and creator agreements cover web use and stop short of paid media. If the extractor grabs one of those, the liability seems to sit with you, not Google. Most teams I'd bet have never cross-checked their site imagery against their license terms because, until now, they didn't have to.
Google keeps moving the defaults in one direction
Image extraction is one of several toggles moving the same way, and honestly, the pattern matters more than any single one. PPC Land has tracked a run of automation features flipped to on: website coupons auto-applied to some campaigns from October 12, AI voice-overs on Performance Max videos earlier this year, and more. The same API doc shows GENERATE_IMAGE_ENHANCEMENT and TEXT_ASSET_AUTOMATION already enabled by default for PMax.
Meta is doing the same thing, for what it's worth. We wrote about how Meta picked late October to default product browsing into live ads, and the timing complaint is basically identical. Platforms seem to roll out default-on creative automation right before the period when advertisers are least likely to be auditing settings. I doubt there's anything sinister in it. Q4 is simply when the inventory is most valuable and every extra asset helps fill it.
And to be honest, it isn't entirely new. When Google announced landing page images back in April 2025, the language was all about it being a control you opt into. Eighteen months later the opt-in became inherited, and now inherited becomes on. That trajectory is the real story.
The API trap that can quietly wipe your other settings
If you build campaigns through scripts, a tool, or an agency platform that sits on the API, there's a nastier detail buried in the announcement. PPC Land notes that asset_automation_settings is a repeated field, and updates replace the entire array instead of merging into it. Send an update with only the image extraction entry set to OPTED_OUT, and you can erase other entries like your TEXT_ASSET_AUTOMATION choice in the same move.
What you end up with is a fix for one automation that quietly turns another one back to its default, and honestly that's the kind of bug nobody notices until a client asks why the headlines changed. The safe pattern is read first, then write the full array back with every setting you want to keep.
Google also published a GAQL query that pulls campaign.asset_automation_settings for PMax campaigns. Any campaign without an explicit image extraction entry is still leaning on the account setting, which is fine today. It's worth knowing which ones those are anyway.
A 20-minute image audit before December 4
None of this needs a big project. Here's roughly how I'd run it this week:
- List the PMax campaigns you plan to create after December 3. Holiday shipping pushes, January sale, new product launches. Those are the only ones the new default touches.
- Open every final URL and screenshot the images above the fold. Flag anything with a price, a percentage, a date, a countdown, or a person you don't have paid-media rights to.
- Use a simple threshold. If more than 1 in 5 of a page's prominent images carries baked-in promo text or questionable licensing, opt that campaign out. Below that, extraction is probably fine and might even help.
- Build the opt-out into your campaign checklist. In the UI it's under Campaign settings, the Images tile, then the "Landing page images" checkbox, per Google's help page. For API tools, add
GENERATE_IMAGE_EXTRACTIONwithOPTED_OUTto the creation payload before the date. - Check the asset report a week after launch. If you left it on, look at which images actually served before you assume they were the good ones.
The threshold in step 3 is my own rule of thumb, not anything Google publishes. Adjust it. The point is to make the decision on purpose.
One odd gap PPC Land's Luis Rijo flagged: the announcement gives two dates and doesn't say whether a campaign created on December 4 itself follows the old rule or the new one. I'd treat December 3 as the last safe day and stop guessing.
Leave it on, but not by accident
I'm not even sure extraction is a bad feature. For a brand with clean product photography and evergreen pages, more image variety across Discover and YouTube probably helps, and Google wouldn't keep pushing it if the averages looked terrible. My prediction: by the end of Q1 2027, more than half of new PMax campaigns in accounts that had Dynamic images switched off will be serving extracted images, mostly because nobody touched the checkbox.
The outcome worth avoiding is pretty narrow: your January clearance ad shows a Black Friday banner and you only find out from a customer screenshot.