Why model Google Business Profile in a tracking map?

Because for local clients it drives a large share of real conversions (calls, directions, clicks) and it lives entirely outside the website, so a tag-and-pixel tracking setup ignores it. Recording the profile next to the map — its ID on the Accounts card, and optionally a custom node with its website link, NAP, and call path — means local visibility is verified alongside everything else, not assumed-fine until rankings drop.

How do I attribute traffic and calls from the profile?

Tag the profile's website link with UTMs so GA4 attributes the clicks to the profile instead of bucketing them as organic/direct, and route profile calls through call tracking (carefully, to preserve NAP consistency). On the Phloz map, a custom node for the profile linked to the call-tracking node documents that attribution path instead of leaving it improvised.

Does Phloz manage or post to Google Business Profile?

No — Phloz is the agency's tracking and delivery layer, not a GBP posting tool, and it has no Business Profile connection. It records the profile ID and the GA4 link; anything more goes on a custom node or in notes. Posting and review management stay in the agency's dedicated local tools.

Local

Google Business Profile integration for digital marketing agencies

For local and multi-location clients, the Google Business Profile is often the single highest-leverage marketing asset — it drives the map pack, calls, and direction requests that turn into walk-ins. It's also outside the website, so it falls through the cracks of a tracking setup built around tags and pixels: the website link goes untagged, calls from the profile aren't attributed, and a suspension can go unnoticed for weeks. Recording the profile on the client's record — and, where you want it on the map, as a custom node linked to call tracking and the website — puts local visibility next to the rest of the client's tracking, where it can be verified.

How Phloz models Google Business Profile

What Phloz records about Google Business Profile 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.

No Business Profile node type: the profile's ID lives on the client's Accounts card, and the GA4 property node records whether Business Profile is linked
Optionally, a custom node for the profile, linked to the call-tracking node and the website, with the UTM-tagged website link and NAP notes on it
A place to record NAP (name / address / phone) consistency, the single biggest local-ranking hygiene factor across the profile + citations
No Business Profile data: Phloz can't see verification, suspensions, or reviews — those stay in Business Profile

Common Google Business Profile configuration gotchas

The configuration mistakes agencies most often make with Google Business Profile, 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.

Untagged website link: the profile's website button sends traffic that GA4 buckets as organic or direct unless the link is UTM-tagged. Tag it (e.g. utm_source=google&utm_medium=gbp) so profile-driven traffic is actually attributable.
NAP inconsistency: a phone number or address that differs between the profile, the website, and local citations erodes local ranking — and call-tracking number swaps are a common culprit. Keep the canonical NAP stable and consistent everywhere.
Silent suspensions / unverified edits: profiles get suspended or have edits reverted by Google without an obvious alert, quietly tanking map-pack visibility. A recurring check on the profile catches it before the client's calls dry up.

At launch (V1)

There is no Business Profile node and no Business Profile connection. What Phloz records: the profile or location ID on the client's Accounts card, and on the GA4 property node whether Business Profile is linked and which location. Verification status, category, and the tagged website link go in notes — or on a custom node for the profile.

Not built yet

Read-only sync via the Business Profile API: surface verification + suspension status and review velocity in 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 Google Business Profile 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 Google Business Profile 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 Google Business Profile 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 Google Business Profile integration. Honest answers — same data we'd give a friend evaluating the integration.

Why model Google Business Profile in a tracking map?: Because for local clients it drives a large share of real conversions (calls, directions, clicks) and it lives entirely outside the website, so a tag-and-pixel tracking setup ignores it. Recording the profile next to the map — its ID on the Accounts card, and optionally a custom node with its website link, NAP, and call path — means local visibility is verified alongside everything else, not assumed-fine until rankings drop.
How do I attribute traffic and calls from the profile?: Tag the profile's website link with UTMs so GA4 attributes the clicks to the profile instead of bucketing them as organic/direct, and route profile calls through call tracking (carefully, to preserve NAP consistency). On the Phloz map, a custom node for the profile linked to the call-tracking node documents that attribution path instead of leaving it improvised.
Does Phloz manage or post to Google Business Profile?: No — Phloz is the agency's tracking and delivery layer, not a GBP posting tool, and it has no Business Profile connection. It records the profile ID and the GA4 link; anything more goes on a custom node or in notes. Posting and review management stay in the agency's dedicated local tools.

Other local 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