Client onboarding audit

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.

• The previous agency never documented anything — every account password is in someone's head, every tracking property is in a different state of repair, and the client doesn't remember what they paid for
• Half the conversion events fire but none of them are tied to revenue — the previous setup tracked engagement, not outcomes
• The GTM container has 60 paused tags and 40 active ones, no way to tell which are still needed without testing each one
• Pixel installations are inconsistent across the site — some pages have it twice, some pages don't have it at all

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 long does a Phloz onboarding audit actually take?

The first time you run it on a new client, plan 90 minutes — most of which is gathering credentials and verifying access. The second time (and every subsequent client) it's 30-60 minutes because the template guides you through the same 30 nodes in the same order. Agencies running this monthly across 5+ new clients report consistent 45-minute median time.

What if the client's existing setup is too messy to document in an hour?

The audit deliberately scopes to "what exists today" — not "what should exist." If something is so broken you can't verify it in 5 minutes, mark it `broken` and move on. The output of the audit is the input to the strategy conversation: "here's what we found broken, here's what we'd charge to fix." Many agencies bill the audit itself as a discrete deliverable.

Does Phloz auto-detect what's configured, or is this manual data entry?

V1 is manual entry guided by the template — you click through the client's GA4, GTM, ad accounts, and confirm each node's configuration. V2 will add API-based auto-discovery for GA4 properties + GTM tags + Google Ads conversions. Manual is intentional for V1: the act of clicking through forces verification, which catches setups that look correct in the API but fire incorrectly in practice.

Other use cases

Other ways agencies put Phloz to work.

• Tracking infrastructure map
• Cross-client reporting
• Agency project management
• All use cases→