Does GA4 Now Connect to Google Business Profile? Here Is How to Use It

Google launched a native integration between GA4 and Google Business Profile in June 2026, pulling local interaction data directly into Analytics for the first time. Here is what seven new metrics tell you, how to connect the accounts, and where the limitations will catch you off guard.

For years, running paid search or SEO for a local business meant living across two dashboards. Google Analytics showed you what happened on the website. Google Business Profile showed you what happened before visitors got there: the calls, the direction requests, the clicks from Maps. Those two data sets had no native connection. You pieced the story together manually, or you just ignored the GBP signals entirely.

That gap closed in June 2026. Google launched a native product link between Google Analytics 4 and Google Business Profile, pulling seven local engagement metrics directly into the GA4 interface without any tracking code or tagging required. The data shows up in Standard Reports automatically once the accounts are linked.

It sounds straightforward. And in some ways it is. But there are limitations significant enough that going in blind will cost you time. Here is the full picture.

What Is the GBP + GA4 Integration?

The integration is a product link, similar to how you link Google Ads to GA4. You connect your Google Business Profile account directly to your GA4 property through the Admin panel, and Google automatically begins importing your GBP interaction data on a rolling six-month window. No tags. No Google Tag Manager setup. No custom dimensions needed on your end.

The feature began rolling out in early June 2026 and is available to any GA4 property owner who also manages a Google Business Profile. According to BrightLocal, the same update also introduced the ability to manage GBP listings directly via Gemini, though that is a separate capability from the Analytics integration.

For agencies and in-house teams that have been manually exporting GBP data and cross-referencing it with Analytics sessions, this replaces a lot of copy-paste work with a native data layer you can actually build reports around.

What Data Does It Pull In?

The integration imports seven core interaction metrics from your Google Business Profile. These cover the main ways a user can engage with your listing on Google Search and Maps before they ever reach your website.

Interactions is the aggregate count of all engagements with your listing across Search and Maps. Website Clicks counts the number of times a user clicked through to your site directly from the GBP listing. Calls tracks phone call button taps. Directions counts requests for driving or transit directions to your location. Messages logs conversations started through the GBP messaging feature. Bookings tracks appointment or reservation completions via the booking button. Menus records views of your menu, if applicable to your business type.

These are not new metrics. GBP has reported them inside its own dashboard for years. What is new is that they now sit alongside your web behavior data inside GA4, meaning you can look at listing engagement and on-site behavior in the same interface without switching tools.

How to Set It Up

The setup process is short. Open your GA4 property and go to Admin. Under the Property column, click Product Links, then find Google Business Profile links in the list. Click Link, and follow the prompts to select which Business Profile you want to connect. If you manage multiple profiles, you can link more than one, but read the limitations section before you do that for multi-location accounts.

Once linked, GBP data begins appearing in the Standard Reports section of your GA4 property. Google adds a dedicated section to the left-hand menu panel automatically. The data imports on a rolling basis going back six months from the link date. You will not get historical data beyond that window.

There is no tagging, no custom event setup, and no data stream configuration required. The connection is entirely API-based.

Key Limitations to Know

The integration is genuinely useful, but four constraints will affect how you work with it in practice and you should understand them before building client reports around the data.

Six-month data retention only

GA4 retains GBP interaction data on a strict rolling six-month window. Your standard web event data can be retained for up to 14 months, but local metrics expire faster. If you need historical GBP data beyond six months, you must pull it directly from the GBP dashboard and store it externally before it drops out of GA4.

Multi-location aggregation problem

If you link multiple Google Business Profiles to a single GA4 property, Analytics aggregates all the metrics into one combined dataset. There is no native dimension to break down calls or direction requests by individual location. For a single-location business this does not matter. For a chain with multiple stores, it is a significant gap that forces you to maintain separate GA4 properties per location if you need individual reporting.

No access in Explorations

GBP metrics are locked to the Standard Reports section. You cannot use them in custom Explorations, apply comparison filters, or include them in Looker Studio via the GA4 connector in the usual way. Your analytical depth is limited to whatever GA4’s Standard Reports interface allows. Advanced segmentation is not available for this data.

No subproperty support

The integration is only available for standard GA4 properties. If your analytics architecture uses GA4 subproperties, you cannot link GBP there. The link must go to a primary standard property.

Using It for Local Campaign Reporting

Despite the limitations, the integration adds real value for local campaign reporting if you know what to look at.

The most useful thing it gives you is a correlation layer. You can now look at periods where you increased local search ad spend or pushed a Google Ads local campaign hard, and see whether GBP interactions like calls and direction requests moved in parallel. That correlation was impossible to make inside a single tool before. You had to compare GBP export data to Ads performance manually.

For service businesses running call-based campaigns, the Calls metric from GBP tells you something different than call conversions tracked through Google Ads. GBP Calls counts taps on the phone number from the listing itself, outside of any paid click path. Seeing both together gives you a fuller read on total call volume driven by your local presence versus your paid traffic.

For brick-and-mortar businesses, the Directions metric is a strong local intent signal. A spike in direction requests that correlates with an ad campaign running on local inventory or local service categories is meaningful. You now have one place to see that connection without building a manual bridge.

Teams doing local SEO work can use the same data to track whether organic ranking improvements in Maps and local packs are translating into listing interactions. GBP Interactions rising while paid spend stays flat is a clean signal that organic visibility is improving.

What This Means for Local SEO

This integration matters more for local SEO than it might initially seem. GBP performance has always been a signal that sits at the boundary of SEO and paid: it is shaped by your organic ranking in local packs, but also influenced by your ad presence, your review velocity, and your listing completeness.

Having that data inside GA4 means you can start building a more complete picture of local search performance in one place. When a local SEO campaign pushes a client from position 4 to position 2 in the Maps pack, the impact usually shows up first in direction requests and calls before it shows up in website traffic. This integration gives you a native way to track that signal without relying on GBP alone.

The six-month retention limit is the main frustration from an SEO perspective, because local SEO moves slowly and year-over-year comparisons are often the most meaningful benchmark. The workaround is to export GBP data monthly into a spreadsheet or data warehouse so you preserve the historical record beyond what GA4 keeps.

At Incisive Growth, we have started incorporating GBP interaction data into our local client reporting dashboards since the integration went live. The setup takes about five minutes. The value shows up immediately in client conversations where you no longer have to explain why you are quoting numbers from two different tools.

Frequently Asked Questions