Free · No sign-in · No extension
Free Meta Pixel checker: every event your site sends, page by page
Enter your website. A browser opens your pages like a shopper and lists every Meta pixel it sees, the events each one sends, and anything fired twice or before a cookie choice.
- Pixel 1234…Home, Category, Product, Cart. PageView sent twice on every page.
- Pixel 5678…Checkout only. Loaded by an app.
What it shows
Every pixel on your site
Each pixel ID and the pages it loads on. Several pixels is common (apps, agencies), so the check shows which pages each one covers.
Events sent twice
PageView or other events sent twice to the same pixel on one page load, which Meta counts twice unless both copies share an event ID.
Where each pixel comes from
Pasted into the theme, loaded by Tag Manager, or added by an app.
What happens with consent
Whether the pixel fires before a choice, and whether it stops after a visitor rejects.
Personal data in requests
Email addresses or phone numbers sent to tags, reported by field name only.
Every other tag too
Google, TikTok, Pinterest, Snapchat, Microsoft, LinkedIn, Reddit and more, in the same report.
Pixel Helper or a full check?
Meta's Pixel Helper extension (now called Meta Ads Data Advisor) shows what fires on the page you're on, while you click around. This check walks the purchase path for you in one go.
| Pixel Helper extension | Swishiy Meta Pixel checker | |
|---|---|---|
| Pages | The one you're on | Home to checkout, in one run |
| Cookie choices | Whatever you clicked | Before a choice, after accepting, after rejecting |
| Other tags | Meta only | Every ad and analytics tag |
| Duplicates and consent | You spot them yourself | Flagged, with the evidence |
| Install | Chrome extension | Nothing |
Pages
- Pixel Helper extension
- The one you're on
- Swishiy Meta Pixel checker
- Home to checkout, in one run
Cookie choices
- Pixel Helper extension
- Whatever you clicked
- Swishiy Meta Pixel checker
- Before a choice, after accepting, after rejecting
Other tags
- Pixel Helper extension
- Meta only
- Swishiy Meta Pixel checker
- Every ad and analytics tag
Duplicates and consent
- Pixel Helper extension
- You spot them yourself
- Swishiy Meta Pixel checker
- Flagged, with the evidence
Install
- Pixel Helper extension
- Chrome extension
- Swishiy Meta Pixel checker
- Nothing
How we visit your site
A real browser opens your home page, a category, a product, the cart and the checkout. On a lead site it opens a service page and the contact page instead. It never submits a form or places an order.
When a cookie banner shows, it visits three times: before a choice, after accepting and after rejecting. It makes each choice through your consent tool's own settings where it can, otherwise by its buttons, and reports on a choice only when it can see it took effect.
Some sites turn automated browsers away. When that happens, the report says so and checks what it can from your home page's code.
What it can't see
- Meta's Conversions API. It runs on your server, not in the browser. The free Tag Manager audit reads your server container's Conversions API tags and checks their event IDs against the Pixel.
- The purchase on the thank-you page. We never place an order. Check purchases in Events Manager's Test Events after a real order.
- Event Match Quality and Meta's own reporting.
What you get
Your grade and the top three findings straight away. Add your email for every finding, the tags seen in each consent state, and a PDF, Excel and CSV. The report and its link are kept for 90 days, and you can delete them sooner.
Common questions
How do I check if my Meta Pixel is working?
Enter your website above. You'll see each pixel the site loads, the events it sends on each page, and anything fired twice or before a cookie choice. For purchases, use Events Manager's Test Events after a real order.
Why does my pixel fire PageView twice?
Usually the pixel is installed twice: once by an app (such as Shopify's Facebook and Instagram channel) and once in the theme or in Tag Manager. If both copies share an event ID, Meta keeps one. If they don't, it counts both.
I have more than one pixel. Is that a problem?
Not on its own. Apps and agencies often add their own. The check shows which pages each pixel covers, so you can tell whether one is missing from checkout or doubling up elsewhere.
Does it need access to my Meta account?
No. Nothing to connect and nothing to install.
Can I check a site I don't own?
Yes. The check only sees what any visitor's browser sees, on public pages.
Does it check the Conversions API?
Not from the browser. The Tag Manager audit reads your server container's Conversions API tags and checks their event IDs against the Pixel.
Want the whole picture?
The full Tracking audit adds GA4, Tag Manager and Google Ads, and shows each event across all of them.