Find Duplicate Pixels, Missing Events and Deduplication Gaps Before They Cost You Ad Spend
Enter a website and this free Meta Pixel checker finds every Facebook Pixel ID, the events set up in your page code and Google Tag Manager, duplicate PageViews, advanced matching, the event ID needed for Conversions API deduplication and the product tags Meta reads for catalogs. Each result is marked green, yellow or red with a fix.
Enter a page. For the best result, test your homepage and a product or thank-you page.
The address you enter is sent to our server and to Google PageSpeed Insights, which load the page once. We keep a simple log of the address checked and the result. No personal details are saved unless you ask for the report by email.
Get the full Excel report in your inbox.
I set up Meta Pixel and Conversions API through server-side GTM, with event ID deduplication and Event Match Quality of 8 or higher on key events.
Thirty checks across pixel setup, events, match quality, deduplication and catalog tags.
Every pixel on the page, in your GTM container and in live requests, with where each one was found.
The same pixel installed twice, or two PageViews on one page load, which inflate your numbers.
Standard and custom events, misspelled standard names, and whether a conversion event exists.
Whether Purchase sends value and currency, so Meta can report ROAS.
Customer data passed to the pixel, and browser ID parameters on live requests.
The event ID that lets Meta match a browser event to a Conversions API event and count it once.
Whether the pixel waits for consent, or fired while Google tags reported consent as denied.
The Open Graph product tags Meta reads to build a catalog from your product pages.
Three steps, about a minute, no extension and no Business Manager access.
Paste your homepage, a product page or a thank-you page.
Your page source, your published GTM container and the requests your page sends in a live test by Google.
Every finding is marked good, warning or problem with a plain-English fix and an Excel report.
The Meta Pixel (formerly Facebook Pixel) is the code that tells Meta what visitors do on your website, so it can measure and optimise your ads. A Meta Pixel checker tests whether that code is installed correctly: one pixel, firing once, sending the right events with the right data.
Browser tools such as the Meta Pixel Helper only see what fires in your own browser. This tool also opens your Google Tag Manager container, so it can list pixel events that only fire on a click, a form submit or a purchase, together with the trigger for each.
Most advertisers now send each conversion twice: once from the browser pixel and once from the server through the Conversions API (CAPI). Meta keeps one copy only if both carry the same event ID. Without it, purchases are double counted and your ROAS looks better than it is. This checker shows whether your pixel sends an event ID at all.
No outside tool can. Conversions API events travel from a server to Meta and never pass through the browser. What this tool can do is check the browser side that CAPI depends on: an event ID on pixel events, customer data for matching and a server container. The CAPI tab then lists the exact steps to confirm it inside Meta Events Manager.
Events that fire only after a real purchase or form submission are read from your code and GTM container, not triggered. If your pixel is loaded by an app or script the tool cannot read, or waits for consent, it may show “not found” even though it exists. Use Test Events in Events Manager for the final confirmation.
The standards this tool measures against.
| Check | Good | Needs fixing |
|---|---|---|
| Installation | One pixel, one place | Hardcoded and in GTM together |
| PageView | One per page load | Two or more |
| Event names | Exact standard names | “purchase” instead of “Purchase” |
| Purchase | Value and currency sent | No value |
| Advanced matching | Hashed email or phone passed | No customer data |
| Event ID | Sent with every event | Missing |
| Conversions API | Browser and Server both shown in Events Manager | Browser only |
| Consent | Pixel waits for marketing consent where required | Fires before any choice |
Check your pixel before scaling Meta ads.
Find out why results in Ads Manager do not match the store.
Audit a new client’s pixel in a minute.
Confirm events and event IDs after a release.
33 free tools for tracking, analytics, advertising and SEO. No login needed.
Test consent defaults, your banner and the consent signals sent with each hit.
Open the Consent Mode checker →Find out if a site uses server-side GTM, a first-party loader and Conversions API.
Open the server-side checker →Estimate how many conversions ad blockers, browsers and consent hide from your reports.
Open the calculator →See every GTM tag, trigger and variable, plus GA4 events, parameters and Consent Mode.
Open the tracking audit →Hear from our clients. Loved by 600+ businesses worldwide.
“I had an excellent experience working with MD on my Google Ads account. Everything was set up perfectly and worked smoothly without any issues or troubleshooting needed. His expertise and attention to detail made the whole process effortless.”
“I worked with Niamul on multiple Google Analytics projects and was impressed by his expertise and precision. He has a strong grasp of tracking, reporting, and optimization, always ensuring accurate insights. He is proactive, reliable, and easy to collaborate with.”
“MD Niamul is extremely skilled. He fixed my Shopify, Google Analytics, and Google Ads conversion tracking perfectly. Everything works exactly as it should now, and he even added an extra data layer, which was very helpful. Outstanding service, fast delivery, and highly recommended.”
“Reliable, knowledgeable, and truly trustworthy. I’ve been working with Niamul for over a year, and he consistently delivers exceptional results across all analytics tasks. His expertise, communication, and commitment make him my go-to specialist for tracking, measurement, and data accuracy.”
“MD N delivered flawless Meta Pixel, CAPI, and server-side tracking. He understood our goals quickly, explained everything clearly, and ensured full transparency. Communication was smooth, updates were consistent, and the results improved our data accuracy and ad performance.”
Five-star reviews from businesses and agencies in the USA, Canada, UK and Australia.
Read All ReviewsYes. The check, the dashboard and the Excel report are free, with no login.
The extension shows what fires in your own browser on the page you are viewing. This tool needs no extension, also reads your Google Tag Manager container to list events that fire later, and gives you a report to share.
Not directly, and no outside tool can, because CAPI events go from a server to Meta. It checks what CAPI depends on in the browser, such as the event ID for deduplication, and tells you how to confirm in Events Manager.
The pixel may wait for consent, load through an app the tool cannot read, or the site may block automated requests. Try a different page, or check with Test Events in Events Manager.
A unique code sent with each event. When the browser pixel and the Conversions API send the same event ID, Meta counts the event once instead of twice.
Passing hashed customer details such as email or phone with pixel events, so Meta can match more events to people. Manual advanced matching is visible in code. Automatic advanced matching is a switch in Events Manager.
Yes. It reads the published container and lists pixel IDs and events from Custom HTML tags and Meta template tags, with their triggers.
It doubles your page view count and can inflate other events too. It usually means the pixel base code is installed twice, for example by a plugin and by GTM.
Yes. The tool reads only public information that the website sends to every visitor’s browser.
I am MD Niamul, a conversion tracking and web analytics specialist and an official Stape partner. I set up Meta Pixel and Conversions API with proper deduplication and high Event Match Quality, so Meta optimises on real conversions.