Why does my Shopify storefront fire a different pixel ID than the dataset I monitor
Your storefront is firing a Meta pixel, but its ID does not match the dataset you connected. Events are landing in a different (possibly old or wrong) dataset, so the ad account wired to this dataset sees nothing. To fix it, open Meta Events Manager and check which dataset your ad campaigns actually optimize against. Compare that dataset ID with the pixel ID captured in PixelSentry's alert evidence. Then update the Shopify Meta integration to use the correct pixel/dataset, or reconnect PixelSentry to the dataset your storefront actually fires. PixelSentry found this because every 6 hours a headless browser visits your storefront like a shopper and verifies your Meta pixel code loads and generates tracking requests, and every 2 hours it reads Meta's Dataset Quality metrics to confirm Meta receives and matches your events. It alerts only on confirmed breakage, with the captured evidence attached.
What is actually happening
Your storefront is firing a Meta pixel, but its ID does not match the dataset you connected. Events are landing in a different, possibly old or wrong, dataset. Because the ad account is wired to the dataset you connected, and your events are going somewhere else, that ad account sees nothing coming in even though tracking on the page looks like it is working.
This is a mismatch, not a total outage. The pixel code loads. Requests fire. Data moves. It simply arrives at the wrong destination, which is why this kind of problem often hides in plain sight until conversions stop showing up where you expect them.
How PixelSentry confirmed it
Every 6 hours a headless browser visits your storefront like a shopper and verifies your Meta pixel code loads and generates tracking requests. That check reads the pixel ID your storefront actually fires, which is the ID captured in PixelSentry's alert evidence.
Every 2 hours PixelSentry reads Meta's Dataset Quality metrics to confirm Meta receives and matches your events. That is the other side of the pipe: what the dataset you connected is actually receiving.
The signal is direct: the crawl captures the pixel ID your storefront actually fires, and PixelSentry compares it against the dataset you connected. When the fired IDs do not include your connected dataset's ID, that mismatch is the diagnosis, and the captured request is attached to the alert as evidence.
How to fix it
In Meta Events Manager, check which dataset your ad campaigns actually optimize against. This is the dataset your spend depends on, so it is the one that has to be receiving events.
Compare that dataset ID with the pixel ID your storefront actually fires, captured in PixelSentry's alert evidence. If they are the same, your storefront and your campaigns already agree, and the dataset PixelSentry monitors is the odd one out: reconnect PixelSentry to the dataset your storefront actually fires. If they differ, you have found the break: your storefront is sending to one place and your campaigns are reading from another.
Update the Shopify Meta integration to use the correct pixel/dataset, or reconnect PixelSentry to the dataset your storefront actually fires. Which direction you go depends on which ID is the correct one for your ad account. Either way, the goal is a single ID shared end to end.
Why this keeps getting caught
Standing verification means something checks your storefront continuously on a schedule, not only when you manually look.
Because the storefront crawl runs every 6 hours and reads the pixel ID your store actually fires, a fresh mismatch surfaces on the next crawl rather than waiting for you to notice missing conversions. When tracking recovers, PixelSentry sends the all-clear too, so you know the two IDs line up again without having to go back and confirm it by hand.