Posted by: Justine Jay Canete
Date Posted: October 29, 2026
Back to Case Studies
Issue
- After the site launch (~June 10), the GA4 property showed a near-complete drop in sessions, page views, and key events starting June 11.
- GTM was confirmed to be installed and firing, and the Measurement ID (G-J71E58HX3B) matched between GTM and GA4 Admin, ruling out a typo or basic misconfiguration.
- The
gtag/js?id=G-J71E58HX3B request returned a 404 and was blocked in the browser as net::ERR_BLOCKED_BY_ORB. The tag never loaded, so no events could fire.
Solution
- The Google Tag interface showed that G-J71E58HX3B was configured as a Connected Site Tag (destination) under a separate Google tag, G-S7QGJGQDVJ.
- G-S7QGJGQDVJ had been removed from the site, most likely during the redesign/launch, which broke the connected-tag relationship.
- Adding G-S7QGJGQDVJ back into GTM re-established the connection, and data began flowing to G-J71E58HX3B immediately.
Achievement
- Full GA4 tracking was restored on the same day the investigation began, with data flow confirmed in Realtime and DebugView.
- The root cause (the Connected Site Tags dependency) was identified and documented for the client.
- Expectations were set that the gap in data from June 11 onward is not recoverable.