Tracking infrastructure map

Common challenges agencies hit on this

The recurring obstacles agencies report when running this use case. Honest list — these aren't Phloz-specific problems, they're patterns we see across most agencies regardless of tooling. Worth recognising even if you don't end up on Phloz.

• Tracking documentation decays the day it's written — a Google Sheet last updated six months ago is worse than no documentation, because the agency relies on it
• When a single tracking node breaks (e.g., GA4 measurement ID changed), the downstream effects (broken audiences, wrong-shaped conversion data) take weeks to surface in optimisation reports
• Onboarding a new agency hire to "how this client's tracking works" takes hours of meetings, because the knowledge lives in the head of whoever set it up
• When the client moves to a new agency, handing over a clean tracking-infrastructure document is the difference between a clean exit and a 6-month support tail

How agencies use this in practice

The pattern that works across most agencies running 5–50 clients: scope the use case as a discrete operational surface, assign a single owner (usually the ops lead or tracking engineer), set a recurring cadence (weekly check, monthly audit, quarterly review), and connect it to the rest of the agency's work via the tracking map and the per-client task surface.

The 1-2-week setup window is the same regardless of tool — the differentiator is whether the tool ships the primitives you need (client, tracking node, recurring task, audit template) or makes you build them yourself out of custom fields. Phloz ships them; generic PM tools don't. That's the entire trade-off, and it's only worth paying for once you have the client volume to need it (typically 5+ retainers).

Frequently asked questions

The three questions agencies ask most often about this use case. Honest answers — same data we'd give a friend evaluating the approach.

How is the tracking infrastructure map different from Tag Inspector or ObservePoint?

Tag Inspector + ObservePoint are crawlers — they audit pages by visiting them and scraping what fires. They're great for "is the tag firing?" questions. The Phloz tracking map is a documentation + relationship layer — it answers "what tags should fire and how do they connect?" The two are complementary, not competitive. Mature agencies use both: ObservePoint to verify, Phloz to document.

Can the tracking map be exported for client handoffs?

Yes — every client's tracking map exports to JSON (Phloz's own format; there is no CSV export of the map). It works as a deliverable when handing the client over to in-house teams or to a different agency: any tool that reads JSON can parse it, and another Phloz workspace can import it directly.

How many node types does the tracking map support?

23 typed node types, one of which (the GA4 data stream) is retired and kept only for existing maps. They cover websites and landing pages, GTM web and server containers, GA4 properties, non-GA4 analytics (Matomo, Piwik Pro, Adobe, Plausible, Fathom), Google Ads accounts and conversion actions, Meta ads accounts, pixels and the Conversions API, TikTok ads accounts and pixels, Microsoft Ads accounts (with the UET tag ID), LinkedIn Ads accounts (with the Insight Tag ID), CRM, email and e-commerce platforms, call tracking, server and conversion-API endpoints, and a generic `custom` type for anything not covered — a Pinterest tag, say.

Related in Phloz

• GTM container checker (free)Reads a container export in your browser; nothing is uploaded.

Other use cases

Other ways agencies put Phloz to work.

• Client onboarding audit
• Cross-client reporting
• Agency project management
• AI tracking audit
• Client request tracking
• Google Ads alerts
• AI client management
• All use cases→