Your Meta Pixel is the foundation of every Facebook and Instagram ad campaign you run. If it is broken, under-reporting, or firing incorrectly, your campaigns are optimising toward the wrong data — and you are wasting ad spend without knowing it.
The good news: a solid Facebook pixel audit takes about 5 minutes if you know exactly where to look. This guide walks you through each step, what healthy output looks like, and what to do when you find a problem.
What Does a Facebook Pixel Audit Check?
A Facebook pixel audit is a systematic review of whether your pixel is installed, firing correctly, sending the right data, and not duplicating events. Specifically, you are checking:
- Whether the pixel is present on all pages
- Whether events fire at the right moments (page view, add to cart, purchase)
- Whether conversion events are being deduplicated correctly
- Your Event Match Quality score
- Whether there are stale or unused pixels still sending data
Even a small misconfiguration — like a purchase event firing on the order page but not passing a value — can cause Meta’s algorithm to underbid on your best customers. Regular audits catch these issues before they compound.
Before You Start: What You Need
- Chrome browser with the Meta Pixel Helper extension installed (free from the Chrome Web Store)
- Access to Meta Events Manager (business.facebook.com → Events Manager)
- Admin access to your website or store
- 5 minutes
Step 1: Check If the Pixel Is Installed on Every Page
Open your website in Chrome with the Meta Pixel Helper extension active. Click the extension icon in your browser toolbar. You will see one of three states:
- Green (pixel found) — pixel is firing on this page
- Yellow (warning) — pixel found but with issues such as duplicates or malformed events
- Red / grey (no pixel) — no pixel detected on this page
Check your homepage, a product page, your cart page, and your thank-you/order confirmation page. Each should show a green pixel. The thank-you page is the most important — this is where your Purchase event fires.
If the Pixel Helper shows yellow on any page, click “View Details” to see what the warning is. Common yellow warnings include firing the same event twice or sending an event with missing required parameters.
Step 2: Review Events Manager for Recent Activity
Go to Events Manager in your Meta Business Suite. Select your pixel and click the Overview tab. You will see a list of events your pixel has sent in the last 7 days, including event volume and the percentage received via browser versus server.
What to look for:
- PageView — should fire on every page. If it is significantly lower than your actual traffic, the pixel is missing from some pages.
- ViewContent / AddToCart / InitiateCheckout — check the funnel drop-off. If AddToCart events are 10x your purchases, that is normal. If they are equal, something is wrong.
- Purchase — this is your most important event. The event count should roughly match your order management system for the same period.
Click on the Purchase event and look at the parameters tab. Every purchase event should include: currency, value, order_id (for deduplication), and contents. Missing parameters here directly harm your campaign performance and Event Match Quality.
Step 3: Check Your Event Match Quality Score
Still in Events Manager, click on the Match Quality tab for your Purchase event. Meta assigns a score from 0 to 10 that indicates how well your customer data (email, phone, name) matches profiles in Meta’s system.
| Score | Meaning | Action |
|---|---|---|
| 8–10 | Excellent | No action needed |
| 6–7 | Good | Try sending more customer parameters |
| 4–5 | Fair | Check what parameters you are sending |
| 0–3 | Poor | Audit your CAPI or pixel data immediately |
A low match quality score means Meta cannot attribute your conversions to the right people, which reduces the effectiveness of your lookalike audiences and retargeting. If you are running server-side tracking via the Conversions API, ensure both browser and server events include customer email hashed with SHA-256.
Step 4: Look for Duplicate Events
Duplicate events happen when the same conversion fires twice — usually once from your browser pixel and once from your Conversions API — without proper deduplication. This causes over-reporting and makes Meta think you are getting more conversions than you actually are.
In Events Manager, look at your Purchase event and check the Deduplicated column. If a significant percentage of events are being deduplicated, that is a good sign — it means your deduplication is working. If you are using both pixel and CAPI but seeing zero deduplication, your event_id values may not be matching between the two.
To check for browser-only duplicates, use Meta Pixel Helper on your thank-you page and count how many Purchase events fire. You should see exactly one. If you see two or more Purchase events without a server-side source, you have a duplicate pixel or a script loading twice.
Step 5: Test Your Key Conversion Events Live
In Events Manager, go to Test Events. Enter your website URL and click Open Website. This opens your site in a special mode where Meta captures every event in real time. Complete a test purchase using your store’s test payment mode and watch the events appear in the panel on the right.
What to verify:
- PageView fires immediately when the page loads
- AddToCart fires when you add a product, not on page load
- InitiateCheckout fires when you enter the checkout
- Purchase fires only once on the thank-you page, with the correct value and currency
If any event fails to appear during the test, check the Meta Pixel Helper on that page for error details.
What a Healthy Pixel Audit Looks Like
| Check | Healthy Result |
|---|---|
| Pixel installed on all pages | Green in Pixel Helper on every page |
| PageView volume | Matches your actual traffic in Analytics |
| Purchase event count | Matches orders in your system (±5%) |
| Purchase parameters | Includes value, currency, order_id, contents |
| Event Match Quality | 7 or higher on Purchase event |
| Duplicate events | Zero browser-only duplicates; CAPI deduplication working |
| Test Events | All events appear correctly in real-time test |
Common Problems Found in Pixel Audits and How to Fix Them
Problem: Pixel missing from some pages
Fix: If you are on Shopify, check that your pixel is added through Customer Events in Shopify Admin, not just hardcoded into a theme. If you are using GTM, verify the trigger on your base pixel tag fires on All Pages, not specific pages only.
Problem: Purchase value is $0 or missing
Fix: Your purchase event is not pulling the order total correctly. For Shopify, check that your pixel integration uses the checkout total price. For WooCommerce, verify your pixel plugin hooks into the order complete page, not the payment pending page.
Problem: Low Event Match Quality (below 6)
Fix: Check what customer parameters you are sending with your Purchase event. At minimum, send hashed email and hashed phone. If you are using CAPI, ensure your server-side events also send first name, last name, and city. Each additional parameter increases your match quality score.
Problem: Purchase event fires multiple times
Fix: Use the event_id parameter on both your browser pixel and CAPI events, with the same value for the same order. Meta uses this to deduplicate. Also check that your thank-you page is not loading your pixel code twice.
Problem: Events are not showing in Events Manager
Fix: First check whether the pixel ID in your code matches the pixel ID in Events Manager. A mismatch means events are going to a different pixel. Also run the audit in an incognito window with extensions disabled to rule out ad blocker interference.
When Should You Run a Pixel Audit?
Beyond a monthly routine, run a pixel audit immediately after any of these events:
- Switching themes or redesigning your website
- Migrating your store to a new platform
- Installing or uninstalling a marketing app
- Changing your checkout process or adding a new payment gateway
- Seeing an unexpected drop in reported conversions in Ads Manager
- Scaling ad spend significantly — issues that were small at £1,000 per month become expensive at £10,000 per month
The 5-minute audit process outlined here is designed to be fast enough to run any time you make a change to your site. After completing your tracking audit, prioritise fixes in this order: pixel coverage first, then purchase value accuracy, then duplicate events, then Event Match Quality.
What to Do After Your Audit
Once you have made fixes, re-run the audit using the Test Events tool to confirm everything is working before relying on your live data again. Make pixel audits part of your monthly routine. A quick 5-minute check catches problems before they cost you real money.
If you are running both a browser pixel and CAPI, use Events Manager’s deduplication data to confirm both sources are sending matching event IDs. If deduplication is at zero, investigate why — it likely means your server-side events are not reaching Meta or are using different event IDs than your browser events.
Related Articles
- Meta Pixel vs Conversions API: Which One Do You Actually Need?
- What Is Meta Conversions API? A Complete Guide
- Tracking Explained: How Every Ad Platform Tracks Your Ads
- Free Tracking Audit Checklist: Is Your Setup Working?
📋 Not sure where to start? Use our Free Tracking Audit Checklist to find out where your setup is losing data.
Book a free tracking audit → We’ll review your setup and tell you exactly what to fix.