檢查 63 間網店的廣告像素:它們實際送出了甚麼
I checked the ad pixels on 63 online stores. Here is what they really send
作者用自建 Chrome 擴充功能檢查 63 間網店的 165 個頁面,指出只看頁面內 JavaScript 呼叫,未必能確認像素事件是否真正送出。測試中,一款常見工具在 71 個頁面顯示了 52 個未離開瀏覽器的事件;這 165 個頁面中另有 38 個 Meta 事件來自 Shopify 像素沙盒。
If you run ads for an online store, the numbers in Meta or TikTok Ads Manager depend on one thing: the events the store's pixel sends from the browser. When those are wrong, everything downstream is wrong too. Purchases get counted twice, revenue goes missing, and campaigns optimize on bad data.
So I built a small Chrome extension that reads the pixel requests a page really sends, and I ran it across 165 pages of 63 real stores (mostly Shopify). Here is what came out of it.
Why "really sends" matters
Most pixel helper extensions watch the pixel's JavaScript calls inside the page, for example fbq('track', 'Purchase'). That tells you what the site tried to send. It does not tell you what left the browser. Cookie banners block calls, settings drop them, and some pixels don't run in the main page at all.
Reading the network requests instead (facebook.com/tr, analytics.tiktok.com/api/v2/pixel, google-analytics.com/g/collect, googleadservices.com/pagead/conversion) shows exactly what the platform received.
In my test the difference was not academic. A popular helper that watches page calls showed 52 events across 71 pages that never left the browser. If you trust that view, you think tracking works when it doesn't.
Shopify's sandbox hides pixels from page-based tools
Since Shopify moved pixels into Customer events (web pixels), the pixel code runs inside a sandboxed iframe, not in the store's page. Tools that look at the page simply don't see it.
Across the 165 pages, 38 Meta events came from these sandboxes. On one store a page-based helper reported no Meta pixel at all, while two pixels were firing from the sandbox. If you've ever been told "pixel not found" on a store that clearly tracks sales, this is probably why.
The problems that showed up most
These are the issues worth checking on your own store:
- The same event sent twice with different event IDs. The platform can't merge them, so the event is doubled in reports. Common cause: the pixel is installed twice, once in the theme and once through an app.
- Purchases without value or currency. The ad platform can't report ROAS or optimize for revenue.
- Missing event ID (Meta, TikTok) or transaction ID (GA4, Google Ads). If the store also sends server-side events, the browser and server copies can't be deduplicated.
- AddToCart or ViewContent with value 0. Free gifts and broken prices skew the numbers.
- Pixel loads but sends nothing. Usually it is waiting for cookie consent.
- An order confirmation page with no purchase event. The platform never sees that sale.
How to check your own store in a minute
- Open a product page and add something to the cart.
- Make a test order and stay on the thank you page.
- Look at which events went out, with which IDs and values.
You can do this in DevTools on the Network tab by filtering for tr?, pixel and collect, and decoding the payloads by hand. Or you can use the extension I built for exactly this: PixelScope. It shows Meta, TikTok, GA4 and Google Ads events from the network, flags the problems above in plain words, and keeps everything in your browser. It's free and needs no login.
https://chromewebstore.google.com/detail/pixelscope-ad-pixel-check/cfkpcmdhimaabbilofjcnpedbkmojipo
If you try it on your store and something looks off, post it in the comments and I'll help read it.
Disclosure: I'm the developer of PixelScope. I used an AI assistant to help with the code and with editing this post; the test data is from real runs.
來源:DEV Community · dev.to