Google Business Profile to GA4: What the New Integration Measures, and What It Still Misses
A current guide to GBP-to-GA4 reporting, aggregate metrics, six-month retention, multi-profile limits, and the downstream evidence it still misses.
Google’s June 2026 Business Profile integration brings local-profile performance metrics into Google Analytics. That is useful: a team can review profile interactions and website behavior in the same product instead of switching dashboards.
It does not join an individual profile interaction to an individual website session, caller, booking, CRM lead, or closed job. The integration exposes aggregate platform telemetry. Lead attribution still requires tagged links, call and booking records, accepted form events, CRM identifiers, and controlled outcome definitions.
This guide explains what the integration measures, the restrictions Google documents, and the additional evidence a service business needs before it labels an interaction as a lead or revenue.
What Google launched—and what it did not
Google documents a direct connection between a Business Profile and an Analytics property. Once linked and populated, Business Profile reporting appears as a dedicated collection in GA4. The purpose is to put profile performance and site behavior closer together for analysis.
The imported values remain aggregate Business Profile metrics. They are not ordinary event rows tied to a GA client ID, session ID, lead ID, or CRM record. That distinction is the central implementation boundary: co-location in GA4 is not the same thing as identity resolution or lead-level attribution.
Read every imported metric by its actual definition
Platform labels often sound closer to a business outcome than they are. Google Business Profile Help defines a call as a click on the call button. A website click is a click on the profile’s website link. A direction request is an interaction with directions. Eligible bookings depend on a supported booking provider.
| Profile metric | What it records | What it does not prove |
|---|---|---|
| Calls | A customer clicked the call button on the profile. | That a call connected, was answered, was qualified, or produced work. |
| Website clicks | A customer clicked the website link on the profile. | That the final page loaded, a GA4 session was collected, or an inquiry occurred. |
| Directions | A customer requested directions under Google’s metric rules. | That the person visited the location or bought a service. |
| Bookings | An eligible booking completed through a supported provider. | Attendance, qualification, collected revenue, or a complete acquisition path. |
| Messages | A count of eligible profile conversations where the feature applies. | Lead fit, response quality, sales outcome, or revenue. |
| Views and searches | Profile exposure under Google’s counting and reporting rules. | A website visit, buyer identity, or incremental demand caused by optimization. |
Account for retention and multi-profile restrictions
Google documents a rolling six months of Business Profile metrics in the integration. That is useful for current operations, but it is not a permanent historical warehouse. Export or store the business-level aggregates needed for longer trend analysis under an approved data-retention policy.
When several profiles are linked, Google combines the metrics. The current documentation does not provide individual-profile segmentation or filtering in custom reports and Explorations. A multi-location business therefore needs its own location identifiers on controllable website links, phone routes, booking paths, and CRM records if it wants location-level outcome analysis.
| Question | Native integration | Additional evidence needed |
|---|---|---|
| How much eligible profile interaction occurred? | Yes, within Google’s metrics and retention window. | Business definitions and historical export if longer retention is required. |
| Which linked profile produced the outcome? | Restricted when profiles are aggregated. | Stable location IDs in tagged links, call routes, booking records, and CRM inquiries. |
| Which website session came from a profile link? | Not a lead-level join. | Consistent UTM tagging and preserved landing/session fields. |
| Which call became qualified? | No. | Call record, inquiry ID, qualification state, and controlled reason code. |
| Which interaction produced revenue? | No. | CRM opportunity relationship and documented revenue basis. |
Configure a usable measurement layer
Record the connected Business Profile account, GA4 property, access roles, number of profiles, connection date, timezone, and expected reporting start. Capture a dated baseline from Business Profile Performance so the team can identify delayed population, missing metrics, or scope differences.
For website and appointment links the business controls, use a documented UTM taxonomy. One workable pattern is utm_source=google, utm_medium=organic, utm_campaign=gbp, a placement value in utm_content, and a stable location key in utm_id. That is an operating convention, not an official Google Business Profile requirement.
- 01
Business Profile telemetry
Google reports aggregate eligible calls, website clicks, bookings, directions, messages, searches, and views. The native integration does not identify the customer or qualified outcome.
- 02
Controlled action paths
Tagged website and booking links, tested call routes, and accepted form or booking events preserve a stable source, placement, and location key without personal data.
- 03
Operational outcomes
An opaque inquiry ID connects accepted contact to qualification, booking, opportunity, and a documented revenue basis inside approved operational systems.
Connection and reporting checklist
- Confirm that the Business Profile and Analytics users have the required access.
- Record the GA4 property, profile group, number of locations, timezone, and link date.
- Capture Business Profile Performance before and after linking for comparison.
- Verify which imported metrics apply to the business; not every metric exists for every profile.
- Document the rolling retention limit and the owner of any longer-term aggregate export.
- Use lowercase, controlled UTM values on profile links the business can edit.
- Preserve campaign parameters through redirects and do not add campaign tags to internal links.
- Keep a link inventory so profile managers and listing tools do not silently replace tagged destinations.
Connect profile telemetry to qualified outcomes outside the integration
Calls need a call record and an inquiry state. Website forms need an accepted server response and one lead event. Booking systems need a completion identifier and cross-domain or provider integration where supported. The CRM needs a separate inquiry object, even when several inquiries belong to the same contact.
Use an opaque inquiry ID and controlled fields for channel, location, service, timestamp, qualification, disqualification reason, owner, opportunity, and outcome. Store first-touch, inquiry-touch, and latest-touch acquisition values separately where known. Keep unmatched and unknown records instead of assigning a source to satisfy a dashboard total.
Selected CRM lifecycle changes can be mirrored into GA4 using recommended events such as generate_lead, working_lead, qualify_lead, disqualify_lead, close_convert_lead, and close_unconvert_lead. The CRM remains the operational source of truth, and any value sent to analytics needs a documented basis.
Run QA against the real contact paths
Implementation QA
- Compare the imported aggregate metrics with the Business Profile Performance surface for the same period.
- Test a tagged profile website link through every redirect into the final GA4 landing session.
- Test the appointment link and prevent a third-party booking domain from becoming a self-referral.
- Place test calls from the profile and website, then distinguish call-button clicks, routed calls, answered calls, and qualified inquiries.
- Submit a valid form and an invalid form; confirm that the lead event fires once only after acceptance.
- Trace each test inquiry into the CRM with location, service, source context, qualification, and owner.
- Confirm that analytics parameters and URLs contain no names, emails, phone numbers, addresses, or free-text messages.
- Document unmatched records, delayed metrics, missing permissions, and profile-level reporting gaps.
- Recheck Google’s integration documentation before publishing a dashboard or operating procedure.
Source ledger
These sources support the operating guidance above. Platform behavior and documentation can change, so volatile implementation details should be rechecked before a rollout.
- Link Business Profile to Analytics — Google Analytics Help. Primary documentation for connection requirements, available metrics, rolling six-month retention, multi-profile aggregation, and reporting restrictions.
- What’s new in Google Analytics — Google Analytics Help. Release log for the June 2026 Business Profile integration and adjacent Analytics reporting changes.
- Understand your Business Profile performance and insights — Google Business Profile Help. Defines calls, website clicks, directions, searches, views, messages, and eligible bookings as Business Profile metrics.
- URL builders: Collect campaign data with custom URLs — Google Analytics Help. Documents UTM parameters, naming consistency, case sensitivity, and acquisition reporting for controllable profile links.
- Recommended events — Google Analytics. Defines lead-lifecycle event names that can complement aggregate profile metrics with website and CRM evidence.
- Measurement Protocol — Google Analytics Help. Explains how server-side and offline events can supplement client collection while preserving identifiers and timing requirements.
The practical next step
Connect one eligible profile and property, record the account roles and connection date, validate the imported metrics against Business Profile Performance, then test one tagged website, call, or booking path through to a qualified CRM inquiry.