On October 28, Meta Puts a Shopping Screen Between Your Ad and Your Sales Page. It Switches Itself On.

Eleven days from now, the thing that happens after someone taps your Facebook ad may stop being your landing page.

On October 14, Meta notified advertisers that product browsing will be automatically enabled for all existing Facebook and Instagram ads starting October 28, 2026. The key word in the notice is "existing." Product browsing is not a new capability — advertisers could already switch it on for individual ads. What changes on October 28 is the default for ads that are already running: off becomes on, and anyone who wants the old behavior has to act.

The notice's headline reads: "Starting October 28, 2026, we'll add product browsing to your existing ads." Tap the ad, and people may see an experience inside Facebook or Instagram with product info and personalized suggestions before they ever land on your domain.

As one analysis put it: "The creative does not change; the first screen after the tap does."

The justification is a number Meta won't break down

Meta attaches the change to a claim that businesses saw 3% more conversions on average in an experiment run between August 6 and August 21, 2026, across about 117,700 advertisers.

That's the whole case. Meta does not specify which conversion types are counted — in-app purchases, actions on external sites — and omits ROAS, CPC and average order value. The announcement also doesn't state which campaign objectives and placements the feature applies to, referring to active ads without further clarification.

For a course business, that last omission is the entire question. The only official trace of the feature is a Help Center page on ad destinations, which lists product browsing under personalized destinations for the Sales objective with a website conversion location. If your funnel runs on a Leads objective to a webinar registration, you may be untouched. The notice doesn't say that. As of October 15, Meta had not published a Help Center article, changelog entry or newsroom post about any of it. The October 28 date comes from advertisers who received the notice, not from a public Meta page.

Some advertisers on X are calling it "forced product browsing."

The exact opt-out path

Two routes: the "Opt out" button in the Meta notification sent to your account, or Ads Manager → open an active ad → Advantage+ Creative and Destination settings → toggle product browsing off. Ads Uploader reports the switch sits under "Personalized destinations" as "Product browsing."

The two are not equivalent. The notice button has to be used before October 28, and what it covers is not stated — one ad account, every account an advertiser manages, a business portfolio, or only the account the notice was addressed to. The per-ad toggle still works after the date, one ad at a time.

If you manage three ad accounts across a personal brand, a course LLC and a client, assume nothing about scope. Check each.

There's also no clean way to do this in code. When Meta defaulted Dynamic Media on for Advantage+ catalog ads between September 1 and October 20, 2025, it shipped an API opt-out field, OPT_OUT, so advertisers managing ads through the Marketing API could decline programmatically. The product browsing notice references no equivalent field.

What to watch the week after

Meta's notice does not clarify the default for new ads created after October 28, which means checking Advantage+ Creative settings on every new campaign launched into November. The notice is also silent on duplicated ads and ads created through the API.

If you leave it on, the honest expectation is messier attribution before cleaner numbers. An extra Meta-owned screen means a slice of your taps resolve inside the app rather than on your site, and your pixel only sees whoever walks out the other side. Watch landing page views against link clicks from October 28 onward. A widening gap is the tell.

The timing is not subtle. October 28 is the opt-out deadline; Black Friday falls on November 27 and Cyber Monday on November 30. Which is to say: the default flips exactly when a Q4 launch calendar is least forgiving of a variable nobody tested.