Conversions API
Tracking Pixel Limitations in 2026: Privacy Updates and What to Do
Why tracking pixels miss conversions in 2026: ad blockers, browser privacy limits, cookie consent and iOS changes, what it does to your ads and how to fix it.
By PixlBridge Team
Updated 21 min read
On this page
Tracking pixel limitations are a big part of why your Shopify orders and the purchases Meta reports rarely match. A pixel is a small script that runs in the shopper’s browser, so it can only report what that browser allows, and in 2026 ad blockers, cookie limits, consent banners and iPhone privacy features all have a say.
The cost goes beyond untidy reports: Meta’s delivery system learns from the purchases it receives, so every sale the pixel misses is one less example of who buys from you.
This guide covers what limits pixels today, the privacy updates behind those limits, what they do to your Meta ads, and what you can fix with server-side tracking through the Conversions API (CAPI), a working consent setup and a few checks on Shopify. None of it is about getting around people’s privacy choices; the aim is to measure accurately within them.
What is a tracking pixel?
A tracking pixel is a small piece of code on your website that reports what visitors do, such as viewing a product, adding it to the cart or buying, to an ad or analytics platform. The name comes from the invisible 1×1 image early pixels used; today’s pixels, like the Meta Pixel, are mostly JavaScript running in the visitor’s browser.
On Shopify, the Meta Pixel usually comes from the Facebook & Instagram app, and sometimes from code pasted into the theme or a custom pixel. However it’s added, it works in four steps:
- A shopper clicks your ad. Meta adds a click ID,
fbclid, to the link to your store. - The pixel’s script loads from Meta and stores a browser ID in a first-party cookie,
_fbp. When the link carries a click ID, it keeps that too, in_fbc. - As the shopper browses, the pixel sends standard events from the browser to Meta:
PageView,ViewContent,AddToCart,InitiateCheckoutandPurchase. - Meta matches each event to a person where it can, then uses it to report results, optimize ad delivery and build audiences.
Every step depends on the shopper’s browser, and each limitation below breaks one of those steps.
Tracking pixel limitations at a glance
These are the main reasons a pixel misses or distorts conversions:
- Ad blockers stop the pixel’s script or its requests to Meta, so no events are sent.
- Cookie limits in Safari delete the pixel’s cookies early, so returning shoppers look new and lose their link to the ad click.
- Consent choices keep the pixel off for visitors who decline tracking, where your store asks for consent.
- iPhone privacy features and in-app browsers limit how Meta can connect ad clicks to purchases.
- Stripped click IDs: some browsers remove
fbclidfrom links, so the visit can’t be tied to the ad. - Loading gaps: slow pages, closed tabs and payments that never return to the thank-you page mean events never fire.
- A browser-only view: a pixel sees only what happens in a browser on your store.
- Setup errors: duplicate pixels, a wrong pixel ID, old checkout scripts or a paused app pixel lose events or count them twice.
Most of these mean Meta receives fewer events than really happened; duplicates do the opposite. A server-side path for your events helps with blockers and loading gaps, and partly with lost cookies. Consent requirements and Apple’s rules still apply, however an event is sent.
Why pixels miss conversions now
Pixels haven’t gotten worse at their job; the browsers, phones and laws around them have changed. Here is what happens in each case on a Shopify store.
Ad blockers and built-in tracker blocking
Ad blockers and privacy extensions work from lists of known ad and tracking domains, and Meta’s pixel is on the common lists. Some browsers do the same out of the box: Firefox’s Enhanced Tracking Protection and Brave’s Shields limit or block many known trackers by default. Blocking can also happen outside the browser, in VPN and DNS filtering services.
When the script can’t load, or its requests to Meta are stopped, the pixel sends nothing for that visitor: no page views, no add-to-carts, no purchase. The order still shows up in Shopify; Meta just never hears about it from the browser.
Browser tracking prevention and cookie limits
The pixel relies on its cookies to recognize a returning browser and to remember which ad click brought it. Safari’s Intelligent Tracking Prevention (ITP) cuts those cookies short: it deletes cookies created by scripts, like _fbp and _fbc, after seven days without a visit to your site. When a shopper arrives through a link that carries a click ID from a site Safari classifies as a tracker, cookies the landing page sets this way last only 24 hours.
So a shopper who clicks your ad on Monday and buys in Safari ten days later comes back as a new visitor with no click ID. Unless the event carries other details Meta can match, such as a hashed email address, the sale may not be credited to the ad.
Consent banners
Where privacy law requires consent, your cookie banner decides whether marketing pixels run at all. On Shopify, app pixels and custom pixels declare the permissions they need, such as analytics and marketing, and Shopify only loads them for visitors who have given those permissions. A visitor who declines, or never answers the banner, sends no browser events.
That part is working as intended. The problem is a banner that’s wired up wrong: a consent app that doesn’t pass choices to Shopify can keep pixels off after a visitor accepts, or let them run before anyone has.
iPhones: App Tracking Transparency and in-app browsers
On iPhone, Apple’s App Tracking Transparency (ATT) limits how Meta can measure people who tap “Ask App Not to Track” in the Facebook or Instagram app; the privacy updates below explain how.
The in-app browser, on iPhone and Android alike, splits journeys. When someone taps your ad in Facebook or Instagram, your store usually opens inside the app’s own browser, which keeps its own cookies, separate from Safari or Chrome. If they come back later in their usual browser to buy, the pixel sees a different visitor with no click ID; the same happens when someone clicks on their phone and buys on a laptop. And iCloud Private Relay, for iCloud+ subscribers browsing in Safari, hides the shopper’s real IP address, one of the signals used to match events.
Link decoration stripping
Ad platforms “decorate” links with click IDs; Meta’s is fbclid. Some browsers and privacy tools now remove known click IDs before the page loads. Safari’s Link Tracking Protection does it for links opened from Mail and Messages and in Private Browsing, and some privacy-focused browsers and extensions do something similar.
Without fbclid, the pixel can’t create the _fbc cookie, so the visit loses its direct link to the ad click, and nothing later in the chain can put that ID back.
Page speed, loading and checkout gaps
The pixel’s script loads in the background, usually after the page itself. On a slow mobile connection, a shopper who leaves within a few seconds may never trigger a page view. The costlier gaps are at the end of checkout:
- A shopper who closes the tab while the thank-you page loads may never send the
Purchaseevent. - Some payment methods send shoppers to another site to pay. If they don’t come back to the thank-you page, the browser never reports the purchase.
- Some orders never involve a browser on your store at all, such as subscription renewals or orders your team creates for a customer.
Setup errors and platform changes
Not every gap comes from privacy. The usual setup problems:
- The same pixel added twice, for example through the Facebook & Instagram app and in theme code, so events are counted twice.
- A wrong or old pixel ID, so events go to a dataset nobody looks at.
- Old checkout scripts. Shopify has replaced
checkout.liquidand the “Additional scripts” box on the order status page with checkout extensibility and Customer events. Tracking code pasted in those places stops running once a store’s checkout pages are upgraded. - A paused app pixel (see Shopify’s pixel changes below).
- Missing or wrong parameters, such as a purchase sent without its value or currency.
Pixel tracking privacy updates to know in 2026
The rules behind these limits have been building for years. Here they are in general terms; for what applies to your store, check with a privacy adviser.
Apple: App Tracking Transparency and iOS tracking limits
Since iOS 14.5 in 2021, apps have to ask permission before tracking people across other companies’ apps and websites. When someone declines in the Facebook or Instagram app, Meta has to limit how it uses data about what they do on your website. It measures their conversions in an aggregated way (Meta’s Aggregated Event Measurement) and fills some gaps with modeled results, so reports on these shoppers are less detailed and partly estimated.
Meta applies these rules whether the events come from the pixel or the Conversions API, so server-side tracking doesn’t get around ATT.
Privacy laws and consent
In the EEA and the UK, privacy law (the GDPR and the cookie rules that go with it) generally requires opt-in consent before marketing pixels run. In the US, state laws such as California’s mostly work the other way round: tracking can start by default, but people can opt out of the “sale” or “sharing” of their data for targeted ads, and some states expect businesses to honor browser opt-out signals such as Global Privacy Control.
Either way, you decide how consent works on your store, and you stay responsible for it when an app sends data on your behalf.
Consent signals in ad tags
Ad platforms now build consent into their tags. Google asks advertisers who reach people in the EEA to pass consent choices to its tags, such as through its Consent Mode, before it uses their data for ad personalization and remarketing. The Meta Pixel has a consent setting that holds events until consent is granted.
On Shopify, the Customer Privacy API passes each visitor’s choices (analytics, marketing, preferences, sale of data) to pixels and apps. Consent apps should use it, rather than reading or editing Shopify’s cookies.
Third-party cookies: limited in Safari and Firefox, still in Chrome
Safari blocks third-party cookies by default, and Firefox blocks known tracking cookies and keeps other third-party cookies separate for each site. Chrome dropped its plan to remove them: in 2025 Google decided to keep third-party cookies, which people can still block in Chrome’s settings and which Incognito windows block.
For the Meta Pixel, this matters less than it sounds. Its own cookies, _fbp and _fbc, are first-party, set on your store’s domain, and the cookie limits above are what shorten them. What third-party blocking removes is Meta’s own cookie on the pixel’s requests, which is one reason hashed customer details matter more than they used to.
Shopify’s pixel changes
Shopify runs app pixels and custom pixels through Customer events (Settings → Customer events), in a sandbox and under your customer privacy settings. Since January 2026, marketing app pixels default to a data access setting called Optimized. When Shopify judges that a marketing pixel is sharing more data than it needs, based on signals such as referred traffic, sales and synced campaign settings, it can pause some or all of that pixel’s data sharing until relevant activity returns. The alternative is Always on; pixels from analytics apps can’t be optimized and stay Always on.
Each app pixel has an activity log showing when its data access was granted or paused, and whether the change was automatic or manual, for changes from June 3, 2026. Either setting still respects consent: Shopify only loads a pixel when the visitor’s privacy choices allow it.
How Meta Pixel limitations affect your ads
Missing events change what Meta reports, what it learns and who it can reach.
Under-reported conversions and misleading ROAS
Meta can only report the purchases it receives. A simple illustration, not a benchmark: you spend $1,000 and the sales your ads drove are worth $3,000, a 3× ROAS (return on ad spend). If one purchase in five never reaches Meta, Ads Manager may show closer to $2,400, a 2.4× ROAS, and the campaign looks weaker than it is. Meta fills some gaps with modeled conversions, but the less it receives, the more its reports rest on estimates.
Errors run the other way too: a pixel installed twice, or two apps sending the same purchase with different IDs, inflates purchases and ROAS. And not every difference between Meta and Shopify is tracking; attribution windows, view-through credit and sales from other channels play a part. To read ROAS against your margin, see what ROAS is and how to find your break-even ROAS.
Weaker optimization
Meta’s delivery system decides who sees your ads by learning from the people who convert. When purchases go missing, it learns from fewer buyers, and from a skewed sample: mostly shoppers whose browsers let the pixel through. Campaigns that optimize for purchases need a steady flow of purchase events to leave the learning phase, so missing events can slow that down too.
Attribution gaps
Attribution is how Meta decides which ad gets credit for a sale. Every broken link above, from an expired cookie to a stripped click ID or a journey split across browsers, makes that harder: some of those sales are still matched through other details, while others go unattributed or are only modeled.
Smaller retargeting and lookalike audiences
Website custom audiences, such as people who added to cart in the last 14 days, are built from pixel events. When events are blocked or consent is declined, those audiences shrink, and lookalike audiences built from them have less to learn from. Part of that is by design: people who declined tracking shouldn’t be in them.
Server-side tracking: the complement to your pixel
Server-side tracking sends events to the ad platform from a server instead of the shopper’s browser. For Meta, that’s the Conversions API: your store, or an app working for it, sends each event straight to Meta with the order details and hashed customer information attached. Because the browser isn’t in the middle, a blocker or a closed tab doesn’t decide whether the event arrives.
It isn’t a replacement for the pixel, and it doesn’t make every limit go away. Here is what it does and doesn’t fix:
| Limitation | Does server-side tracking help? | Why |
|---|---|---|
| Ad blockers | Yes | The event is sent from a server, not the browser |
| Closed tabs and offsite payments | Yes, for purchases | The purchase comes from the order in your store, not the thank-you page |
| Cookie limits | Partly | An expired cookie stays expired, but purchases can carry the hashed email and phone from the order, which Meta can match |
| Stripped click IDs | Partly | A removed fbclid can’t be restored; other match keys still help |
| Consent requirements | No | Sending from a server doesn’t remove the need for consent where the law requires it |
| iOS App Tracking Transparency | No | Meta applies the same rules to server events |
| Attribution windows | No | Meta’s reporting rules stay the same |
These answers assume purchases come from your store’s order data, as with apps that use Shopify’s order webhooks. Setups that relay events from the browser to a server still need the browser to send them first.
Run both, and make sure Meta counts each action once. Meta treats a browser event and a server event as one when they share the same event name and event_id and arrive within 48 hours of each other. The guide to deduplication in server-side tracking on Shopify shows how that works in practice, and client-side vs server-side tracking compares the two methods in detail. If you’re weighing apps, the roundup of pixel alternative tracking tools compares the main options.
Does server-side tracking get around privacy rules?
No. Sending an event from a server changes how it travels, not whether you’re allowed to send it. Where a visitor’s data needs consent before it’s shared for advertising, that applies to server events too. Decide with your privacy adviser how consent applies to server events in the regions you sell to, just as you did for the pixel.
How to check for pixel problems on Shopify
Before you change campaigns, check the tracking. These six checks cover the common problems:
- List every pixel on your store. In Shopify, open Settings → Customer events and review the app pixels and custom pixels. Then look for a second copy of the Meta Pixel in your theme code or a tag manager. The free Meta Pixel & CAPI checker shows a store’s Pixel ID, how it was added, whether it’s added twice, and its cookie banner.
- Check each app pixel’s data access. In the same place, see whether the pixels you rely on are set to Optimized or Always on, and open a pixel’s activity log to see whether Shopify paused it. If a pixel you depend on was paused, decide whether Always on fits your data-sharing choices; consent applies either way.
- Test the consent path. Open your store in a private window, accept the cookie banner and browse; then repeat and decline. Where consent is required, events should only arrive after you accept. For a custom pixel, Shopify’s own Pixel Helper (open the pixel in Customer events and click Test) shows each event as it fires, or “Pixel is awaiting consent”. Meta’s Pixel Helper extension often can’t see pixels in Shopify’s sandbox, so an empty result there doesn’t prove a problem.
- Watch events arrive in Meta Events Manager. Open your dataset, go to Test events, and walk through the store: view a product, add it to the cart, start checkout and, if you can, place a real test order. Check that each event arrives with the right details, such as the value and currency on the purchase.
- Read Diagnostics and the connection method. The Diagnostics tab lists problems Meta has found with your events, such as missing parameters. The Overview shows each event by connection method, browser or server, and how many were deduplicated. If you send server events, check their EMQ (Event Match Quality) as well: Meta’s 0–10 score for how well an event’s customer details match people, explained in the Event Match Quality guide.
- Compare with your Shopify orders. Use the same dates and time zone, and compare Shopify’s orders with the Purchase events Meta received in Events Manager, not with the purchases Ads Manager credits to your ads. The table below shows how to read the result.
| What you see | Likely cause | What to check |
|---|---|---|
| Fewer Purchase events than orders | Browser losses: blockers, declined consent, closed tabs, a paused pixel | Your consent setup, the pixel’s data access, and a server-side source for purchases |
| More Purchase events than orders | The pixel added twice, or two tools sending purchases with different event IDs | Duplicate pixels, and deduplication by event_id |
| The right count with wrong values | Value or currency missing, or taxes and shipping handled differently | The value and currency on purchase events in Test events |
| Events Manager matches Shopify, Ads Manager shows fewer | Attribution, not tracking: not every sale comes from an ad | Your attribution setting and your other sales channels |
With the browser pixel alone, expect some gap even with a perfect setup: declined consent, blockers and closed tabs are part of normal traffic. What you’re looking for is a gap that’s large, sudden or growing.
Privacy-friendly tracking best practices
Good tracking and good privacy aren’t opposites: the right events, sent once, with consent, are easier to trust and to defend.
- Get consent right first. Use a cookie banner that fits the rules where you sell, and make sure it passes choices to Shopify’s customer privacy settings, so your pixels follow them.
- Hash personal data before it leaves. Meta asks for customer details such as email and phone to be normalized (for example, email trimmed and lowercased, phone as digits with the country code) and SHA-256 hashed before they’re sent. Click and browser IDs, IP address and user agent are sent as they are.
- Send only what you need. Standard events with the parameters Meta uses, such as value, currency and product IDs, are enough. Keep sensitive details, such as health information, out of event data and page URLs; Meta’s terms don’t allow sending them.
- Let one tool send each event. Two apps sending the same purchase means duplicates and more data shared than needed, so remove tracking apps you no longer use.
- Say what you do. Your privacy policy should explain that you share data, including hashed customer details, with Meta for ad measurement.
- Test after every change. Run the checks above again after theme changes, checkout updates, new tracking apps or changes to your banner.
How PixlBridge helps Shopify stores
PixlBridge is a Shopify app that sends your store’s events to Meta through the Conversions API, server-side, and reports your Meta ad results next to your Shopify sales. It covers the delivery side of the limits above, with no code and no theme edits.
- Two sources, one event. Shopify’s Web Pixel (customer events) captures storefront activity, and Shopify’s order webhooks add the order and customer details. PixlBridge sends
PageView,ViewContent,Search,AddToCart,InitiateCheckout,AddPaymentInfoandPurchase, and each event type can be switched off per store. - Purchases from your orders. A purchase is built from Shopify’s order data, so it reaches Meta even when a blocked pixel or a closed tab means the browser never reported it. Visits reach Meta within seconds, purchases within about a minute.
- Hashed match keys. Email, phone, name, city, state, zip and country are normalized and SHA-256 hashed before sending, and raw values aren’t stored. The click and browser IDs (
fbc,fbp), IP address and user agent go with them, as Meta expects. - Counted once. Each event gets a deterministic
event_idbuilt from Shopify’s own identifiers, so a browser pixel that uses Shopify’s event IDs isn’t double counted. One overlap to decide: the Facebook & Instagram app at its “Maximum” data-sharing level also sends purchases server-side, with its own IDs. Lower that app’s data sharing or switch off Purchase in PixlBridge; PixlBridge’s store health page flags the overlap. - Delivery you can see. If sending fails for a temporary reason, retries start at one minute and double each time; after five attempts the event is marked failed with Meta’s message.
- Checks built in. Send a test event (a custom test event, never a purchase) from My store → More, or add a test code from Events Manager under My store → Advanced settings → Test & tools. The “Meta Pixel + Conversions API” panel and Recent activity (“Sent to Meta (CAPI)”) show what was sent, and store health shows event counts and the share of purchases carrying each match key.
- Meta’s numbers next to your sales. The Ads overview shows ad spend, purchases, purchase value and ROAS by campaign, ad set and ad, and Home puts your Shopify sales and blended ROAS (store sales against Meta ad spend) beside them.
On privacy, PixlBridge acts as your processor and you decide consent. Its web pixel respects Shopify’s customer privacy settings, so where your store asks for consent, it only runs for visitors who allow analytics and marketing. Purchases built from Shopify’s order webhooks are sent from the server without a consent check, so cover that server-side sending in your privacy policy, and switch off any event type your rules don’t allow. Personal details are only ever sent hashed.
What it can’t do: bring back what privacy choices exclude, change how Meta treats iOS opt-outs, or restore a stripped click ID. It sends events to Meta only, not to Google or TikTok, and better data doesn’t guarantee a higher ROAS or EMQ.
To start, install PixlBridge from the Shopify App Store, connect Facebook & Instagram with Facebook Login for Business, choose your ad account and Meta Pixel, and send a test event. The product page explains how PixlBridge sends Shopify sales to Meta through the Conversions API. Plans start at $29 a month, with a 14-day free trial and no card needed: see plans and pricing.
Summary: what to do about tracking pixel limitations
Tracking pixels still work, but they only see what the shopper’s browser allows. Ad blockers, Safari’s cookie limits, consent choices, iPhone privacy features, stripped click IDs and loading gaps all cut the events Meta receives, which weakens reporting, optimization and audiences.
You can’t remove those limits, and some exist on purpose. You can measure well within them: add server-side events through the Conversions API with matching event_ids, make sure your consent banner passes choices to Shopify, clear out duplicate pixels and old checkout scripts, send hashed and minimal data, and compare Events Manager with your Shopify orders after every change.
Frequently asked questions
What are the main limitations of tracking pixels?
Tracking pixels run in the shopper’s browser, so ad blockers, browser cookie limits, declined consent, iPhone privacy features, stripped click IDs and pages that close before the pixel fires can all stop events from reaching the ad platform. Setup errors, such as a pixel installed twice, can also distort the numbers.
Do tracking pixels still work in 2026?
Yes. Pixels still report browsing and purchases for many shoppers, and Meta recommends running its pixel alongside the Conversions API. They miss more events than they used to, so the pixel works best with a server-side source next to it.
Why does my Meta Pixel miss purchases on Shopify?
The usual causes are ad blockers, Safari’s cookie limits, visitors who decline cookies, shoppers who close the tab or pay on another site and don’t return to the thank-you page, and setup problems such as old checkout scripts or a paused app pixel. Compare your Shopify orders with the Purchase events in Meta Events Manager to see how big the gap is.
Do ad blockers stop the Meta Pixel?
Many do. Ad blockers and privacy-focused browsers block the pixel’s script or its requests to Meta, so the browser sends no events for that visitor. Server events sent through the Conversions API don’t pass through the browser, so blockers don’t stop them.
How did iOS 14.5 change Facebook pixel tracking?
iOS 14.5 introduced App Tracking Transparency, which lets iPhone users tell apps such as Facebook and Instagram not to track them across other companies’ apps and websites. For people who opt out, Meta measures conversions in a more limited, aggregated way and models some results, whether the events come from the pixel or the Conversions API.
Does server-side tracking get around cookie consent?
No. Server-side tracking changes how an event travels, not whether you may send it. Where the law requires consent before data is shared for advertising, that applies to server events too.
Why don’t Meta’s purchases match my Shopify orders?
Part of the gap is tracking: purchases the browser never reported. The rest is attribution: Ads Manager only counts purchases it credits to an ad under your attribution setting, while Shopify counts every order. To check tracking, compare Shopify orders with the Purchase events Meta received in Events Manager for the same dates and time zone.






