Google Brings Business Profile Metrics Into GA4

Google now surfaces Google Business Profile performance metrics natively inside GA4, closing one of the longest-standing blind spots in local analytics. Rolling out in early-to-mid June 2026 — reported variously between June 8 and 10 — the integration pulls seven profile metrics into Google Analytics on a rolling six-month window, with no tags or tracking code required. Calls, direction requests, and bookings that used to vanish the moment they happened on Search or Maps can finally sit beside on-site behavior in one report.

The stakes are practical. For years, the only Business Profile signal that reached an analytics tool was a website click tagged with UTM parameters. Everything else — the phone call from the knowledge panel, the tap on Get Directions, the booking made straight from Maps — generated no analytics event at all. Marketers reported on local performance in one dashboard and web performance in another, then stitched the two together by hand. This integration brings those local signals into the same property as the rest of GA4.

This guide focuses on what is genuinely new — the GA4 integration itself, not another walkthrough of profile optimization. We map each of the seven metrics to buyer intent, spell out exactly what the integration cannot do (campaign-level attribution being the big one), and give agencies a governance playbook for linking, segmenting, and offboarding client accounts without creating a reporting mess.

The integration began rolling out in early-to-mid June 2026. Trade coverage and Google’s own changelog put the launch somewhere between June 8 and 10, and the rollout was gradual — some accounts saw the new option immediately, others waited weeks for it to appear. Rather than pin a single date, treat early-to-mid June as the window.

Once available, linking happens entirely inside GA4: Admin, then Product links, then Google Business Profile links. There are no tags to add and no gtag.js changes; the moment a profile is connected, a Business Profile collection shows up in the Reports menu. You need an Editor or Administrator role on the GA4 property and an Owner or Manager role on the profile — miss either and the link will not complete. Think of it as the measurement layer that every Google Business Profile feature generated but that analytics could never read.

Seven metrics come across: interactions, calls, bookings, directions, website clicks, messages, and menu views. That set is confirmed in Google’s own Help documentation rather than only secondary coverage, so it is safe to treat as fact. One quirk worth knowing — GA4 shows all seven regardless of business type, so a service business will see a menu-views row that always reads zero, where the native profile dashboard would simply hide it.

Run the numbers on what changed and the integration looks more significant than a feature note suggests. Of the seven metrics, exactly one — website clicks — was ever visible to analytics, and only when every profile link carried UTM parameters. The other six were dark. A phone call placed from the knowledge panel, a tap on Get Directions, a booking, a chat message, a menu view: each happened on Google’s surfaces and left no trace in any analytics tool. That is six of seven signals, roughly 86% of the metric types, moving from invisible to reportable in a single release.

For local businesses, those six are often the highest-intent actions a customer takes. Someone who taps to call or asks for directions is far closer to a purchase than someone who clicks through to read more. Losing that data meant local marketers were optimizing against the one low-intent metric they could see while flying blind on the high-intent ones underneath it.

It is part of a wider pattern in GA4 through 2026: Google steadily folding once-siloed data sources into the property, the same way it has been bringing new traffic sources in GA4 from AI assistants into view. The reporting surface is consolidating, even in the places where the underlying attribution is not.

Knowing the seven metrics exist is the easy part. Knowing what each one tells you — and what GA4 still cannot — is where the reporting value lives. The matrix below maps every metric to the offline action it proxies, the campaign type it helps validate, and the specific limitation you inherit when you read it inside GA4. We grouped the rows by buyer intent, because the decision-stage signals are the ones worth watching most closely.

Read top to bottom, the matrix makes the integration’s real job obvious. It is strongest as a consideration-and-decision visibility layer — it tells you that demand is happening — and weakest as an attribution engine. Every row in the limitation column points back to the same two constraints: no per-campaign breakdown and no per-location segmentation. Keep both in view when you build a client report on top of this data.

It is worth being precise about the limits, because the easy headline — that Google has closed the local attribution loop — is wrong. The integration brings local performance metrics into GA4; it does not attribute them to campaigns. There is no campaign-level breakdown anywhere in this data. If direction requests jump during a Local Inventory Ads flight, GA4 will show the jump but cannot tell you the campaign caused it. Tying local actions back to spend still requires store-sales frameworks, geo-lift testing, or manual correlation. This is correlational visibility, not causal attribution.

The analytics consultancy DataClare framed it the same way, calling the link a welcome addition that, at this stage, is better understood as a reporting enhancement than a complete reporting solution. That is the right altitude to set client expectations at. Three structural limits sit underneath the attribution gap:

• Aggregation. You can link several profiles to one property, but GA4 has no dimension to separate them. Ten locations report as one undifferentiated number.
• Standard Reports only. The metrics are locked out of Explorations, comparisons, and custom filters, and they do not flow into subproperties. Custom funnels and cohort analysis cannot include them.
• A short memory. Business Profile data is held on a rolling six-month window, against the 14-month ceiling on standard web events.

That last asymmetry has a direct operational consequence: any year-over-year comparison of local performance has to be built outside GA4. Export the Business Profile metrics to a warehouse like BigQuery before the rolling window drops them, or the data simply will not exist when you need to compare this June to last June. For anything requiring true per-location depth, the GBP Performance API and the native profile dashboard remain the better tools — this integration supplements them, it does not replace them. Reviews, star ratings, photo counts, Q and A, and post engagement are not included either; those stay in the profile dashboard.

For agencies running analytics across a portfolio of local clients, the integration introduces a small governance problem alongside the new data. Because the link can be created by anyone with the right roles, it can quietly appear across analytics, local-SEO, paid-media, and regional teams at once — leaving nobody sure who owns it. A clear playbook avoids that.

This is the kind of measurement plumbing that pays off quietly — it rarely makes a strategy deck, but it is the difference between a local-SEO program you can prove and one you can only assert. It pairs naturally with a broader local SEO strategy for Google Business Profile in 2026 and the GBP strategy after the May 2026 core update, giving both a measurement spine. When we set up local reporting as part of our analytics engagements, this link is now a default step — connected at the root, exported for history, and documented for handover. For clients running local paid media, we wire it into paid media reporting as a demand signal, never as a campaign-attribution source.

The GA4 link did not arrive alone. In the same June 2026 window, Google connected Business Profiles to Gemini for profile management — updating hours, drafting posts, and composing review responses from inside the assistant. It is a separate product surface from the GA4 integration, but together they sketch a clearer shape: GA4 becomes the measurement layer for the profile, and Gemini becomes the management layer. One tells you what is happening; the other helps you act on it.

Step back and the integration reads as another move in Google’s slow consolidation of GA4 into the single place marketers are expected to live. The company has spent 2026 pulling fragmented signals — AI-assistant traffic, and now local profile activity — into one property. The pattern matters more than any single feature: Google is betting that whoever owns the reporting surface shapes how budget gets justified, and it would rather that surface be GA4 than a competitor’s dashboard or a spreadsheet.

Projecting forward, two things look likely. First, the gaps in this first version — no per-location segmentation, no Explorations access, the six-month cap — are exactly the kind Google tends to close in later releases, so the export-to-warehouse workaround should be treated as a stopgap, not a permanent architecture. Second, as more local data lands in GA4, the agencies that win will be the ones who built governance and measurement discipline early, rather than bolting it on after a client asks why two reports disagree. The teams treating this as plumbing today will have clean local reporting when the next data source arrives.

For most local businesses, the practical takeaway is smaller and immediate: link the profile, watch the high-intent metrics you could never see before, and resist the urge to read campaign attribution into numbers that do not carry it. If you want that wired into a defensible local program rather than a one-off report, that is the kind of work our agentic SEO and analytics teams handle end to end.