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 or CSV. Some agencies use this as a deliverable when handing the client over to in-house teams or to a different agency. The structured format means the receiving party can re-import into their own tooling without manual translation.

How many node types does the tracking map support?

V1 ships with 9 typed node types (GA4 property, GTM container, Meta pixel, Google Ads conversion action, TikTok pixel, Microsoft Ads UET tag, audience, UTM convention, page) plus a generic `custom` type for anything not covered. V2 adds typed support for Klaviyo flows, Shopify pixels, HubSpot tracking, LinkedIn Insight, Pinterest CAPI, and 5 more.

Use case

Tracking infrastructure map

The thing no other agency platform has: a typed, relational map of every pixel, tag, property, and audience you manage — across every client.

The spreadsheet problem

Most agencies document tracking in a Google Sheet per client. Three problems: no relationships, no health state, no types. When something breaks, it lives in one person's head.

The graph approach

Phloz models tracking as a graph: typed nodes (GA4, GTM, Meta, Google Ads, TikTok, Microsoft, audiences, UTMs, pages) and typed edges (fires-on, owned-by, depends-on). Click a node — see every pixel that depends on it, every ad account that owns it, every page it fires on.

What you get

A single visual graph per client. Health states (working / broken / missing / unverified) you can filter by. Last-verified timestamps. "Who owns this?" answerable in one click. And a clean export to JSON so you can pipe it into whatever comes next.

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 or CSV. Some agencies use this as a deliverable when handing the client over to in-house teams or to a different agency. The structured format means the receiving party can re-import into their own tooling without manual translation.
How many node types does the tracking map support?: V1 ships with 9 typed node types (GA4 property, GTM container, Meta pixel, Google Ads conversion action, TikTok pixel, Microsoft Ads UET tag, audience, UTM convention, page) plus a generic `custom` type for anything not covered. V2 adds typed support for Klaviyo flows, Shopify pixels, HubSpot tracking, LinkedIn Insight, Pinterest CAPI, and 5 more.

Other ways agencies put Phloz to work.

Start your free trial

14 days free · No credit card · Starter tier free forever