Free tool · No extension needed
Meta Pixel Checker
Check if any website has a Facebook pixel. See its pixel IDs, the events in its code, and pixels hidden in Google Tag Manager or Shopify.

- 1Paste any website or page URL
- 2Press Check
- 3Get pixel IDs, events and other tags
What is the Meta Pixel?
The Meta Pixel (still often called the Facebook pixel) is a snippet of JavaScript a website adds so Meta can see what visitors do after they click an ad. It loads Meta's library from connect.facebook.net, starts with fbq('init', 'pixel ID') and sends events such as PageView, AddToCart and Purchase.
Those events are how Meta reports conversions, optimizes delivery toward people likely to buy and builds retargeting audiences. A missing or broken pixel means ads optimize blind. Meta's pixel documentation covers the full setup.
How this checker works, and its limits
We load the page the way a browser's first request would, without running it. Then we read the HTML for the pixel code and the noscript image fallback, open the site's published Google Tag Manager container, read Shopify's web pixels config, and scan up to five of the site's own scripts.
That catches most installs. It can't see what only exists once the page runs:
- Events fired by clicks, add to cart or checkout steps (we show the ones written into the code, not whether they fired).
- Pixel IDs read from a variable or the dataLayer at runtime.
- Tags that wait for a cookie consent banner, server side tag managers and Shopify custom pixels.
- Conversions API events, which go from the server to Meta and never touch the page.
For those, use Meta's own tools below. They're the definitive check, because they watch the pixel while the page runs.
How to check a pixel with Meta Pixel Helper or Events Manager
Meta Pixel Helper (now called Meta Ads Data Advisor). Meta's free Chrome extension, per Meta's Pixel Helper docs:
- 1Install Meta Ads Data Advisor from the Chrome Web Store and pin it to your toolbar.
- 2Turn off your ad blocker for the site you're checking, then open the page.
- 3Look at the extension icon. A number means Meta Pixel events fired on the page; no badge means no pixel was detected.
- 4Click the icon to see each pixel found and whether it loaded.
- 5Do the action you want to test, like adding an item to the cart, then select the pixel and confirm the event shows as successful.
Test events in Events Manager. Use this for your own pixel. It also shows Conversions API events. See Meta's guide to testing your events.
- 1Open Events Manager and select your pixel (dataset) under Data sources.
- 2Open the Test events tab.
- 3Under browser events, enter your website URL and open the site from there.
- 4Browse, add to cart or check out. Each event appears in the Test events tab within seconds.
Common Meta Pixel problems and fixes
- No pixel found at all
- The base code isn't on the page, or it's in a GTM tag that never fires. Check the tag's trigger is All Pages and the container is published.
- Two pixel IDs on one site
- Often an old agency pixel left behind, or the same pixel added by both a Shopify app and the theme. Remove the one you don't use, or you'll split or double count events.
- PageView fires twice
- The base code is installed twice, for example in the theme and in GTM. Keep one install.
- Purchase never shows up
- The event is only on the thank you page, which some checkouts host on another domain. Use the platform's integration, or send Purchase through the Conversions API too.
- Pixel only fires after cookie consent
- Expected in regions that need consent. Make sure the consent banner actually releases the tag once a visitor accepts.
- Pixel Helper shows nothing on Shopify
- Shopify's Facebook & Instagram app runs the pixel in a sandbox. Use Test events in Events Manager to confirm it.
Meta Pixel vs Conversions API
The pixel runs in the visitor's browser. Ad blockers, browser privacy features and declined cookie banners can stop it. The Conversions API sends the same events from the website's server straight to Meta, so they don't depend on the browser.
Meta recommends running both, with matching event IDs so it can remove duplicates. Shopify's Facebook & Instagram app and most tag managers can set up the server side for you. Because Conversions API traffic never touches the page, no outside tool (this one included) can detect it.
How to spy on a competitor's tracking stack
A competitor's tags say a lot about how seriously they buy ads. Run their home page and a product page through the checker and look at:
- Which ad platforms they pay for. TikTok, Pinterest, Snap, Reddit or Google Ads tags next to the Meta Pixel show where else they spend.
- How deep their tracking goes. AddToCart, InitiateCheckout and Purchase events mean they optimize for sales, not just traffic.
- Several pixel IDs. Separate pixels per country or brand usually mean separate ad accounts and markets.
- A tag manager or Shopify apps. Tells you which platform and stack they run on.
Then look at the ads themselves. The Competitor Ads Finder shows every active Meta ad a brand runs, longest running first, and Competitor Analysis finds who else is advertising in their niche.
The pixel tells Meta what sells. Skaler tells you why.
Questions, answered.
Paste the site's address into the Meta Pixel Checker above and press Check. It reads the page, its Google Tag Manager container and a few of its scripts, then lists every Meta Pixel ID it finds and the events written into the code. For a full check of events fired by clicks and purchases, open the site with Meta's Chrome extension (Meta Pixel Helper, now called Meta Ads Data Advisor) or use Test events in Events Manager.
No. Meta Pixel Helper is a Chrome extension that watches the pixel while the page runs in your browser, so it also sees events fired on clicks and checkouts. This checker reads the page code from our server, so it works on any device without installing anything, and it also finds pixels that sit inside Google Tag Manager or Shopify's apps.
Some pixels only exist once the page runs: IDs set from a variable, tags that wait for cookie consent, server side tag managers or custom pixels in Shopify's Customer events. A static check can't see those. The result notes tell you when that is likely, for example when the site uses a consent banner or a GTM container.
No tool can, from outside. Conversions API events go from the website's server straight to Meta, so they never show up in the page. Only the pixel owner can see them, in Events Manager.
Yes. Shopify's Facebook & Instagram app installs the pixel through Shopify's web pixels sandbox, which Meta Pixel Helper often doesn't show. The checker reads the store's web pixels config and reports the pixel ID from there.
Every fbq track and trackCustom call written into the page, its scripts or the GTM container, such as PageView, ViewContent, AddToCart or Purchase. Events in the page code usually fire on load. Events in GTM or script files fire on their own triggers, like a click or a checkout step.
Yes. A pixel ID is public by design: it has to be in the page so browsers can send events. The ID alone gives nobody access to the owner's data or audiences. If you see events from sites you don't own in Events Manager, Meta lets you limit which domains can send data to your pixel.
Yes. Under Also found it lists the TikTok Pixel, Google Analytics 4, Google Ads, Google Tag Manager, Pinterest, Snap, LinkedIn Insight, X, Reddit and Microsoft Ads tags it can see, with their IDs when they're readable.
Yes. There's a daily limit per visitor to keep it fast, but no account, no login and no extension.
Some sites answer automated visits with a bot check or an error page, so there's no page code to read. Check those sites with Meta's Chrome extension instead, which runs in your own browser.

Your pixel is live. Now find the ads that win.
Skaler shows which Meta ads are winning and why: hooks, angles, formats, ROAS. Plus competitor ad intel and bulk launching.
Start free