Google’s “What’s new in Google Analytics” log, updated June 8, records a change that has been surfacing in GA4 Admin panels this week: properties can now link directly to Google Business Profiles and pull local interaction data into a dedicated reporting collection. For brands managing a physical presence alongside a website, it is the first time call counts, direction requests, and booking activity can sit in the same GA4 view as web sessions, with no tagging work required. The gap it closes is real. The gap it leaves open is larger.
What does the GA4 Business Profile link do?
Linking a GA4 property to a Google Business Profile creates a dedicated reporting collection in the GA4 Reports menu, surfacing seven Business Profile metrics: interactions, calls, bookings, directions, website clicks, messages, and menus. Data appears on a rolling 6-month window, shorter than GA4’s standard retention period. Setup is admin-only via the Product Links section of GA4 Admin and requires Editor or Administrator access on the property plus Owner or Manager status on the Business Profile. No tags, no code changes, roughly five minutes.
That citable summary covers what Google’s copy actually promises: centralized reporting. Google describes the feature as the ability to “centrally report on your local business, website, and app metrics,” not to attribute them. The distinction is worth holding onto before any planning conversations begin.
The rollout is gradual and account-by-account. If the Product Links option for Google Business Profile is not yet visible in your Admin panel, it has not reached your property. Check again next week before filing a support ticket.
The reporting gain and the attribution gap
Here is what the link actually delivers: a single place to observe local engagement alongside web behavior. A retailer can now open GA4 on a Monday morning and see that direction requests spiked on Saturday alongside a corresponding rise in product-page sessions. Without this link, that comparison required exporting Business Profile Insights separately and matching dates by hand. The consolidation is a genuine quality-of-life improvement for local marketing teams.
Here is what the link does not deliver: causal connection. A spike in direction requests during a Local Inventory Ads flight cannot be tied to that campaign through this link. The Business Profile metrics land in GA4 as a reporting layer. They are not part of GA4’s attribution models, so they cannot link a local action back to the campaign or channel that drove it. You can see the numbers together. You cannot explain the relationship between them from inside GA4 alone.
This is not a criticism of the feature: it is a framing correction. Teams that have been manually reconciling Business Profile Insights exports with GA4 session data will immediately benefit. Teams hoping the link solves local-campaign ROI measurement will need to keep their existing offline-conversion or store-visit measurement setup. Those are different problems, and this feature addresses only the first one.
The framing also matters for reporting to stakeholders. “We can now see calls and direction requests in GA4” is accurate. “We can now measure the impact of our campaigns on store visits” is not what this link provides, and saying so will create expectations the data cannot support. If your team runs local campaigns and needs ads-data control clarity, the GA4 consent and ad_storage configuration is the more foundational layer to have locked down first.
Setup and data scope
The five-minute setup described in trade walkthroughs is accurate for a straightforward single-property, single-profile link. Multi-location businesses with one Business Profile per location and multiple GA4 properties will need to work through the linkages one at a time. No bulk-link interface has surfaced in the walkthroughs so far.
The seven metrics (interactions, calls, bookings, directions, website clicks, messages, and menus) come directly from Business Profile, not from GA4 measurement. They are not session-based events. They are unlikely to behave like GA4 event data in Explorations. They surface in the dedicated collection Google creates at link time, which makes them useful for at-a-glance monitoring rather than deep behavioral analysis. A detailed walkthrough from Digital Applied covers the collection layout and expected latency for each metric type.
The 6-month rolling window also deserves a note in any handoff to clients or internal stakeholders. If your standard reporting cadence uses annual comparisons, the Business Profile data in GA4 will not support them. Year-over-year direction request trends will still require a separate Business Profile Insights export or a third-party connector.
Google’s June batch also covered the AI Assistant acquisition channel additions in GA4, which reorganized how ChatGPT, Gemini, and Claude traffic appears in acquisition reports, another case of Google applying a default reporting change without per-account configuration. The Business Profile link follows a similar pattern: new data in a standard location, no implementation required. The full Google Analytics release notes document both alongside the June 11 Source Group update for those tracking the pace of change this month.