Analytics
Google Analytics 4 integration for digital marketing agencies
GA4 is the analytics layer most digital marketing agency clients live on, and it's also the one most often misconfigured at handoff. A broken GA4 setup tanks attribution accuracy, breaks audience exports to ad platforms, and silently degrades campaign optimisation. Tracking GA4 properties as typed objects — not as URLs in a custom field — is the difference between catching a misconfiguration on day three and finding it after a quarter of bad spend.
How Phloz models Google Analytics 4
Every Google Analytics 4 concept that matters for digital marketing agency operations is a typed object in the tracking map. Health state per node, audit cadence, and graph relationships to every other tracking-system node it touches — so a broken tag or misconfigured property is findable in seconds across your full book of clients.
- GA4 property as a typed node with measurement ID, data stream IDs, owner, and health status (working / broken / missing / unverified)
- Linked tags (GTM container that fires it, conversion actions it surfaces, audiences it builds)
- Last-verified timestamp + verification cadence — agencies set "verify quarterly" and Phloz reminds the assigned engineer
- Per-client visibility: every GA4 property your agency manages, across every client, in one queryable graph
Common Google Analytics 4 configuration gotchas
The configuration mistakes agencies most often make with Google Analytics 4, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.
- Conversion events vs key events: GA4 renamed "conversions" to "key events" in 2025, but most older agency setups still use legacy conversion event names. Verify both surfaces match.
- Cross-domain tracking: client domains + agency tracking subdomains break attribution if the GA4 property's data stream config doesn't list every host. Audit the data stream's "Configure your domains" list at every client onboarding.
- Internal traffic exclusion: agencies forget to exclude their own IP ranges + their client's office IPs, polluting client analytics with agency review traffic. Set this once at property creation and the data stays clean.
At launch (V1)
GA4 properties appear as typed nodes in the tracking map with measurement IDs, owner, health status, and last-verified timestamp.
Coming (V2)
Live sync via the GA4 Data API: read real conversion events, audience sizes, and property metadata directly into Phloz.
Why we built the integration this way
Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With every Google Analytics 4object as a typed tracking node, the agency can answer questions like "which clients have a misconfigured Google Analytics 4setup?" or "which Google Analytics 4configurations changed last quarter?" from a single graph query.
The V1 surface is intentionally manual — agencies enter the configuration at onboarding rather than auto-importing. This forces explicit verification at the exact moment the agency takes over the client's tracking, catching most of the commonGotchas listed above before they become production issues. V2 will add API-based sync where the underlying platform supports it; we won't add sync where the underlying API doesn't expose the right data.
When to use this in your client onboarding flow
The standard pattern for digital marketing agencies running Phloz: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Google Analytics 4configuration as Phloz nodes — pixel IDs, tracking-code installations, conversion-action setup, the relationships to other systems. Verify each one fires by triggering a test event. Set the "verified at" timestamp on each node. Schedule a quarterly verification task on the agency engineer who owns tracking.
The 30 minutes at onboarding catches 90 percent of the tracking issues that would otherwise surface during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.
Frequently asked questions
The three questions agencies ask most often about Phloz's Google Analytics 4 integration. Honest answers — same data we'd give a friend evaluating the integration.
- How often should we audit a client's GA4 setup?
- Quarterly at minimum, monthly during active campaign periods. Phloz lets you set a "verify_at" timestamp on each GA4 property node so the audit becomes a recurring task on whoever owns the tracking-engineering role at your agency.
- Can Phloz import existing GA4 configurations?
- V1 is manual entry — you create the GA4 node and link it to the client. V2 will use the GA4 Admin API to auto-populate property metadata, conversion events, and audience configurations. The V1 manual model is intentional for launch: it forces explicit verification rather than trusting an auto-import.
- How does Phloz handle BigQuery exports?
- BigQuery export is a property-level configuration in GA4. Phloz tracks the export status as part of the GA4 node's metadata (enabled / disabled / pending verification). For agencies running custom BigQuery dashboards, this catches export failures before the dashboard goes blank.
Other integrations
Other analytics and adjacent tools Phloz integrates with.
14 days free · No credit card · Starter tier free forever