Aveani PixelScope · in review
PixelScope · Chrome extension by Aveani

See what your
pixels really send.

Most pixel helpers show what a page asked its pixel to do. PixelScope shows what actually left the browser for Meta and TikTok, including pixels inside Shopify's sandbox, Google Tag Manager and apps.

In review on Chrome Web StoreTry it here
The difference

A pixel can be called and still send nothing.

We opened a real product page on Brooklinen and looked twice: once at what the page's code asked the Meta pixel to do, once at what the browser actually sent.

What the page asked for

Calls to the Meta pixel in the page's code

  1. call 1dataProcessingOptions
  2. call 2init 847463095293947
  3. call 3track PageView
  4. call 4track ViewContent
4calls. A helper that counts these reports events firing.
What reached Meta

Requests the browser sent to facebook.com/tr

  1. —none on this load
0requests. Meta's own counter on the page agreed: eventCount 0. PixelScope said "loaded but sent nothing".

Checked on 15 Nov 2026 in Chrome. The calls were real; the cause on this load was consent and settings, not a broken site.

Inside PixelScope

One glance, then the detail.

The popup reads top to bottom: the verdict, the pixels and what each one tracks, the problems in plain words, then every event with its value.

01 VerdictProblems firstErrors, things to check, or a clean bill, with the count of pixels and events.
02 FunnelWhat each pixel tracksPage, product, cart, checkout, purchase, lit up as they're sent.
03 PixelsEvery ID, one click to copyTwo pixels of the same platform on one page? You'll see both.
04 ProblemsWhy it mattersEach issue says what it breaks, like doubled conversions or ROAS you can't trust.
05 Also on the pageThe rest of the stackGoogle Ads, Analytics, Klaviyo, Pinterest and more, named from request addresses only.
What we found

63 stores, 165 pages, one real browser.

Home page, a product page and add to cart on well-known Shopify and DTC brands. Then we compared what PixelScope showed with each page's own network log.

38

Meta events sent from Shopify's sandboxed pixel, invisible to helpers that only watch the page's code

18

pages where the Meta pixel loaded but sent nothing

12

pages running two pixels of the same platform

0

events PixelScope missed that the page's own log showed

Run on 15 Nov 2026 in Chrome from Norway, so cookie banners were in play.Counts are pages, not stores.
Playground

Break a store. Watch what PixelScope says.

Shop the demo store, then flip the switches below it: decline cookies, install the pixel twice, drop the currency. The popup on the right uses the extension's real rules.

demo-store.com/products/field-jacket

Field Jacket

49.00 EUR
Simulated in your browser with PixelScope's real rules. Nothing is sent anywhere.
PixelScope · live
Privacy

Everything orbits your browser. Nothing leaves it.

  • No servers, no account. PixelScope has no backend to send anything to.
  • Memory only. Events live in the browser's session memory for the open tab and vanish when you close it.
  • Read-only. It never blocks, changes or replays a request.
  • Free stays free. Paid features, if they come, will only ever be new ones.

Stop guessing
what your pixels send.

PixelScope is waiting for Google's review. The install link goes live here the day it's approved.

In reviewRead the docs