Docs

GA4's Business Profile Integration: What to Track

GA4's new Google Business Profile integration links social, GMB, and website data — track it right or double-count the same customer three times.

Analytics

Google rolled the Google Business Profile (GMB) integration into GA4 this month, connecting Instagram content, Business Profile activity, and website data in one place — a connection that previously needed expensive third-party tools to stitch together. For local and multi-location businesses, that’s genuinely useful: it’s the first time these three data sources have shared a native reporting surface. It’s also a fast way to badly overstate acquisition performance if the integration isn’t set up with deduplication in mind, because a single customer can now show up in a Business Profile view, an Instagram click, and a website session — three touchpoints that are easy to count as three separate conversions if nobody’s tracking the overlap.

The risk isn’t the integration itself, it’s what teams do with it in the first few weeks. A Business Profile “call” action, an Instagram profile visit, and a GA4-tracked website session can all belong to the same customer journey, and reporting each one as an independent win inflates every acquisition number downstream — CAC looks better than it is, and channel attribution stops reflecting reality. Get the tracking right and you get a genuinely unified view of local + social + web performance for the first time; get it wrong and you get three dashboards that all look good and don’t agree with revenue.

Data Points to Track

  • Cross-surface session stitching, using GA4’s user-ID or Google Signals where consented, to link Business Profile, Instagram, and website touches from the same customer instead of counting them as separate users
  • Business Profile action type per event — calls, direction requests, website clicks, and message starts — logged distinctly, since they carry very different conversion likelihood
  • Attribution model applied to blended journeys, tracked explicitly (first-touch, last-touch, or data-driven), so cross-surface conversions aren’t silently defaulting to whichever model happens to double-count the most
  • De-duplicated conversion counts, compared against the sum of individual-surface counts, to quantify exactly how much overlap the integration is surfacing
  • Location-level performance, for multi-location businesses, since blended GMB+Instagram+web data is most valuable segmented by physical location rather than aggregated site-wide

Setup Steps

  1. Enable the GA4-Business Profile integration for each verified location and confirm the connection is pulling Business Profile action events, not just profile views.
  2. Turn on Google Signals or an equivalent consented cross-device identifier before relying on cross-surface stitching — without it, the integration reports adjacent data rather than linked journeys.
  3. Build a de-duplication check that compares total blended conversions against the sum of per-surface conversions, and treat a large gap as a signal the stitching isn’t working as expected.
  4. Set one attribution model as the reporting default for blended journeys and document it, so acquisition reports stay comparable across locations and over time.
  5. Segment reporting by location before drawing channel-level conclusions, since a single site-wide view will hide the fact that Instagram might be driving one location and Business Profile calls another.

Actionable Insights

A location where Business Profile calls consistently precede a website conversion is telling you the call is the real decision point — that’s where investment in call tracking and staff response time pays off, not the website. A large gap between de-duplicated and summed conversions is a direct measure of how much of your reported acquisition growth was actually double-counting, and it’s worth restating recent performance once the dedup logic is in place. And if Instagram-sourced Business Profile visits convert well in some locations but not others, that’s a genuine local-marketing signal the blended view surfaces for the first time — not something a single-channel report could have shown you.

Expert help

Need help tracking this in your app?

Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.

Talk to an expert