Checklist

Meta shows clicks, Shopify shows few visits: is the cookie banner one reason?

Meta link clicks far above landing page views? We tested 3 Shopify stores with no click, Reject and Accept to see when the Meta PageView fires.

In brief

Meta counts a landing page view only when it sees the page load after an ad click, through its in-app browser or the Meta Pixel. A cookie banner can decide whether the pixel runs at all. We opened three Shopify stores from a US connection on November 3, 2026, with a test fbclid in the URL, three times each: no click, Reject, and Accept. On Store AD, which waits for consent, Meta sent no PageView unless the visitor clicked Accept, and then it came 4.9 seconds after the click. On Store AE, set up as opt-out, Meta sent a PageView 4.3 seconds after the page opened with no click. On Store AC, the Meta script loaded after Accept but sent no PageView in two tries. Shopify's own analytics request went out before the banner appeared on all nine visits. This test cannot tell you why a given store loses landing page views. Not legal advice.

A link click is counted by Meta when someone taps a link in the ad. Not every link in an ad leads to your site.

A landing page view is counted by Meta when the destination page loads after the click. Meta says it sees that load through its in-app browser or through the Meta Pixel on the page, and that some landing page views may be estimated with modeling when data is missing.

A Shopify session is counted by Shopify from its own analytics on the storefront. Shopify changed how it measures sessions between September 21 and 23, 2026. Sessions now follow continued activity instead of ending at midnight UTC, some sessions without a page view now count, and known bots are filtered by default. If your comparison crosses those dates, part of any change in sessions can come from the new method.

The three numbers come from different systems, so they will never match one to one.

What one merchant reported

On November 2, 2026, a merchant posted on X that 40 link clicks were producing 1 or 2 landing page views. On one ad, 200 outbound clicks showed 2 Shopify sessions and 1 landing page view. He wrote that about 90% of clicks used to become landing page views, and that the gap showed up across several stores. He had already checked his cookie banner settings, consent behavior, theme, redirects, the Facebook iPhone app, and slow 4G, and said the cause was still not clear.

We did not test his stores. We tested whether a banner, by itself, can move the first Meta PageView late or remove it.

How we tested three Shopify stores

All three stores are public Shopify stores running the Meta Pixel. We used desktop Chrome from a US connection, a new browser profile for each visit, and Global Privacy Control off. Each visit landed on the home page with utm_source=facebook and a test fbclid, like a click from a Meta ad.

  • Store AC uses Shopify's own cookie banner, with Accept and Decline on the first screen.
  • Store AD uses a consent app that holds the Meta Pixel until the visitor chooses. Accept and Decline are on the first screen.
  • Store AE is set up as opt-out for US visitors. The first screen shows Accept and "Your Privacy Choices". To opt out we opened Your Privacy Choices, switched off the one sharing toggle, and clicked Save.

For each store we did three visits. On the no-click visit we waited 60 seconds. On the Reject and Accept visits we waited for the banner, clicked one second later, and stayed 35 seconds. A promo pop-up covered one banner, so we clicked every banner button with a DOM click() instead of the mouse. All times below are seconds from the start of page navigation.

When did the first Meta PageView fire?

Swipe to see more

Store and visitPage loadedBanner shownClickFirst Meta PageView
AC, no click1.30.9nonenone in 60 s
AC, Decline1.30.92.3none in 35 s after Decline
AC, Accept1.40.92.4none in 35 s after Accept
AD, no click2.81.7nonenone in 60 s
AD, Decline2.61.63.1none in 35 s after Decline
AD, Accept2.51.53.08.0
AE, no click4.63.5none4.3
AE, opt-out4.53.0Save at 6.93.6, before Save
AE, Accept1.71.22.44.3

"Page loaded" is the browser's load event. Store AD's PageView came 4.9 seconds after Accept, or 8.0 seconds after the page opened. On a store set up like AD, a visitor who ignores the banner sends no PageView, so Meta gets no pixel signal for that visit. On Store AE the PageView did not wait for a choice. In the opt-out visit, Meta had sent it 3.3 seconds before we clicked Save.

Store AC is the odd one. After Accept, Meta's script loaded 0.2 seconds later, but no request reached Meta's event endpoint in 35 seconds. We repeated Accept and opened a product page, with the same result. The banner was not what stopped it, because consent had been given. On our desktop visits, no request reached Meta's event endpoint after Accept. We can't tell from outside why; that matches the "pixel not firing" item below, which an owner would check in Events Manager.

For what Meta sends after Reject on other stores, see our Meta Pixel after Reject test. For what loads before a choice, see Meta Pixel and CAPI before Accept.

When did Shopify record the visit?

On all nine visits, the browser sent Shopify's own analytics requests before the banner appeared. The first one went out between 0.4 and 2.2 seconds after the page opened, including on the visits where we later rejected. It carried a page_viewed event.

On Stores AC and AD, Shopify's analytics and marketing cookies were not set until Accept. On Store AE, which starts opted in, the Shopify analytics cookie was set on every visit.

We can see the request leave the browser. We cannot see whether Shopify's reports counted it as a session. On these three setups, though, Shopify's first request did not wait for the banner, while Meta's PageView did on Store AD.

Did the fbclid survive the landing?

Yes, on all three stores. Store AD redirected the bare domain to www with a 301, and the final URL kept both the fbclid and the UTM tags. Stores AC and AE answered with no redirect.

Where Meta's PageView fired (AD after Accept, AE on every visit), the browser wrote the _fbc cookie and the PageView request carried an fbc field. On Store AD, _fbc appeared 7.8 seconds after the page opened, so a visitor who left before then left no _fbc behind. Store AC never wrote _fbc. Our BFCM Reject test covers which other services received a test fbclid after Reject.

Other causes to check before the banner

The banner is one item on a longer list. These come from Meta's help pages and the top guides on this question, and we did not test them:

  • Slow pages. People leave before the pixel loads. Compare your page load time with the PageView times above.
  • Redirects and short links. A redirect that drops the query string loses the fbclid. Open your ad URL and check the final address.
  • In-app browsers. Facebook and Instagram open links in their own browser, which behaves differently from desktop Chrome.
  • Accidental taps. Reels and Stories placements get mistaken taps, and one person can click twice.
  • Bots and invalid clicks, including traffic from outside your target countries.
  • Pixel set up wrong. Missing, installed twice, or a custom pixel not connected. Store AC above loaded the script and sent nothing; from outside we can't tell whether setup is the reason.
  • Several destinations in one ad, or an Instant Experience. Compare landing page views with outbound clicks, not link clicks.
  • Ad blockers and browser tracking protection in Safari and Firefox.
  • Shopify's session change on September 21 to 23, 2026, if your comparison spans it.

How to check your own store

  1. Open your ad's destination URL with a test fbclid in a private window and do not touch the banner.
  2. In the browser's network tab, filter for facebook.com/tr and note whether a PageView appears and how many seconds it takes.
  3. Repeat with Reject, then with Accept.
  4. Check that the final URL still has the fbclid after any redirect.
  5. If PageView only fires after Accept, the share of visitors who never answer the banner is a share Meta's pixel never sees. Compare that with your gap.
  6. If PageView never fires, even after Accept, fix the pixel before you look at anything else.

Whether a store should load the pixel before a choice is a legal question for your counsel. Not legal advice. If you send events server side, our Meta CAPI after Reject All page shows what that path sent on stores we tested.

Limits of this test

  • This capture cannot find the root cause for the merchant above, or for any store we did not test.
  • In his report, Shopify sessions were low as well as landing page views. One possibility is that both tools lost the same visits, for example if people left before the page loaded or the clicks were not from people. On our three stores Shopify's first request went out before the banner, so a banner alone would not explain a low Shopify count on setups like these. We cannot confirm that for his stores.
  • Desktop Chrome only, from the US, one visit per store and state. We did not test Facebook's or Instagram's in-app browser, phones, Safari, or EU visits.
  • We see requests leave the browser. We cannot see Meta's landing page view count, which may be modeled, or Shopify's session count.
  • Three stores is a small sample. Other consent tools and settings will behave differently.

For the wider picture of what still loads after Reject on Shopify, see the Reject All hub. Not legal advice.

FAQ

Can a cookie banner lower Meta landing page views?

Yes, if the banner holds the Meta Pixel until the visitor accepts. On the store we tested with that setup, visitors who ignored or declined the banner sent no PageView to Meta. Meta can still count some views through its in-app browser or estimate them, so the drop may be smaller than the share of people who decline.

Does Decline stop Shopify from recording the visit?

Not the first request. On all three stores, Shopify's own analytics request left the browser before the banner appeared, on Decline visits too. We could not see whether Shopify's reports counted those visits as sessions.

Why is Meta's PageView several seconds late on some stores?

The pixel script loads after the page, and on opt-in setups it also waits for the click on Accept. On one store the PageView came 4.9 seconds after Accept. Visitors who leave sooner are not counted by the pixel.

Is a link clicks to landing page views ratio of 10 to 1 normal?

We have no benchmark to give. Compare landing page views with outbound clicks, check the pixel on your landing URL, and rule out the other causes in this guide before you blame the banner.

Does the fbclid survive a www redirect?

On the store we tested with a redirect from the bare domain to www, yes. Some redirects and link shorteners drop the query string, so open your own ad URL and check the final address.

Did Shopify's September 2026 change affect sessions?

Shopify changed how sessions are measured between September 21 and 23, 2026. Comparisons that span those dates can show a change that comes from the new method, not from your store.

Sources

These links cover the platform and regulatory context used in this guide. Applicability still depends on the organization and jurisdiction.

Low Landing Page Views? Test the Banner First | ConsentProbe