Meta put a discount on your ad. It read it off your site.
Meta can show a discount it detected on your website inside any ad, even a copy where promotions were off. Where the switch lives and how to audit it.
The discount in that ad was not invented by a copywriter, and it is not a language-model hallucination in the usual sense. Meta can detect offers on your website and display them inside your Facebook and Instagram ads — including in a duplicate of an ad where you had switched promotions off yourself. The control is not in Ads Manager. It is a checkbox in Commerce Manager, under Settings → Offer merchandising, and in the account where it was first documented publicly, every box on that page was already ticked. Our position is blunt: audit that page before you scale anything for the fourth quarter, and start treating offer language as an account setting you govern, not a line of copy you approve ad by ad.
The promo was not written. It was read.
On November 6, 2026, Meta ads specialist Bram Van der Hallen published a screenshot of a Commerce Manager page most advertisers have never opened. His description is the whole mechanism in three sentences: when the option to display offers detected from your website is enabled in Commerce Manager, Meta may show those offers in your ads — even when you turned that option off for the original ad.
Meta's own interface confirms the scope better than any summary. When you duplicate an ad, the platform can surface a notice telling you to manage promotions for the new ad in Commerce Manager, because eligible promotions can appear with the new ad even though promotions are turned off for your original ad. That sentence is the problem: the switch you were taught to use is the wrong switch.
Two consequences follow, and both cost money:
- The setting is account-level; the decision was ad-level. Everything you know about promotions lives inside one creative. What decides whether a discount can appear sits one level above every campaign you own.
- Expiry does not travel with the offer. A code written for a win-back list or a loyalty tier does not carry its audience when it is lifted off a page and attached to cold traffic.
That is why this is not a branding annoyance. A discount is a price claim, and an ad showing one the buyer cannot redeem is a promise made in your name and broken at payment. The refund and the chargeback land on the shop, not on the platform that inserted the sentence.
What is new is not detection. It is the reach.
Meta has been reading offers off advertiser websites since 2024. What changed is who reviews what gets used: in 2024 the advertiser confirmed each offer inside the ad; in 2025 the merchant chose which audience saw which code; in November 2026 the control is one account-level checkbox under a heading that reads «All ads», with no per-audience review, and the duplicate notice confirming that the per-ad promotion setting does not override it.
The trajectory is consistent with everything else Meta has shipped in the Advantage+ era: move the decision one level up, aggregate it, and let the system apply it, and stop asking per object. The first two versions asked you a question. This one assumes the answer.
And the blast radius grew again on October 28, 2026, when product browsing moved from opt-in to on-by-default for ads that were already running. The second block on the Offer merchandising page only touches ads that lead into a shop or product browsing experience — so ads whose owners never enrolled those experiences can now receive «Sale events» and «Seasonal event names» too.
The three switches, and what each one reads
The page has three checkboxes and they do not read the same source. Opening each one separately is the difference between a real audit and a screenshot you took once.
| Checkbox | Where it applies | What it reads | What it can do |
|---|---|---|---|
| Detected offers | All ads, account-wide | Offers detected on your website and in your ads | Attach a discount from anywhere on the site to any ad |
| Sale events | Ads leading to a shop or product browsing | Sale events detected in your ad creative text | Pull a sale mention out of a creative line and turn it into an offer element |
| Seasonal event names | Ads leading to a shop or product browsing | Seasonal names, matched to related offers | Label an offer with a season — the documented example reads «New Year's offer! Save 20%» |
Read the first row twice. The source is your website and your ads, and the destination is every ad in the account. If your site carries five kinds of offer — sitewide percentage, category discount, bundle, free-shipping threshold, email-only code — the setting does not distinguish which of them belongs to which campaign, because it was never given that information.
If you sell one price to everyone, the page is boring. If you run more than one offer, it is a liability with a checkbox.
How much offer language actually sits on a page
The abstraction gets easier to argue with a count. On November 9, 2026 I pulled the visible text of four public storefront homepages — apparel, bedding, cookware and beauty — and matched five offer families: percentage off, an explicit saved amount, free shipping, a promo code, a bundle instruction.
- Cookware: three families, with discount strings on essentially every product tile — sale prices beside struck-through list prices, plus individual savers like «Save $225 (22% off)» on a set.
- Bedding: three families in one viewport — «20% off select sheets», free shipping over $100, and a «Bundle & Save» module.
- Apparel and beauty: two and one families respectively, both built around a free-shipping threshold, the apparel one with «Up to 70% off select styles» in the announcement bar.
Four of the five returned that markup; the fifth rate-limited the request — a reminder that the page a human reads and the page a crawler reads are not always the same.
None of this is a criticism of those shops — discounting is the business model of a promotional calendar. The point is arithmetic: the setting does not read the two lines of copy in your ad, it reads every price claim on the site, including the ones written for a segment, a season or a retention flow. A shop running a Black Friday preview, a loyalty code and a bundle page has three offer universes live at once and one checkbox that does not know it.
Hence the second-order effect. If the system attaches an expired offer, the buyer is not confused — the buyer is angry, because the number was specific. Vague promises survive contact with checkout. Specific ones do not.
The inventory: one line per offer, before you touch a budget
The fix is not a copy edit, and it is certainly not asking a writer to be more careful. The fix is an inventory. In accounts we work on, the version of this that survives contact with a real promotional calendar is deliberately boring: one row per offer string, with the audience it was written for and the ads it is allowed to appear in.
| Offer string | Written for | Allowed in | Risk if it surfaces elsewhere |
|---|---|---|---|
| Sitewide 20% | Everyone | Broad prospecting, brand | Low — it is meant to be public |
| Email-only code | One list | Retention and win-back only | High — reads as a broken promise at checkout |
| Loyalty tier price | Signed-in members | Logged-in retargeting | High — non-members see a price they cannot get |
| Free shipping threshold | Cart-building | All traffic | Medium — changes the offer even when the price does not |
| Bundle instruction | Catalog browsing | Shop and product-browsing ads | Low for message, high for margin — bundles get read as discounts |
Two rules come out of that table. An offer that is not meant to be public has no business being crawlable in plain text on a page the platform can read — that is a page-design decision, and it belongs with whoever owns the site. And an offer that is public still needs an owner: the moment it can appear in a campaign nobody planned, the campaign's margin story stops being true.
The twenty-minute audit you can run this week
This is the sequence we run before a promotional peak. No engineering work, and it repeats next quarter.
- List the offers, not the ads. Pull the text of the pages your ads point to and mark every price claim. A rotating promo module counts as one offer, and if you cannot name its audience in one phrase, it is already leaking somewhere.
- Open Commerce Manager → Settings → Offer merchandising. Screenshot all three checkboxes before changing anything. If you cannot find the page you are in the wrong tool — it is neither Ads Manager nor Events Manager.
- Decide per box. Detected offers is the account-wide switch and the one that matters most. The other two only reach shop and product-browsing ads, and they read different sources: creative text and seasonal naming.
- Confirm with a duplicate. Duplicate one live ad and read the notice. If it says eligible promotions can appear with the new ad even though they were off on the original, you have reproduced the mechanism in your own account.
- Tag every copy, then read support tickets. A distinct
utm_contentper duplicate is the cheapest way to learn later that a surprise discount ran; «the code didn't work» is the same signal arriving earlier, in customer service. The outside-in version of the habit is reading competitor ads in the public Ad Library.
Do this before the budget goes up, not after. A promoted campaign multiplies whatever the account setting already does.
Who carries the price claim now
On November 20, 2026, Meta's revised Commercial Terms take effect, with an AI Features section that puts responsibility for what its AI features create — including features the platform switches on itself — onto the advertiser. Whether an auto-displayed discount falls inside that clause is not public, and it is a fair question: a discount is not a retouched photo, it is a price.
Meta's reading of sites is at least explicit: spokesperson Andy Stone described the crawling clause as pulling accurate product information from third-party sites, which is exactly what a discount is. Google took the same route on October 12, extracting promotions from advertiser websites into eligible Search and Performance Max campaigns.
That is the shift, and it is bigger than one checkbox. Offer language stopped being a message you write when the platform started reading the page you already published. The advertisers who leave this quarter clean will not have the best promo copy; they will know which offers are public, which are not, and which of the two the machine can reach.
If the inventory turns up more offers than you expected — it usually does — that is a paid media problem before it is a copy problem. Tell us what your site is currently promising and we will tell you where it can surface.
Frequently Asked Questions
Where do I turn off detected offers in Meta?
In Commerce Manager, not in Ads Manager. Open Commerce Manager, go to Settings and then Offer merchandising. The first block, headed «All ads», carries a checkbox called «Detected offers» described as «Display offers detected from your website and ads». Unticking it is the account-level switch. A second block, «Ads leading to shop or product browsing», carries «Sale events» and «Seasonal event names» for ads that open a shop or product experience inside Facebook and Instagram.
Does switching promotions off on an ad stop Meta from showing a discount?
No. Meta's own notice on duplicated ads says eligible promotions can appear with the new ad «even though promotions are turned off for your original ad», and points the advertiser to Commerce Manager to manage them. The per-ad promotion setting and the account-level detected-offers setting are two different controls in two different tools.
Is the detected-offers setting on by default?
Meta has not said. There is no announcement, no Help Center article and no statement about the default state. In the account where the setting was first documented publicly, all three checkboxes were ticked. Treat the default as unknown and check your own account rather than assuming either state.



