Floodlight recording zero visits despite confirmed site traffic.
Four simultaneous causes: a Floodlight snippet hardcoded in the HTML duplicating the GTM-fired tag, undefined consent, missing tag sequencing, and a second GTM container of unknown origin.
Universal Pixel implemented as the setup tag, consent requirements added, tags renamed to reflect their actual scope.
Validated in Preview and published. A diagnosis with several simultaneous causes, not one.
Context
"Zero visits recorded in Floodlight" is the kind of symptom that invites looking for one obvious cause. The first surface-level check found nothing clearly broken — the tag was there, it was firing, and data still wasn’t arriving. That was the signal the problem wasn’t simple.
How it was actually solved
A second GTM container of unknown origin
The most unexpected cause: a second Google Tag Manager container was installed on the site, left over from an earlier implementation nobody on the current team knew was still active. That ghost container fired its own version of the Floodlight tag, directly conflicting with the "official" one — a case of invisible technical debt that no audit looking only at the container you assume is active would ever catch.
Why missing sequencing made an existing problem worse
With two containers competing and a hardcoded snippet adding to the mix, the order tags fired in wasn’t deterministic — sometimes Floodlight ran before consent was resolved, sometimes after. Without explicit sequencing, behavior changed session to session, which made the problem look "intermittent" when it was actually consistent — just not in its timing.
When the obvious explanation doesn’t quite fit the symptoms, it’s almost always because more than one cause is acting at once. Chasing a single root cause on a diagnosis with contradictory symptoms leads to fixing one piece and leaving the other three intact.
FAQ
How do you find a "ghost" GTM container nobody knows exists?
By inspecting the page source for every GTM snippet actually present, not just the one documented for the project. Any container ID you don’t recognize is a lead worth chasing.
Why Universal Pixel instead of the original setup tag?
Universal Pixel centralizes Floodlight configuration into a single reference tag, reducing the risk that a future duplication — like the one that caused this problem — goes unnoticed again.