Diagnosing a Silent GA4 Tracking Failure: How a Native BentoBox Integration Suppressed GTM’s Google Tag

Posted by: Justine Jay Canete Date Posted: August 27, 2026
Back to Case Studies

Issue

GA4 event tags (click_to_resy, contact_us, phone_click, and others) were firing correctly in GTM Preview but producing zero network requests and not populating in GA4 DebugView or Realtime reports. RCFX conversion tracking was unaffected.

Solution

The client’s site was built on BentoBox, which has a native GA4 integration that installs its own hardcoded gtag.js snippet. This created a duplicate Google Tag for the same Measurement ID (G-Z4Z279VL49) alongside the Google Tag already configured in GTM. When both are present, Google’s built-in deduplication logic detects the duplicate Measurement ID and suppresses the GTM instance. GTM still marks the event tags as “fired” in its execution layer, but the underlying Google Analytics transport never initializes within GTM’s context, so no collect requests are dispatched. Disconnected the native GA4 integration in BentoBox and confirmed GTM as the sole owner of the Google Tag. All event tracking was already fully built in the GTM container, so no additional configuration was needed.

Achievement

Restored GA4 event tracking across all configured conversions for both L’Amico and Skirt Steak.

 

Snippet/Screenshot/Link

Snippet/Screenshot/Links:
QA screenshot confirming the event firing correctly after the fix: https://webpagefx.mangoapps.com/msc/MjkzODgwMl8yNTIzNjkyNA