Client tracking audit: from 40 to 92 in four fixes

What you’re watching

• Tracking health ranks every client's tracking, worst first. The sample client, Thornbeck Outdoor Co., is at the top with 40/100.
• The client's tracking map shows how its site, GTM, GA4, the Meta pixel and the Google Ads account connect. GA4 and the pixel are marked Broken; the GTM container sends nowhere.
• The 20-rule audit reads the map and names each problem and its fix: two critical findings, calls that never reach Google Ads, and no conversion action.
• GA4 is repaired at the source, then recorded in Phloz: Working, its measurement ID, "Save + mark verified". The pixel is re-installed in Meta and verified the same way.
• GTM is connected to GA4, calls are routed into Google Ads, and the conversion action Google Ads was missing is added.
• Same client, 92/100. The audit runs every week, so the next client that slips shows up at the top of the list.

Phloz never changes anything in your Google accounts, and it doesn't watch tags live: it reads what your team records on the map and audits it every week.

The words on screen

The video has music and no voiceover; everything it says is on screen. Here it is in order.

1. This client’s tracking scores 40/100 — and nobody on the account knew.
2. Phloz scores every client’s tracking, worst first.
3. Each client gets a map of what’s wired to what.
4. A 20-rule audit reads the map. Each finding names the node and the fix.
5. You repair GA4 at the source. Then record it: Working, its measurement ID, Save + mark verified.
6. Pixel re-installed in Meta, verified in Phloz.
7. Connect GTM to GA4. Route calls into Google Ads.
8. Add the conversion action Google Ads was missing.
9. Same client. 40 → 92.
10. Typed. Connected. Verified.
11. The audit runs every week. You hear first, not your client.
12. Run the audit on your worst client.

The agency, its clients, contacts and figures are a demo workspace with made-up names; the screens are the app as it ships. It’s also on Phloz’s YouTube channel.