Ajax Tracking

Argument piece comparing Ajax form tracking in GTM versus TagCompanion. GTM's accurate solution requires custom JavaScri... full excerpt

Argument piece comparing Ajax form tracking in GTM versus TagCompanion. GTM's accurate solution requires custom JavaScript that most marketers can't write, so they fall back to a visual workaround that measures the wrong event and quietly corrupts ad platform signals. TagCompanion generates the same network-level container without any code. Same output, different path. Ends with the honest scope.

Last Tuesday, a developer pushed a CSS update. A class name changed. The tracking broke. Nobody noticed until Friday whe... full excerpt

Last Tuesday, a developer pushed a CSS update. A class name changed. The tracking broke. Nobody noticed until Friday when the ROAS tanked. That is the GTM problem in its most concrete form: the standard workflow produces tracking that is designed to break. No error, no alert, no warning. The data stops, and your ad platform flies blind. The complexity GTM veterans mastered was never the destination. Clean conversion data was. That era is ending.

AJAX form submissions don't reload the page. That's great for user experience. Terrible for tracking. Google Tag Manage... full excerpt

AJAX form submissions don't reload the page. That's great for user experience. Terrible for tracking. Google Tag Manager's standard triggers can't detect them. You need custom JavaScript to intercept the requests and capture the responses.