Paste any public URL and instantly find out whether your Meta Pixel is installed, which Pixel IDs are initialised, which standard and custom events are tracked, and whether common implementation mistakes are present — all without leaving your browser.
Why this matters
Meta Pixel powers every conversion campaign you run on Facebook and Instagram. If it misfires — wrong ID, duplicate initialisation, missing noscript fallback — your attribution data breaks silently. You'll think you're getting purchases when you're getting nothing, or your audience targeting will build on events that never actually fired. Catching these issues before you spend ad budget is the difference between a campaign that scales and one that bleeds.
What the checker scans for
Pixel ID — the 15-16 digit number passed to fbq('init', ...). The tool extracts every ID it finds in the page's static HTML, so duplicate pixel installations are immediately visible. Duplicates inflate conversion counts and distort cost-per-result figures in Ads Manager.
fbevents.js — the Meta Pixel base script loaded from connect.facebook.net. If the pixel is initialised but fbevents.js is missing from static HTML it usually means a tag manager (GTM, Segment, etc.) is loading it dynamically — the checker flags this so you know to test with the Meta Pixel Helper browser extension too.
<noscript> fallback — the <img> tag inside a noscript block that fires a PageView for users with JavaScript disabled. Meta's own implementation guide requires it. It's almost always missing when the pixel is added manually rather than through a platform plugin.
Event tracking calls — any fbq('track', ...) or fbq('trackCustom', ...) calls baked into the page HTML. Standard events like PageView, Purchase, AddToCart, and Lead are listed separately from custom events so you can see exactly what's hardcoded versus what's triggered dynamically by user actions.
Standard Meta Pixel events
Meta recognises a fixed set of standard events that map directly to campaign objectives and optimisation signals:
PageView— fired automatically by the base pixel; needed for traffic and retargetingViewContent— product or content page viewed; used for dynamic product adsAddToCart— item added to a shopping cart; key signal for purchase campaignsInitiateCheckout— checkout flow started; used to optimise for checkout completionsPurchase— transaction completed; the most valuable conversion eventLead— form submitted or lead captured; critical for lead generation campaignsCompleteRegistration— sign-up or account creation completedSearch— search query performed on the siteAddPaymentInfo— payment details entered in checkoutAddToWishlist— item saved to a wishlistContact— contact form or call initiatedCustomizeProduct— product configurator or variant selector usedDonate— donation madeFindLocation— store or location finder usedSchedule— appointment bookedStartTrial— free trial startedSubmitApplication— application submittedSubscribe— subscription started
Limitations of static HTML scanning
This tool fetches the raw HTML the server returns and scans it with regex — it does not execute JavaScript. Events fired by user interaction (clicking a button, completing a purchase, scrolling to a section) will not appear in the results because those only run in a real browser session. For full dynamic testing, use the Meta Pixel Helper Chrome extension alongside this tool.
Some sites also block headless requests with bot-detection middleware. If the checker returns a fetch error, the site's server is likely rejecting the request — this doesn't mean the pixel is broken.
How to use it
Type or paste the full URL (with or without https://) and click Check. Results appear in seconds: a green banner confirms a pixel was found, a red banner means none was detected. Scroll down to see the pixel ID (with a one-click copy button), the checklist, any events found, and a list of issues to fix.
Free to use, no account required.