Meta Can Now Show an AI-Generated Page Instead of Yours. Here Is What It Does to Your Data.
Meta is testing a Landing Page Experience Enhancement that uses AI to build a visual landing page from your website and may show it to people who tap your ad instead of your site. It sits behind the 'test new AI generation features' switch in Advertising Settings, Meta caps those tests at fewer than 5% of ad impressions, and as of October 2026 there is no public documentation on whether your pixel, GA4 or forms ever fire on it.
Meta Can Now Show an AI-Generated Page Instead of Yours. Here Is What It Does to Your Data.
Meta is testing a feature called Landing Page Experience Enhancement that generates an AI visual landing page from your website and may show it to people who tap your ad instead of your site. It sits behind the "test new AI generation features" switch in Advertising Settings, Meta says the tests cover fewer than 5% of ad impressions, and as of October 2026 we know of exactly one public record of it. Because the visitor never reaches your domain, no GA4 session, no heatmap, no form and no tag on your own site can record that visit.
What follows is not one more Advantage+ feature. It is the fourth move of the same year in one clear direction: taking the destination, the events and the first conversion step off the advertiser's website and moving them inside Meta. Here is what the feature actually is, what breaks in your reporting, and what we decided to do in the accounts we manage.
What it is, in Meta's own words
The copy Meta shows in the panel is literal:
"We'll use AI to generate a visual landing page from your website, highlighting your key services and calls to action. When enabled, people who tap your ad may see this instead of your website."
Three facts matter:
- It is one of eleven tests hanging off the "test new AI generation features" switch in Advertising Settings. Jon Loomer documented the screenshot on September 7, 2026 and published the write-up two weeks later; as far as we can find, it is still the only public record.
- Meta says these tests apply to fewer than 5% of your impressions. A small number, but spread across your whole volume rather than isolated in one campaign you can carve out.
- Meta only shows a generic example. It does not say where that page is served from, whether your pixel fires on it, how it counts the conversion, or when it leaves testing.
That last line is the problem. It is not that the documentation is thin. There is no documentation.
Do not confuse it with the other "landing page experience"
Precision matters here, because Meta shipped two changes weeks apart whose names rhyme and whose consequences are opposite.
In September, landing-page quality entered the auction — the signal we have been calling Engaged Value — and that one prices your page: a slow landing with redirect chains and no trust signals pays a higher CPM. In our analysis of that signal we set out the audit framework we run before scaling any campaign.
The Landing Page Experience Enhancement does not price your page. It replaces it. One punishes you for having a bad landing; the other swaps in one you did not design. Different problems, and fixing one does nothing for the other.
What breaks when the page is not yours
When the description says "instead of your website," the consequence is mechanical: your domain never loads. Almost everything else follows from that.
| What you relied on measuring | What happens if the AI page serves the click | Confidence |
|---|---|---|
| GA4 sessions and page views | No session — the visitor never resolves your domain | High |
| Heatmaps, session replay, on-site A/B tests | Zero data from that visit | High |
| Lead forms and CRM capture | That path does not exist on the substituted visit | High |
| Your CMP and consent banner | Never runs on the substituted visit | High |
| Your pixel and server-side GTM | They do not run on a page you do not serve; Meta does not say what runs instead | High for the first half, unknown for the second |
| What Meta counts as a conversion | Unpublished. It may keep counting, model it, or ignore it | Unknown |
| Message match and CRO | You lose the first screen: copy, offer, block order | High |
Row by row the pattern is the same: your data dies, Meta's survives. And that is precisely the problem for anyone who reports on paid media by comparing Ads Manager against GA4.
If your paid traffic starts showing conversions in Meta that do not arrive with sessions in GA4, the first question is no longer "is this bot traffic?" but "how much of my click is landing on a page that is not mine?" It is still a reconciliation between the platform report and your order table — we would just have one more cause to rule out. The diagnostic we use to take suspicious traffic apart does not change: compare against orders, never against the platform.
The pattern: four changes, one direction
Seen together, 2026 is not a pile of unrelated updates.
- Landing quality enters the auction (September). Your page becomes a bidding input. → Engaged Value
- AI infers your conversion events. Every pixel created since August 3 ships with Automatic Events on by default, letting AI "identify and add missing events from your website." → our Automatic Events audit
- The first conversion step leaves the landing page. Reply to Keywords comments and DMs inside the ad itself. → the four decisions we make before turning it on
- Meta generates the destination. Landing Page Experience Enhancement builds the page whoever taps your ad will see.
Destination, events, first contact: all three are moving inside the platform. Individually each is defensible. Together they mean the funnel you are paying for starts and ends inside a system you do not instrument.
What we do in the accounts we manage
Our position is clear and it is an opinion, not documentation: we turn it off by default. The reason is simple. A client paying for traffic has the right to see that session in their own analytics; we cannot audit, cannot run CRO, and cannot reconcile what we cannot reach. If we do not reach the visit, we cannot defend the budget.
| Situation | Decision | Why |
|---|---|---|
| Performance account measured on CPA or ROAS | Off | You need a full trail to the order to defend the spend |
| Lead capture on your own forms | Off | The substituted visit has no form: Meta can report conversions your CRM never sees |
| Pure-reach brand campaign on a well-known domain | Off anyway | The cost of not measuring still exceeds the benefit of a "cleaner" landing |
| We want to understand the effect before deciding | On for ONE campaign, with a holdout and weekly reconciliation | The only honest way to measure it is to let it run and compare Ads Manager, GA4 and orders over the next seven days |
| EU traffic with your own CMP | Off | The consent banner never runs on the substituted visit |
The audit, in four steps:
- Open Advertising Settings and find "test new AI generation features." If you left it on years ago — as Loomer did — it is there, among eleven tests.
- Review the other ten while you are in there. Several of those switches change how Meta builds or measures the ad, and you only see them in your own account.
- Re-check it on every duplicated ad. Creative enhancements get inherited on duplication and do not always hold the state you think you have.
- Set a weekly reconciliation: Ads Manager conversions against GA4 sessions against real orders. Meta rises and sessions do not: investigate before you raise budget.
What we still do not know
We would like to close this piece with certainties, but the feature is new and undocumented. What we do not know, and what is worth watching in your account:
- Where that page is served from. If it is a Meta domain, your pixel does not run. If it is a proxy over your site, it might. Meta does not say.
- Whether the visit counts as a conversion for Meta. Without that, any prediction about your CPA is a guess.
- Whether it coexists with Engaged Value. Does the generated page automatically score well on the quality signal, or are you trading a CPM penalty for a conversion ceiling? Not published.
- When it leaves testing, and in which markets. There is no calendar.
So our recommendation is not "adopt the novelty." It is "turn it off, and measure it only if you want to understand it." Never build a Q4 plan on a feature Meta has not documented and whose only public record is a screenshot.
Our take
What this test reveals is strategic, not technical. Meta no longer wants you to rent a landing page. It wants your offer to be clear enough to be summarized by a model and served on a screen you do not control.
That punishes funnels unevenly. Funnels that depend on sequence — quizzes, upsells, redirect chains, long advertorials — lose exactly what made them work. Legible offers (clear service, clear price, one call to action) barely notice, because what the model repeats back is what you would have written anyway.
If your business depends on controlling the first screen, you already have your decision: turn the switch off and treat the first screen as what it always was, your own asset. If your business depends on Meta bringing you demand, start writing offers that survive being paraphrased. Both are compatible. What is not compatible is still assuming that whoever taps your ad lands where you put it.
Frequently asked questions
What is Meta's Landing Page Experience Enhancement?
It is a test inside Advertising Settings that uses AI to generate a visual landing page from your website, highlighting your key services and calls to action. In Meta's own words, when it is enabled, people who tap your ad may see that page instead of your website. It is one of eleven tests grouped under "test new AI generation features."
Where do you turn off Meta's AI-generated landing page?
In Advertising Settings, at the "test new AI generation features" switch. If you never touched it and it was already on, that is where it is. Meta says tests in that group cover fewer than 5% of ad impressions, and it is worth re-checking on every duplicated ad, because creative enhancements are inherited.
Does this feature affect GA4 and conversion measurement?
If the AI page substitutes for yours, that visit never loads your domain: GA4 records no session, your heatmap tools capture nothing and your forms do not exist on that path. Meta has not published whether its pixel fires on that page or how it counts the conversion, so the difference between Ads Manager and your analytics can only be closed by comparing both against real orders.
Frequently Asked Questions
What is Meta's Landing Page Experience Enhancement?
It is an Ads Manager test that uses AI to generate a visual landing page from your website, highlighting your key services and calls to action. In Meta's own words, when it is enabled, people who tap your ad may see that page instead of your website.
Where do you turn off Meta's AI-generated landing page?
In Advertising Settings, under the 'test new AI generation features' switch. The tests are opt-out, so they are already on if you left them on, and Meta says they apply to fewer than 5% of your ad impressions.
Does this feature affect conversion measurement and GA4?
If the AI page substitutes for yours, that visit never loads your domain, so GA4 records no session, your heatmaps capture nothing and your forms do not exist on that path. Meta has not published whether its pixel fires on that page or how it counts the conversion, so the gap between Ads Manager and your analytics can only be closed by reconciling both against real orders.
