GA4 · Google Tag Manager · Setup and debugging
Tracking that you can prove is working
Each guide does one job in GA4 or Tag Manager: install it, fire one event, or find out why an event never arrived. The steps follow Google's own help pages, opened and read on the date printed on the guide. A container file or an event reference downloads with the guide, so nothing has to be retyped from a screenshot.
Latest guides
-
2026-11-11Verified
Install GA4 with Google Tag Manager: the Google tag, the first page_view, and the check that proves it works
One Google tag on the Initialization trigger sends page_view on its own. No second page_view tag, verified in Tag Assistant Preview, published as a version.
-
2026-11-11Verified
Your GA4 purchase event never arrives: trace it with Tag Assistant and DebugView
Four checkpoints, in order: Preview, DebugView, the Measurement ID, and the 24 to 48 hour lag plus the custom dimension. Worked with Google's example order at $72.05.
How a guide is checked
Google's help pages are the source of truth for every click path and every field name. Container files are validated structurally before they ship: the JSON must parse, every tag's trigger must resolve, and every variable a tag references must exist. Numbers that come from Google's examples are recomputed here first — the example order in the purchase guide is $72.05 because 10.01 × 3 plus 21.01 × 2 is 72.05, and that arithmetic was run, not copied. The Method page states what was run and what was not.