November has been quiet on new Meta ad formats and busy on defaults. Some features can now switch on unless a tool sends an explicit opt-out. Others have only been spotted in one account, which is a different kind of change and needs a different kind of check.
This guide sticks to what Meta published on 4 November, what PPC Land reported on 6 November, and what the CMA has said about the paused terms. It does not treat a reported checkbox as a confirmed default.
What changed at a glance
| Change | Where it lives | What the source says | How to keep control |
|---|---|---|---|
| Product showcase | Marketing API v27.0, for creatives with no Product showcase setting | Meta may turn it on when it has a high-confidence match to a product set in your catalogue. Older API versions do not change. | Set Product showcase to opt out in the creative features spec |
| Reach more people across other mobile devices | New eligible Sales ad sets that target specific devices or operating systems | On when the device setting is left out. Existing ad sets do not change. | Set the device setting to 0 |
| Detected offers | Commerce Manager, Settings, Offer merchandising | Reported ticked in one account on 6 November. Default, start date and which accounts have it are not confirmed. | Untick Detected offers if the box is there and you do not want it |
| Lookalike location fields | New Lookalike audiences via the API | Rejected on v27.0 from 4 November. Meta says the same rejection reaches remaining versions about 90 days later, date to be confirmed. | Remove country and location fields. Locations come from the ad set |
| Updated commercial terms | Business terms for advertisers | Put on hold. A Help Center notice, via a November round-up, says they will not take effect on 20 November 2026. | Nothing to sign yet. Existing terms remain in effect, on that account |
Product showcase can now switch on by itself
On 4 November 2026 Meta released Graph API v27.0 and Marketing API v27.0. From that version, Meta may turn on Product showcase when you create an ad whose creative has no Product showcase setting. It says it only does this when it has high confidence that a specific product set in your catalogue matches the ad. The ad can then show closely matched products. Versions before v27.0 do not change.
Meta calls the feature optional. The opt-out is a setting in the creative features spec: product extensions enrol status set to opt out. If a tool, uploader or script has moved to v27.0 and does not send that opt-out, the new behaviour applies. The release notes describe the API. They do not say Ads Manager does the same thing.
A clean catalogue can make the extra products useful. It is a weaker fit when the catalogue includes lines you are not promoting, when the ad is a brand message, or when a creator ad needs the product on screen to match what the creator is using. The same opt-out habit showed up with product browsing in October, covered in Meta product browsing: should UK advertisers opt out?
Device targeting now widens by default
The same release says new eligible Sales ad sets that target specific mobile devices or operating systems have "Reach more people across other mobile devices" turned on when the device setting is left out. Meta can then deliver to other devices and operating systems when it expects that to improve performance. To keep the devices and systems you named, set the device setting to 0.
- Existing ad sets do not change. The default is for new ad sets.
- Two cases are excluded. The setting is not available for the Mobile App conversion location or for Special Ad Categories.
- Older API versions follow later. Meta says the default reaches all versions about 90 days after the v27.0 launch, which it gives as February 2027, with the exact date still to be confirmed.
If an offer or a landing page only works well on one system, an ad set labelled for that system may no longer be limited to it. Check the setting before you read a device report. Placement and creative defaults have moved the same way, which we covered when placement controls were removed and with Advantage+ creative automation.
Detected offers: discounts from your website in your ads
This is not in the 4 November API notes, and PPC Land says it could not find a Meta announcement for it. On 6 November, PPC Land reported a LinkedIn post by Bram Van der Hallen. In the Commerce Manager account he showed, Settings then Offer merchandising had a checkbox called "Detected offers", described as "Display offers detected from your website and ads". The box was ticked in that account. Two further boxes, Sale events and Seasonal event names, were also ticked, for ads that lead to a shop or to product browsing.
The same report publishes Meta's own notice in the "Duplicate your ad" dialog: "Eligible promotions can appear with your new ad, even though promotions are turned off for your original ad." The notice points people to Commerce Manager.
What the report does not establish, and what we will not fill in, is whether Meta ticks the box by default, when the page appeared, which countries have it, or whether a live ad (not only a copy) can pick up an offer. That is why the check is "open Commerce Manager and look", not "assume it is on".
If the box is on, an expired code, a members-only discount or a sale you are about to end could show on an ad you did not write the offer into. As peak trading approaches, copied ads are common, and the notice is specifically about copies. If you leave Detected offers on, the offers on the site need to be ones you will stand behind in public. If each ad has to stand alone, untick the box and tell anyone else who works in the account.
Smaller API changes worth passing to your developer
The same v27.0 notes include changes that break a request rather than change who sees an ad:
- Lookalike audiences. From 4 November, v27.0 rejects a new Lookalike that includes country or location fields in the lookalike spec. Meta says those fields had no effect, because delivery locations come from the ad set. Existing Lookalikes keep running. The rejection is due on remaining versions about 90 days later, date to be confirmed.
- Catalogue batch. The catalogue batch endpoint stops working on v27.0. Integrations should use the items batch endpoint. Older versions keep the old endpoint until those versions are dropped.
- A Page video metric. Total video consumption rate stops returning data on every Graph API version from early November 2026. Meta says there is no direct replacement.
- AI disclosure on Page posts. Apps on v27.0 can set a post as AI-generated, or clear that label, when editing a Page post. Older versions do not gain that parameter.
- Version retirements. Graph API v21.0 is removed on 21 January 2027. Graph API v22.0 is removed on 20 May 2027.
The practical question for whoever runs the integration: have the Meta tools been checked against v27.0, and do they send an explicit value for device reach and for Product showcase?
What has not changed: the new terms are paused
The Competition and Markets Authority opened an investigation on 30 October 2026 into whether Meta's commercial terms could be an abuse of a dominant position. The CMA says the terms Meta planned to revise on 20 November have been put on hold, and that Meta announced a pause on 28 October. No assumption should be made that the law has been broken. The case page lists October 2026 to January 2027 for the first round of information gathering, and says those dates may change.
A round-up of November Meta changes, citing Meta's Business Help Center, says the updates to the Commercial Terms, Product Catalog Terms, Self-Serve Ad Terms and Ad Creative Generative AI Terms are paused, will not take effect on 20 November 2026, and that the existing terms remain in effect. We have not opened that Help Center page ourselves. The CMA notice is the official UK source for the hold. The Help Center wording is reported, not copied from Meta's site in this article.
Separately, the CMA is asking Meta about its Meta One business subscription and about posting external links without paying a subscription. That sits outside this investigation, and the CMA has not decided whether to take formal action. Our note on Meta One for Business UK is the earlier piece. If crawling your own site is the worry, the AI training opt-out in robots.txt is about what you can set on the site, not about Meta's terms.
A new creator breakdown for partnership ads
The same November round-up reports a new Ads Insights breakdown that groups partnership ads by the Instagram handle of the creator or partner. It says the breakdown supports impressions, reach, link clicks and video watch metrics, that it cannot be combined with other breakdowns, and that conversions are not in the supported list yet. That is the round-up's account of Meta's out-of-cycle changes, not a figure we have pulled from an account.
If you run partnership ads with more than one creator, it is a way to see whose handle is carrying reach and views without splitting every test into its own ad. It sits next to the Meta ads creative breakdown, and next to how creator ads are briefed in our UGC and creator content work.
A short Meta ads default settings check
- Commerce Manager. If you have it, open Settings, then Offer merchandising. Decide on Detected offers, Sale events and Seasonal event names on purpose. Do not assume the box is on, or off, until you see it.
- Offers on the website. Take down expired codes. Anything still visible is something Meta's reported setting can pick up.
- Copied ads. Preview a sample. Look for offer text or products you did not add.
- Tools on v27.0. Ask whether they send an explicit device value and an explicit Product showcase value.
- Device reports. Before you compare iOS with Android, check the new ad set was not set to reach other devices.
- Catalogue. If Product showcase stays on, prices, stock and the product set are now part of ads you did not build around those products.
- Product browsing. If that October change is still open, use the product browsing guide.
How BlackFire handles platform defaults
Our paid media service starts every campaign from a target cost per lead or return on ad spend. Tracking is part of that work, and the page says we would rather spend less and learn faster than burn budget on a good-looking guess. A new default earns its place only if it still serves that target. We check the setting when the platform changes it.
If you want that read on the account you have now, book a call. We will look at what the account is allowing Meta to switch on. There is no promised return in that conversation.
Meta ads default settings FAQs
What are the new Meta ads default settings?
From Marketing API v27.0, released on 4 November 2026, Meta may turn on Product showcase for new ads whose creatives have no Product showcase setting, when it has a high-confidence catalogue match. New eligible Sales ad sets that target specific devices have Reach more people across other mobile devices on unless the device setting is 0. Separately, a Detected offers checkbox has been reported in Commerce Manager. Meta has not said whether that box is on for every account.
Do these changes affect ads I already have running?
Meta says existing ad sets are not changed by the device-reach default, and versions before v27.0 do not change for Product showcase. Detected offers is an account setting, and the report of it does not show exactly which ads it applies to, so it is worth checking now.
How do I stop Meta adding website discounts to my ads?
PPC Land reported a Commerce Manager path: Settings, then Offer merchandising, then untick Detected offers. Meta's duplicate-ad notice, as published in that report, says eligible promotions can appear on a copy even when they were off on the original, so preview duplicated ads before publishing.
Do the changes apply in Ads Manager as well as the API?
Meta's v27.0 release notes describe the API. They do not say whether Ads Manager gets the same defaults. Check the settings in Ads Manager rather than assuming either way.
Are Meta's new advertiser terms in force in the UK?
No. The CMA says Meta put the terms it had planned for 20 November on hold. A November round-up, citing Meta's Business Help Center, says the updates are paused, will not take effect on 20 November 2026, and that the existing terms remain in effect. The CMA opened its investigation on 30 October 2026 and has made no decision.
Next step
Check Commerce Manager if you have it, and ask whoever launches the ads whether v27.0 is sending an explicit opt-out. If you want a second look at tracking, device settings and the catalogue, book a call.
A look at what the account is allowing
Book a call if you want the defaults read against the target. We will not promise a return.
Book a call

