Your Ads Are Running, Your Sales Are Coming In, and Your Pixel Has Been Dead for Months
The numbers in Ads Manager look a little off. Not wrong enough to stop the campaign, just wrong enough to nag at you. You tell yourself the algorithm is learning, or attribution is weird right now, or maybe it's iOS. Meanwhile, facebook pixel not tracking is exactly what's happening, and nothing in your dashboard is going to tell you that directly.
A financial media company running two newsletter brands had this problem. Their funnel pages had been moved off WordPress and onto edge infrastructure. Fast pages, clean URLs, great conversion rates. The business was working. But Tag Manager doesn't run at the edge, and that meant the meta pixel had gone completely quiet. No events firing. No signal reaching Ads Manager. Months of ad spend optimizing against nothing.
The failure surfaced in an infrastructure audit, because that is the only place this kind of failure shows up. The ads kept running. The sales kept coming in from somewhere. The silence in Events Manager just looked like peace.
That is the part worth sitting with. A dead pixel does not announce itself. Your campaigns do not pause. Your ROAS does not crater overnight in a way that triggers an obvious alarm. The data just stops being real, and your optimization engine keeps making decisions as if it were.
This is not an edge case reserved for companies with unusual infrastructure. Any funnel page that lives outside your main site, whether that is a dedicated landing page host, a headless setup, or an edge deployed environment, is a candidate for exactly this failure. The more sophisticated your infrastructure, the more likely Tag Manager was never part of the picture to begin with.
Why Tag Manager Goes Quiet at the Edge and What to Do Instead
The problem starts with infrastructure. When funnel pages move off WordPress or a standard CMS and onto edge deployed environments like Cloudflare Workers, Google Tag Manager stops working. GTM depends on a DOM it can attach to and a page lifecycle it can follow. At the edge, that lifecycle does not exist in the same way, so the container loads nothing, fires nothing, and reports nothing.
The result is a facebook pixel not tracking situation that produces no error message. Ads Manager keeps spending. Sales keep arriving through other channels. The silence looks like peace.
The fix is not a workaround inside GTM. It is removing GTM from the equation entirely for those pages:
- Hardcode the Meta pixel base code directly into the HTML of each edge deployed page, not through a tag manager layer
- Hardcode the GA4 measurement snippet the same way, so both fire on every page load regardless of environment
- Send a clean test event after every deployment, not just once at setup, because edge functions can be updated without triggering any tag audit
- Check Events Manager and GA4 DebugView after each test to confirm the event arrived with the right parameters
That last point matters more than most teams realize. A pixel can be present in the code and still fail to fire correctly if the event payload is malformed or the pixel ID is wrong. Seeing the snippet in the source is not the same as seeing a confirmed event in Events Manager.
When conversion tracking breaks like this, the ad algorithm is optimizing on incomplete data. It thinks certain audiences or creatives are underperforming when they may be driving the sales that are coming in through other attribution paths. Months of budget can shift in the wrong direction before anyone runs an infrastructure audit.
If your funnel lives anywhere other than your main site, the tracking assumption you made at launch may no longer be true.
Open Events Manager Right Now and Check Whether It Is Listening
Go to Events Manager in Meta Business Suite and look at the activity graph for your pixel. If the line is flat or the last recorded event was weeks ago, that is not a data delay. That is a dead pixel, and your campaigns have been running without it.
The diagnostic is simple. Open Events Manager, select your pixel, and look at the "Test Events" tab. Send a test conversion from the page you care about most. If nothing appears within thirty seconds, the pixel is not firing. At that point the question is not whether you have a tracking problem, you do, and the question becomes how long it has been broken and how much budget optimized against nothing.
Most business owners find out from an audit, not from a complaint. The ads keep running, the sales keep coming in from somewhere, and the dashboard numbers look slightly off in a way that is easy to explain away. That is exactly the environment where a facebook pixel not tracking failure hides for months.
If your funnel pages live anywhere outside your main website, a separate subdomain, a hosted checkout, a landing page tool, an edge deployed environment, check them individually. Each one needs its own verification. A working pixel on your homepage tells you nothing about what is happening on the page where someone buys.
Once you know the pixel is firing, confirm that the events match what you expect: the right event names, the right values, no duplicates. A pixel that fires twice on every purchase will make your cost per conversion look half as good as it is, which is its own kind of damage.
If you want to see the full state of your tracking setup in one place, pixel health, GA4 configuration, conversion event coverage, get your free tracking grade and find out exactly what your ad spend is and is not seeing.