All topics

Tracking infrastructure map

Map GA4, GTM, pixels and ad accounts as a visual graph, with audit findings and their history.

What is the tracking map?

Each client has a map of their tracking setup: GTM containers, GA4 properties, ad accounts, pixels, server-side endpoints and conversion APIs. Nodes are joined by connections ("sends events to", "fires pixel" and so on), so you can see how the data flows at a glance.

Open a client and choose the Tracking map tab. For more room, click Open full screen.

Connecting Google (GA4, GTM, Google Ads)

In Settings → Integrations, choose Connect Google. Phloz only reads from Google (Google Ads has no read-only permission, so Google's consent screen lists edit rights too); then Import from Google on a client's map lists the GA4 properties, GTM containers and Google Ads accounts that Google account can see.

Google may ask for a passkey before it allows Google Ads access (rolling out since August 2026). If your Google account has no passkey, create one at g.co/passkeys before you connect: Google can take up to 7 days to accept a new passkey.

Keyboard shortcuts

  • n: add a node.
  • /: search the map.
  • Enter: open the node you've tabbed to, or edit the connection you've tabbed to.
  • Backspace (the delete key on a Mac): remove the selected connection. To delete a node, open it and click Delete, or Shift-drag to select several nodes and click Delete in the bar that appears.

To connect two nodes, drag from the dot on one node to another. Or open a node, go to Connections, pick a node under Connect to and click Add connection….

n and / only work while you're on the map. If one-key shortcuts get in your way (for example with voice control), turn them off in the Keyboard shortcuts sheet; press ? to open it.

Node health

Click a node to open its side panel and set its health: Working, Broken, Missing or Unverified. Save keeps your changes. Save + mark verified also records today's date and your name ("Last verified … by …"), so the team can see who last checked it. Only use it once you've confirmed the tracking works.

Audit + history

Phloz re-checks every map when you open the dashboard, and runs a full audit every Monday at 08:00 UTC. A client's Audit tab lists what the check finds right now (critical issues, warnings and info) and a History of up to the last 13 audits, about three months, each with a 0–100 score. That shows whether the setup is getting better or worse. You can switch between Timeline and a 90-day chart.

Owners and admins can click Run now on the dashboard's Tracking audit card, or on a client's Audit tab, to re-check straight away, which is useful right after fixing something. The result appears after a minute or two; reload the page to see it.

Anyone who can edit the client can click Create task on a finding. The task lands on the client's Tasks tab with the finding's title, the node it's about, what the audit found and the suggested fix, and a last line naming the audit rule it came from. Critical findings become high priority, warnings medium and info low. The finding then shows Task open and links to that task until it's done. Renaming the task or the node keeps the link; deleting that last line from the description breaks it.