Why does our Meta pixel show as not active or not working, and how do we fix it?
Our answer
Inactive means the pixel isn't sending events correctly. Check your site with Meta Ads Data Advisor and Test Events, then fix the first break: missing code, a wrong pixel ID, consent or ad blockers, or a paused Shopify app pixel.
- Confidence
- Medium
- Strongest proof
- 8 Meta rules
- 3 practitioners, 1 opinion or claim
- Sources
- 5 sources
- 12 statements
- M
New here? Take the 1-minute tour
Why this is the answer
4 reasons and our judgmentInactive is Meta's own status for a pixel that isn't sending events correctly. Meta Ads Data Advisor, the free Chrome and Edge extension formerly called Meta Pixel Helper, shows it on your live pages. A pixel can read Active while single events carry warnings (Meta).
Most breaks start on your own site. Meta lists base code missing or moved after a site update, broken event code, moved pages, a site outage and a wrong domain allow list as common causes of lost events.
Privacy settings can silence a working pixel. Ad blockers can block a web pixel entirely, and Shopify's checker may show it waiting for consent. Shopify's default Optimized setting can pause an app pixel's data, so WeltPixel, a Shopify tracking app maker, checks it first.
A freshly installed pixel should show up within minutes. Meta says to wait a few minutes and refresh if a PageView doesn't appear. Event data may take 30 minutes or more to reach your reports, so check Test Events meanwhile.
Our judgment
Work through the checks in order: the extension first, then Test Events, then store settings and Diagnostics. Each step shows whether the break is on the page, between the browser and Meta, or in a setting.
Our judgment, built from Meta, Ads Uploader, Shopify and WeltPixel: our reading of these sources, not a finding from any one of them.
What the sources say
12 statements from 5 sourcesMeta says pixel event drop alerts compare counts with a week earlier and the 7-day average. Common causes include missing or broken code after site changes, seasonal dips, site outages and allow or block lists.
“If your website is down, no events will be sent.”
Meta's test events tool shows which events are processed and deduplicated. Web events are recorded only while the tool's page is open, and data can take 30 minutes or more to reach reports.
“For website events, activity is only recorded while the test events web page is open.”
Meta's pixel setup tips: check the base code, troubleshoot inside your tag manager, spell standard events correctly since they are case sensitive, and use the test events tool.
“Events are case sensitive.”
Meta's Events Manager flags an error when one purchase sends four or more purchase events, which can over-report purchases and hurt delivery of conversion and catalog sales ads.
“This error can lead to over-reporting of purchases and may negatively impact delivery of ads using Conversion or Product Catalog Sales objectives.”
Ads Uploader says Meta Pixel Helper shows what the browser sends, but Events Manager is the real proof. Don't add a second base pixel, and no event before consent is correct.
“Confirm Events Manager received the event. That's the real proof.”
Shopify says pairing server pixels with web pixels gets the most customer events through; ad blockers can block web pixels, which cuts third-party attribution but not Shopify's own reports.
“What's reduced or lost is third-party attribution”
Shopify's app pixels default to Optimized data access, which can pause a marketing pixel that shares more data than needed. Server pixels, open to certain apps, still follow your store's consent settings.
“Server pixels are still subject to your store's customer privacy and consent settings.”
Meta says its free Meta Ads Data Advisor browser extension replaces Pixel Helper. Common setup errors are duplicated pixel code and placing the base code outside the head section.
“Ensure the Pixel code isn’t duplicated on a single page.”
Jetfuel, an agency, says to run the Meta Pixel and Conversions API together with a shared event ID and name, check deduplication in Test Events, and pass hashed customer details to raise match quality.
“Run the Pixel and CAPI together, never as substitutes”
Ads Uploader says a pixel showing no data usually stems from a rushed setup: check the code is live with the right ID, use Pixel Helper and Test Events, and rule out ad blockers or consent banners.
“Most "my pixel isn't working" problems trace back to a rushed setup, not a broken pixel.”
Meta recommends placing the Pixel base code in the head tags of every tracked page, then checking Events Manager for a PageView event to confirm the install.
“Placing the code within your <head> tags reduces the chances of browsers or third-party code blocking the Pixel’s execution.”
WeltPixel, which sells server-side tracking, says Shopify made Optimized the default for app pixels on January 13, 2026, which can throttle them; set pixels you rely on to Always on and check this first.
“Put the pixel Mode check first in any tracking troubleshooting runbook.”
In the full answer
For readers who sign in- What to do this week3 steps
- The numbers behind it2 figures from cited sources
- The strongest disagreementThe best case against the answer, from a cited source
- How sure we areWhat its confidence rests on, and what would change the answer