GA4 Companion — how it works

The GA4 Companion lives at /tools/ga4. Behaviour in, tickets out — one NiKKOS interface for what GA4 is telling you.

One magic-link covers VERA, DROP and LAND. There is no GA4 login and no account access: you paste the export, we check the live pages behind it.

• VERA — the events you expect, checked against what's actually in the live page source.
• DROP — funnel steps and where the fall-off happens, split into UX, Content, Eng or Tracking tickets.
• LAND — a landing export ordered worst-first into a P0/P1 Do-this board with owners.

1. 01Sign in once with your email — one-tap magic-link.
2. 02Pick the mode that matches the question.
3. 03Paste the export, or load the neutral example.
4. 04Let the live check run against each URL.
5. 05Export the tickets, grouped by lane so each team gets one job.

• Source scans cannot see everything a tag manager fires later, behind a consent gate or after client-side routing.
• An export is a snapshot, not proof of attribution.
• We never invent a drop rate, a session count or a conversion figure — every number is yours.
• DebugView and Realtime still matter where they should. FOUND is evidence, not the last word.

The sibling notes: GSC Companion — how it works for the Search Console side, and Tools hub — companions, not a junk drawer for choosing a door.

Per-mode detail sits in the VERA, DROP and LAND notes.