A link click is Meta’s count of clicks on your ad that lead to a destination, on or off Meta. A landing page view is a click after which your landing page actually loaded and your Meta Pixel fired. Landing page views are lower because every click that dies before the Pixel loads drops out.
Read side by side, landing page views vs link clicks show how many paid clicks never became a visit Meta could see. Most causes of the gap are fixable, and you don’t need a “normal ratio” to find them.
What Meta counts as a link click
Meta defines link clicks as clicks on your ad that lead to destinations or experiences, on or off Meta-owned properties (Meta Business Help Center). On a standard image ad that points to a website, a tap on the image or on the call-to-action button counts as a link click and as an outbound click. Outbound clicks are the narrower metric: only the clicks that take people off Meta.
Two details matter for the gap. The link click is recorded at the tap, before anything loads. And it includes destinations that aren’t your landing page at all, such as an Instant Experience that opens inside the app.
What Meta counts as a landing page view
Meta’s help center describes a landing page view as a click on the ad followed by a successful load. It’s counted when your Pixel fires a PageView, PixelInitialized or ViewContent event, and reporting it requires a Meta Pixel installed and selected in the campaign (Meta Business Help Center). For landing page view optimization, Meta says the Pixel base code must be on the landing pages people reach from your ads (Meta).
So a landing page view is a Pixel event. Whatever stops or delays the Pixel removes a landing page view, even when the visitor did see your landing page.
| Link clicks | Landing page views | |
|---|---|---|
| Recorded when | someone taps a link in the ad | the destination loads after the click and the Pixel fires |
| Needs the Meta Pixel | no | yes |
| Includes people who leave before the load finishes | yes | no |
| Includes clicks to destinations inside Meta | yes | only if that destination loads and the Pixel fires |
| What it tells you | how much the ad pulls | how many clicks became visits Meta could see |
Why are landing page views lower than link clicks?
Each cause removes landing page views at a different point between the tap and the Pixel, which is why each one needs its own check.
A slow landing page. The visitor taps, waits on a blank screen, and goes back to the feed. Meta counted the click; the Pixel never loaded. You won’t reproduce this from a desktop on office wifi.
The in-app browser. On mobile, the click opens inside the Facebook or Instagram app’s own browser rather than the visitor’s usual one (Krause, 2022). The feed is one tap away, so a landing page that shows nothing for a few seconds gives the visitor time to leave.
A Pixel that loads late. The base code sits at the end of the body, behind a tag manager trigger that waits for the whole window to load, or after a stack of heavier scripts. The visitor reads your headline and leaves before PageView fires.
A consent banner holding the Pixel. Where your consent setup requires opt-in before the Pixel loads, visitors who ignore or decline the banner never produce a landing page view. That part of the gap is the cost of compliance. Measure it, and don’t “fix” it by firing early.
Redirects before the landing page. A click tracker, a shortener, http to https, the bare domain to www: each hop is another round trip before your landing page starts loading, and a hop through another domain can strip the URL parameters. If the last hop lands on a URL without your Pixel, landing page views go to zero.
Low-intent and accidental clicks. Some taps aren’t interest. A thumb catches the ad mid-scroll, the browser opens, the visitor closes it. If these are a big part of your gap, it will look worse in some placements than in others.
A missing or mismatched Pixel. The landing page has no Pixel, or a different one from the Pixel selected in the ad set, so landing page views drop toward zero while link clicks look normal. Ad blockers that stop the Pixel script take a steadier share on top.
Clicks that went somewhere else first. If the ad opens an Instant Experience before your website, link clicks count the opens, and only some visitors continue. For those formats, compare outbound clicks with landing page views instead.
How to diagnose the landing page views vs link clicks gap
Start with the breakdowns in Ads Manager: placement, platform, device. If one slice sits far below the others while sending people to the same landing page, look at the clicks from that slice. If every slice is low, look at the landing page and the Pixel.
| Cause | What you see | How to check | Fix |
|---|---|---|---|
| Slow landing page | Gap on every placement, wider on mobile | Mobile LCP, measured on a phone from the app | Cut redirects, scripts and hero image weight |
| In-app browser | Gap wider on Facebook and Instagram mobile than elsewhere | Breakdown by platform and device; tap through from the apps | Same as a slow landing page; simplify the first screen |
| Pixel loads late | The landing page appears, PageView fires seconds later | Network timing in the browser; Test events in Events Manager | Base code in the <head>, no delayed trigger |
| Consent gate | Gap follows the banner’s decline rate | Compare landing page views with consent accepts | Nothing that breaks consent; keep the banner off the headline and form |
| Redirects | fbclid or other parameters missing on arrival; slow first response | Follow the ad URL and count the hops | Link straight to the final URL on the domain that serves the landing page |
| Low-intent clicks | Gap concentrated in one placement | Breakdown by placement | Exclude the placement, or optimize for leads |
| Missing or wrong Pixel | Landing page views near zero | Events Manager: PageView arriving from that domain, from the Pixel selected in the ad set | Install or select the right Pixel |
| Clicks to Meta destinations | Link clicks well above outbound clicks | Compare the two columns | Read outbound clicks for these formats |
The third number: clicks that reached your server
Meta counts link clicks at the tap. The Pixel counts landing page views in the browser. Between the two sits a number most setups never look at: the requests that actually reached the server hosting your landing page.
- If server arrivals are close to link clicks but landing page views are far lower, people arrived and the Pixel didn’t fire for them: speed, Pixel timing, consent, blockers.
- If server arrivals are already far below link clicks, the loss happened before your landing page: a redirect hop, clicks into a destination inside Meta, a broken destination URL.
You can get that number from your server’s access logs, counting requests that carry an fbclid, or from first-party tracking that logs each click on the server. It also gives you a click-to-lead rate that doesn’t depend on the Pixel at all.
DropCPL logs every ad click on the server, in the same response that renders the landing page, so the click is recorded whether or not the Pixel fires. Leads are counted from the forms it receives, and that count is what its CPL is built on. Start free →
How to close the gap
- Remove every redirect between the ad and the landing page, and point the ad at the final URL on the tracking domain that serves it.
- Lighten the first screen. Compress the hero image, drop autoplay video, use system fonts or preload a single one, and defer chat widgets and heatmaps until the form works. The guide to building a landing page for Facebook ads has the full list.
- Load the Pixel base code in the
<head>and fire PageView on load, not on a delayed trigger. - Keep the consent banner off the headline and the form. Stay compliant, and treat the declines as a known, measured cost.
- Prune placements where the gap is structural and leads never follow.
- Re-test on a phone, from the apps, after each change.
Don’t chase the gap to zero. Some people will always tap and leave, and two systems counting different events won’t match exactly (real CPL vs platform CPL makes the same point about leads). Look for a gap that stays stable and looks similar across the ads that share a landing page.
Should you optimize for landing page views or for leads?
Meta’s case for landing page view optimization is that it improves the quality of the traffic your ads bring compared with optimizing for link clicks, and that it’s a good choice if you don’t yet have lower-funnel events set up with your Pixel (Meta). Both points are fair. Neither makes it a lead generation goal.
Meta’s delivery system finds people likely to do whatever you optimize for, so optimizing for landing page views gets you people who load landing pages. In a small 2023 test by Jon Loomer, the ad set optimized for link clicks got 99% of its traffic from Audience Network, the one optimized for landing page views 96%, and the one optimized for a custom “quality visitor” event (two minutes on the post and a 70% scroll) got none from there, with almost all of it coming from the feed (Loomer, 2023). It was a test of about $300 promoting a blog post, so treat it as an illustration. The mechanism behind it is general, though: the traffic you buy follows the event you pick.
| Situation | Optimize for | Why |
|---|---|---|
| The Lead event fires reliably from browser and server | Leads | Meta learns from the result you pay for |
| The Lead event isn’t firing yet | Fix it; landing page views only as a stopgap | Optimizing for visits teaches Meta to find visitors |
| The landing page is content (an article, a pre-sell) and the visit is the goal | Landing page views | The visit is the conversion |
| Too few leads per ad set for Meta to learn from | Consolidate ad sets first, then decide | Optimizing higher in the funnel trades intent for volume |
| You want a cheap pool of visitors to retarget | Landing page views | An ad set optimized for leads qualifies them later |
For lead gen, get the Lead event right from both the browser and the server (Pixel and CAPI deduplication) and optimize for it. Keep the gap between link clicks and landing page views as a health check on the landing page, and judge the leads themselves on cost per qualified lead.