Which clients actually need call tracking?

Service and lead-gen businesses where customers call to convert — home services, healthcare, legal, automotive, local — where the phone is often the primary or highest-value conversion. For pure ecommerce with on-site checkout it's usually irrelevant. Phloz models it as a real node so, for the clients that need it, call attribution is auditable alongside every other source.

How does a tracked call become a Google Ads conversion?

The call-tracking tool records the call and its source, then pushes it to Google Ads as a conversion — frequently via offline conversion import keyed on the click ID — so the campaign that drove the call gets credit and Smart Bidding can optimise for it. The fragile parts are DNI firing correctly and the conversion hand-off actually completing; Phloz makes both a documented, verifiable part of the map.

Does Phloz integrate with CallRail or Invoca directly?

No. Phloz models the provider (CallRail / CallTrackingMetrics / Invoca / WhatConverts / …) as a tracked node — the agency documents the account, DNI status, and the path into GA4 / Google Ads, and verifies it on a cadence. The value is knowing the phone channel is tracked and attributing, not another reporting screen.

Call tracking

Call tracking integration for digital marketing agencies

For service, lead-gen, home-services, healthcare, legal, and local clients, the phone is frequently the highest-value conversion — and the one most agencies leave off the tracking map entirely. Call tracking attributes inbound calls back to the campaign that drove them via Dynamic Number Insertion, then feeds those calls into GA4 and Google Ads as conversions. An agency that doesn't model the call-tracking path is optimising on a fraction of the real conversions, and won't notice when a redesign or a caching change silently breaks number insertion.

How Phloz models Call tracking

What Phloz records about Call tracking on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

Call-tracking provider as a typed node with the account ID, DNI on/off, tracking-number pool size, and health status
Graph relationships: edges into the GA4 property and Google Ads account showing the call → conversion path (reports_conversions_to)
The DNI setup documented on the node with a last-verified date — the audit flags it after 30 days without a check, so re-verifying number insertion is a routine rather than something discovered when calls stop attributing
Per-client visibility: the provider in use and whether attribution is wired through to the ad platforms — the audit flags call tracking with no conversion path recorded

Common Call tracking configuration gotchas

The configuration mistakes agencies most often make with Call tracking, 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.

DNI broken by caching: number-insertion runs client-side, so aggressive page caching or a CDN can serve a stale (or the wrong) number, breaking attribution silently. Re-verify DNI fires after any site, theme, or caching change.
NAP inconsistency hurts local SEO: swapping the displayed phone number for every visitor can fracture the business's NAP (name/address/phone) consistency that Google Business Profile and local citations depend on. Keep the canonical number stable for SEO/GBP and only swap for paid/identifiable sources.
Calls never reach the ad platform: capturing a tracked call is only half the value — if the call isn't pushed back to Google Ads as a conversion (often via offline import), bidding never learns from it. Verify the call → conversion hand-off end to end, not just that calls are recorded.

At launch (V1)

The call-tracking provider (CallRail, CallTrackingMetrics, Invoca, …) appears as a typed node with its account ID, Dynamic Number Insertion (DNI) status, number-pool size, and health status — connected to the GA4 / Google Ads nodes it feeds.

Not built yet

Read-only verification via the provider's API: confirm DNI is live and calls are flowing into GA4 / Google Ads as conversions.

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 Call tracking recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's Call tracking setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Call tracking configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues 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 Call tracking integration. Honest answers — same data we'd give a friend evaluating the integration.

Which clients actually need call tracking?: Service and lead-gen businesses where customers call to convert — home services, healthcare, legal, automotive, local — where the phone is often the primary or highest-value conversion. For pure ecommerce with on-site checkout it's usually irrelevant. Phloz models it as a real node so, for the clients that need it, call attribution is auditable alongside every other source.
How does a tracked call become a Google Ads conversion?: The call-tracking tool records the call and its source, then pushes it to Google Ads as a conversion — frequently via offline conversion import keyed on the click ID — so the campaign that drove the call gets credit and Smart Bidding can optimise for it. The fragile parts are DNI firing correctly and the conversion hand-off actually completing; Phloz makes both a documented, verifiable part of the map.
Does Phloz integrate with CallRail or Invoca directly?: No. Phloz models the provider (CallRail / CallTrackingMetrics / Invoca / WhatConverts / …) as a tracked node — the agency documents the account, DNI status, and the path into GA4 / Google Ads, and verifies it on a cadence. The value is knowing the phone channel is tracked and attributing, not another reporting screen.

Other call tracking and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever