Why it happens
The code was never installed
The code was never installed
The pixel was created in Events Manager and the setup stopped there. Creating a dataset installs nothing on your site.
You are looking at the wrong pixel
Accounts collect pixels: one from an old agency, one from a Shopify app, one made by hand. The site fires one of them, the ads point at another.
The code is on a staging site or another domain
Installed on a preview URL, a store subdomain or a site that has not launched. No real visits, no events.
A platform integration was disconnected
Reinstalling a store app, changing themes or switching accounts in a partner integration quietly drops the connection to the dataset.
The pixel is marked unavailable
Meta can mark a pixel unavailable, and then it cannot be used for tracking or ads at all, however much the site fires it.
How to fix it, step by step
Find every dataset
In Business Settings, open Data sources, then Datasets. List every one the business owns and note which ad accounts each is connected to.
Find the one your ads use
In Ads Manager, open a conversion ad set and read the Dataset under Conversion. That is the pixel that has to be active.
Install it on the live site
In Events Manager, open Connect data sources, choose Web and follow the partner integration for your platform, or paste the base code into the site-wide head. Remove copies of other pixels you no longer use.
Visit the site and test
Open Test events in the same dataset, enter your live URL and browse. PageView shows within seconds when the code is right.
Recheck the status
Go back to Overview after real traffic. The status changes once events arrive.
Steps checked against Meta Business Help Center articles: Set up the Meta Pixel for your website; Troubleshoot your Meta Pixel; Connect a dataset to an ad account.
Sprites diagnoses this
Sprites diagnoses it
Sprites reads your pixel and CAPI health and shows where it breaks, starting with which pixel your ads actually depend on.
What Sprites does
- Lists every pixel connected to the ad account, so you check the one that matters.
- Reads which pixel and which event each ad set optimizes for.
- Reads whether each pixel received any events in the last 7 and 28 days, and when it last fired.
- Reads whether Meta marks a pixel unavailable.
What it doesn't do
- Install the pixel on your site
- Create a dataset or connect a partner integration
- Read domain verification, which Meta does not expose to its API
Questions
What does No activity yet mean on a Meta pixel?
Meta has never received an event from it. The code is not installed, is installed somewhere nobody visits, or the site fires another pixel.
How long does a Meta pixel take to become active?
Minutes after the first real visit to a page with the code. If a day of traffic passes and it still shows nothing, the install is wrong.
Do I need to verify my domain for the pixel to work?
No. Since June 2025 Meta no longer requires a verified domain to set up web events. Verification still matters for editing link previews and proving ownership.
Should I create a new pixel?
Usually not. A new pixel starts with no history. Find out why the existing one is silent and use that one.
Can my ads run with an inactive pixel?
They can spend, but an ad set optimizing for purchases or leads has nothing to learn from and reports no results.
See where it breaks
Connect your accounts. Sprites reads them side by side and shows you exactly where the numbers split.