How to Check If Your Tracking Pixels Are Working

How do you check if a tracking pixel is working?

Open the page, do what the pixel should record, and confirm the request reached the platform: in its own test tool, such as Meta’s Test events, TikTok’s Test Events or Google’s Tag Assistant, or in Chrome’s Network panel. A pixel works when that request leaves the browser, succeeds, and carries the right ID, event and values.

Every vendor page cited below was checked on 25 September 2026.

What counts as “working”?

Four separate things: it loaded, it fired, it reached the platform, and it was correct. Each fails in its own way, and finding the pixel on the page proves only the first.

A success response still isn’t a counted conversion. It means the platform’s server answered; whether the event is accepted, matched and credited to an ad is decided later, and the platform’s own report is the record. Purchases sent from a server, such as through Meta’s Conversions API, never pass through the browser, so no browser tool can list them.

How do you check with each platform’s own tool?

Start here: each platform’s free tool knows its own events, and most show what the platform itself received.

Meta. Meta renamed its extension, and an installed copy updates itself to Data Advisor (Meta: Ads Data Advisor). Its instruction before testing: “Deactivate your ad blocker for the website you are on.” Server events need a test code (Meta: Conversions API); the browser steps are in is the purchase reaching Meta at all.

TikTok and Google. Sources: TikTok Pixel Helper 2.0 (last updated February 2025), TikTok’s Events Manager tools, Tag Assistant, Preview and DebugView. Google’s own check reads Tag Assistant’s Summary tab: events there mean the Google tag is set up correctly; none means it may not be connected to its destination; no tag at all points to your site’s code or measurement ID (Google: verify your Google tag).

OpenAI, Pinterest and Shopify. Sources: OpenAI’s measurement pixel and conversion setup pages, Pinterest Tag Helper, and Shopify’s pages on testing a pixel and testing an app’s pixel. Shopify’s Pixel Helper doesn’t work on headless stores or stores in private mode.

If you run one or two platforms, their own tools are enough.

How do you check in Chrome’s Network panel?

The Network panel lists each request the page sends, to any platform, with its status and payload, and answers “did it fire?” and “was it stopped?” without installing anything (Chrome: Network reference).

1. Open the page, open Chrome DevTools and choose the Network panel.
2. Tick Preserve log, so requests stay listed when the page changes.
3. Reload the page.
4. Type the platform’s address in the Filter box, for example facebook.com/tr.
5. Do what the pixel should record: add a product to the cart, send the form, place a test order. A new request should appear.
6. Click the request. Payload shows its query string parameters and form data. The Status column shows the response code, such as 200, or “(failed)” followed by the error.
7. To see what was stopped, choose More filters → Blocked requests; Chrome highlights blocked requests in red. The Initiator column shows what sent each request.

With server-side tagging, GA4 hits can go to the site’s own subdomain, such as sst.example.com/g/collect. On two sites we checked on 25 September 2026, they went there and to www.google-analytics.com, so filter for /g/collect to catch both.

How do you check many pixels at once?

With a helper that lists several platforms’ requests side by side. It helps most on sites carrying five or six vendors’ tags, and on sites you don’t manage, where the platforms’ test tools aren’t open to you.

All Pixel Helper, which we build, is a free Chrome extension that lists and decodes the requests a tab sends to 40 ad and analytics platforms, with one card per platform account, so two Meta pixels show as two cards. Each request is marked delivered, failed or blocked as Chrome reports it, and a pixel that’s installed but hasn’t sent anything shows “No events fired yet — pixel installed only.” It sees only this tab’s browser requests, never anything sent from a server; delivered means the browser got a response, not that the platform recorded the event; and hits sent to first-party or server-side Tag Manager domains, like the sst. subdomain above, aren’t matched.

1. Open the page and click the extension’s icon in Chrome’s toolbar. The Pixels tab lists the cards, each with its account ID.
2. Turn on Preserve log on the Pixels tab, then do the action you’re testing.
3. Click an event. Chrome’s side panel opens on its Diagnostics, decoded Parameters and Request, with its outcome.

Treat what it flags as a prompt to look closer in each platform’s own tool, not as a verdict: it complements those tools.

How do you see which pixels another site uses?

Load it in Chrome with the Network panel or a helper open and watch what fires as you browse. What fires depends on the page, the banner and where the visitor is.

• Page source finds only hard-coded tags. Searching it for fbq( or gtag( misses tags that Tag Manager or an app loads; those appear only when they run.
• Consent changes the list. Decline the banner first, note what fires, then accept and compare.
• Actions change the list. Purchase and lead events fire only on those steps, so a check of the home page shows page views at most.
• Pixel IDs are in the requests, such as the id on Meta’s; a helper’s per-account cards list each platform’s ID.

How do you check pixels on a Shopify store?

Start with Shopify’s Pixel Helper, then confirm the event in the platform’s own tool. The steps are in test a pixel with Shopify’s Pixel Helper.

• Where Shopify’s pixels run. They load on the storefront, checkout, Thank you and Order status pages (Shopify: pixels). App pixels run in a strict sandbox built on web workers; custom pixels run in a lax sandbox, an iframe that can’t reach the main page (shopify.dev: web pixels).
• Consent. If Pixel Helper shows Pixel is awaiting consent, accept your banner or click Give consent to continue test (Shopify: app pixels).
• Old snippets. Tags pasted into Additional scripts no longer run on the Thank you page: see the 26 August Thank-you-page change.
• Server-sent purchases. What the Facebook & Instagram app or a tracking app sends from a server never appears in a browser tool; check the platform’s report.
• What an extension sees. Custom pixels’ requests show in a browser extension; app pixels’ may not, because they come from web workers rather than the page. For app pixels, rely on Shopify’s Pixel Helper and the platform’s own tool.

Why does a pixel look fine but the platform shows nothing?

Because the browser shows what was sent, not what the platform did with it. Match the symptom to its guide.

How do you record what you found?

Note the date, browser, page address and consent choice, then export the requests, so anyone can repeat the test and compare.

• From Chrome. Right-click a request in the Network panel and choose Copy → Save all as HAR (sanitized). The sanitized file leaves out Cookie, Set-Cookie and Authorization headers (Chrome: Network reference).
• From All Pixel Helper. On the Pixels tab, open Export events and choose Export as CSV for a spreadsheet with one row per event, or Export as JSON for the full decoded events. Exports ignore any filter or search you set.

Either file contains whatever the page sent, including any email address or phone number a tag sent in clear text. Share it the way you would share customer data.

Frequently asked questions

What are monorail and trekkie requests on a Shopify store?

Shopify’s own analytics, sent to Shopify. All Pixel Helper’s Shopify card decodes those requests into events such as page_viewed and checkout_completed, but they are Shopify’s record of the visit, not proof that Meta, TikTok or Google received anything.

Can I check a pixel on my phone?

Partly. TikTok’s Test Events offers a test environment that mimics how your site shows up in the TikTok app, reached with a QR code or in the browser. All Pixel Helper runs in Chrome on a computer, not on a phone.

Does a pixel helper change the page?

Watching requests can’t change them. All Pixel Helper does touch the page in one way: it creates an empty dataLayer on every page that lacks one and wraps dataLayer.push, so it can show pushes. A page script that checks whether dataLayer exists will find one. The extension itself sends nothing anywhere.