To track Google Business Profile website traffic and leads in GA4, connect your profile for native interaction reporting, add UTM parameters to the website links you control, and configure events for successful enquiries. Then filter website reports by your GBP campaign. Together, these steps show profile activity, recorded visits and measurable lead actions without treating them as interchangeable results.
At Google My Business Service, we encourage businesses to connect profile improvements with useful customer actions. More website clicks can be encouraging, but the more useful question is whether those visits lead to relevant enquiries.
This guide explains the setup, the reports to use and the checks that keep your numbers meaningful. Product instructions were checked against the linked Google documentation on 30 October 2026.
Key takeaways
- Understand what each tool measures
- Step 1 — Connect your profile to GA4
- Step 2 — Tag the right links
- Step 3 — Read the right website report
- Step 4 — Define and track useful leads
- Test the complete journey
- Explain differences before fixing them
- Review results and choose an improvement
- Use the FAQs to resolve common concerns
- Choose support that matches the problem
What can GA4 tell you about Google Business Profile traffic and leads?
GA4 can help you review profile interactions, identify website activity associated with tagged profile links and measure configured website outcomes. It cannot turn every call click into a qualified lead or every direction request into a store visit. To understand business value, compare analytics with the forms, bookings and customer records your team actually receives.
Use these measurement layers:
| Layer | What to review | What it does not establish |
|---|---|---|
| Activity on Google | Profile website clicks, call-button clicks and other relevant interactions | A successful website visit, answered call or sale |
| Website activity | Recorded sessions and behavior associated with your GBP campaign | Every person who clicked the profile |
| Website outcomes | Confirmed enquiries or completed bookings | Whether each enquiry is qualified |
| Business results | Valid leads, attended appointments, customers and revenue | A perfectly observable journey for every customer |
If you are new to the platform, start with our beginner’s guide to Google Business Profile.
Step 1: How do you connect Google Business Profile to GA4?
Connect the accounts from the GA4 property’s Admin area using Google Business Profile links under Product links. Google requires Editor or Administrator access in Analytics and Owner or Manager access to the profile. Select the intended business profiles, review the sharing information and confirm the connection. Check that you are linking the correct property before proceeding.
Follow Google’s account-linking instructions:
- Open the correct GA4 property and select Admin.
- Under Product links, select Google Business Profile links.
- Select Link and choose the profiles you manage.
- Review the information and confirm.
The dedicated GBP collection reports aggregated interactions, website clicks, calls, directions, messages, bookings and menus. Google documents a six-month window, combined totals for multiple profiles and restrictions on explorations, comparisons and filtering. Some displayed metrics may not apply to your business. See the integration’s reporting limits.
If the option is absent, check the selected property and account permissions, then consult current support guidance. Continue with UTM tagging and website tracking while resolving the link issue. Native linking is not a prerequisite for that website workflow.
Step 2: How should you add UTM parameters to GBP links?
Add UTM parameters to the actual destination URLs you control in your profile. Use a consistent source and medium, a campaign identifying the profile or branch, and a content label identifying the link placement. The tags help GA4 classify recorded website activity. They do not install Analytics or independently verify that someone became a customer.
A practical convention is:
| Parameter | Example | Purpose |
|---|---|---|
utm_source | google | Keep the source recognizable |
utm_medium | organic | Describe the unpaid placement |
utm_campaign | gbp_main | Identify the profile or location |
utm_content | website | Identify the link placement |
This is a recommended house convention, not a mandatory Google naming format. Google explains the underlying fields in its campaign URL guide.
For example, a tagged homepage URL would be:
https://googlemybusinessservice.com/?utm_source=google&utm_medium=organic&utm_campaign=gbp_main&utm_content=websiteFor a supported profile post linking to the optimization page, the example becomes:
https://googlemybusinessservice.com/google-my-business-optimization-service/?utm_source=google&utm_medium=organic&utm_campaign=gbp_main&utm_content=post_optimizationThese examples illustrate the structure; they do not confirm that either link is installed on a live profile.
Keep locations and placements consistent
| Placement | Campaign | Content |
|---|---|---|
| Main profile website | gbp_main | website |
| Main profile appointment link | gbp_main | appointment |
| Main profile update | gbp_main | post_autumn_offer |
| Second branch website | gbp_branch_02 | website |
Only tag supported fields where you control a valid destination. For action links such as booking or ordering, use a dedicated page that allows that action. Google’s business-link policies prohibit shorteners in those fields and require accessible, working destinations.
Use lowercase values, avoid spaces and preserve existing functional query parameters. Add ? before the first query parameter and & for additional parameters. If the URL has a fragment such as #booking, place query parameters before the fragment.
Do not add campaign UTMs to links between pages on your own website. Keep the tags for incoming marketing links so internal navigation does not muddy acquisition data.
Does google_maps prove a click came from Maps?
No. A UTM source is a label you assign. If the same tagged profile URL appears on Google Search and Maps, changing its source to google_maps does not detect which surface the visitor used. Describe the campaign as GBP website traffic and use supported profile reporting for available platform-level insights.
Step 3: Where do you find GBP website traffic in GA4?
Open Traffic acquisition and filter by the GBP campaign values you chose. Review session-scoped dimensions alongside sessions, engagement and the relevant key event. Do not isolate GBP using only google / organic, because that row can include ordinary Google website search traffic. The campaign condition identifies activity associated with your tagged profile links.
Start with this report:
- Open Reports → Acquisition → Traffic acquisition, where that navigation is available.
- Change the primary dimension to Session campaign.
- Filter for your campaign, such as an exact match for
gbp_main. - Add Session source / medium as a secondary dimension if available.
- Review Sessions, Engaged sessions, Key events and Session key event rate.
- Select your enquiry event in the key-event selector where supported.
For several branches, use a consistently defined set of campaigns, such as names beginning with gbp_. A broad “contains gbp” filter is less reliable if unrelated campaigns also contain those letters.
Google’s Traffic acquisition documentation explains the report. Menus vary between properties; an Editor can restore a missing report through the reporting Library.
Compare specific links in an exploration
For a website-only breakdown, create a free-form exploration using:
- Dimensions: Session campaign, Session source / medium, Session manual ad content, and Landing page + query string.
- Metrics: Sessions, Engaged sessions, and Key events.
- Filter: Include the documented GBP campaign or campaign set.
Session manual ad content corresponds to utm_content, so it can distinguish tagged placements. These dimensions concern website activity; they do not remove the restrictions on imported native GBP metrics. See Google’s traffic-source dimension reference.
Keep an all-session acquisition table separate from an event-specific detail table. Filtering the entire table to a lead event can remove non-lead activity and make a calculated rate misleading.
Step 4: How do you track leads from GBP website visits?
Define the business outcome first, then configure a GA4 event that fires when that outcome happens. For an enquiry form, use confirmed successful submission rather than a button click. Track contact clicks separately from received enquiries, and mark the appropriate outcome as a key event. Finally, assess it within your GBP campaign’s website reporting.
A useful event plan is:
| Action | Suggested event | What the event proves |
|---|---|---|
| Confirmed sales-enquiry form | generate_lead | A successful enquiry submission was detected |
| Website phone link clicked | phone_click | Someone tapped a phone link |
| Website WhatsApp link clicked | whatsapp_click | Someone opened the contact route |
| Website Telegram link clicked | telegram_click | Someone opened that contact route |
| Booking completion confirmed | appointment_booked | The booking system confirmed a reservation |
| Payment successfully recorded | purchase | A purchase event was implemented and received |
generate_lead and purchase are Google-recommended events. The contact-click and appointment names above are proposed custom events. They require implementation; Google does not create them automatically because you use these names. Consult Google’s event reference.
Track a successful form
For WordPress forms such as WPForms or Elementor forms, choose a success signal that matches the actual implementation:
- A reliable success callback or integration that sends one event after acceptance.
- A dedicated confirmation page reached after successful submission, with controls against direct visits and refresh duplicates.
- A developer-provided success event passed to Google Tag Manager.
Enhanced measurement can collect form_start and form_submit, but test the actual form before treating either as a valid enquiry. They do not replace checking whether the business received the submission. Google explains automatic form interactions here.
For a confirmation-page setup, match the confirmed page path exactly rather than matching any URL containing “thank”. Trigger the lead event only through the validated success flow. Test that an error message produces no lead event and that refreshing the confirmation does not create another accepted lead.
Track contact clicks without overstating them
In Google Tag Manager, a Just Links trigger can identify HTML links. For a phone link, use a condition such as Click URL starts with tel:, then fire a GA4 event named phone_click to the correct destination. Enable the relevant built-in click variable and test in Preview before publishing. See Google’s click-trigger guidance.
Apply the same principle to the website’s actual WhatsApp or Telegram link format. Use a channel label such as contact_method=whatsapp; avoid sending message text or private contact details. Review existing automatic or plugin tracking so one click does not trigger several equivalent events.
A WhatsApp click does not confirm a message was sent. A phone click does not establish an answered call. Keep these as contact-intent measures, with confirmed conversations and qualification recorded separately.
Mark the right event as a key event
After validating collection, go to Admin → Data display → Events and mark the successful lead event as a key event using the available control. Google documents the process in Mark events as key events. Marking is not retroactive, so do this before the reporting period you want to assess.
If contact clicks are also key events, select the successful enquiry event when evaluating lead performance. Otherwise, an aggregate count may combine several actions from one person.
Handle booking systems and revenue carefully
If a booking journey crosses onto another domain, completed-booking measurement needs support from that provider. Where both domains can use the same GA4 setup, correctly configured cross-domain measurement can preserve the journey. Otherwise, use supported confirmation integrations or operational records. An outbound booking click alone is not a completion.
Giving a form enquiry an estimated value does not make that amount appear as purchase revenue. Report actual sales through the appropriate commerce implementation or your customer records. Google explains that ecommerce events require configuration; installing GA4 alone does not measure payment completion.
How do you test GBP traffic and lead tracking?
Test the entire journey from the tagged destination to the completed outcome. Confirm that the right page loads, the expected event fires once and the enquiry reaches the receiving system. Then inspect the processed campaign report. A functioning tag or visible button alone does not prove that attribution and lead collection work together.
Use this acceptance checklist:
- Open a controlled tagged test URL in a fresh browser context, respecting the site’s consent choices.
- Check that redirects preserve the campaign information until Analytics can read it.
- Confirm the correct property receives the page activity.
- Use Tag Assistant Preview and GA4 DebugView to inspect the event and safe parameters.
- Submit a valid test enquiry and confirm receipt in the actual inbox or form system.
- Test an invalid submission, repeated clicks and confirmation-page refreshes.
- Check the GBP campaign in processed reports, and document how test records are excluded from operational totals.
Google’s DebugView guide explains how to enable debugging. Developer or internal-traffic filters may intentionally keep tests out of standard reports, so inspect those settings before diagnosing missing test sessions.
Many reports can take 24–48 hours to process. Realtime and DebugView are better initial checks, but they do not replace reviewing the final acquisition report. See Google’s data-freshness guidance.
Never send customer names, email addresses, private phone numbers or form answers through UTMs or ordinary GA4 event parameters. Google’s PII guidance explains the restriction.
Why do GBP website clicks and GA4 sessions differ?
GBP website clicks and GA4 sessions measure different things, so their totals should not be expected to match. Someone can click more than once, leave before tracking loads or decline analytics cookies. Redirects, blockers, existing sessions and differing report settings can also affect recorded activity. Investigate unusual changes rather than assuming every difference signals an error.
Check these possibilities:
| Symptom | First checks |
|---|---|
| Profile clicks rise but campaign sessions disappear | Final URL, redirects, tag installation, consent and date range |
| Campaign appears under an unexpected channel | Source/medium spelling and the property’s channel definitions |
Campaign is missing or (not set) | Published link, complete tags, collection and processing time |
| Contact clicks rise but enquiries do not | Link destination, form success, response process and mobile usability |
| Leads appear to come from a booking provider | Cross-domain setup and provider integration |
| Event count is unexpectedly high | Duplicate tags, repeated triggers and confirmation refreshes |
UTM labels describe the link, not a verified identity. A copied tagged URL can produce campaign-labelled activity elsewhere. Treat the report as measured campaign activity with known limitations.
If recorded website activity drops, first confirm that the public profile and website link work. When the profile itself is missing, use our guide to why your business is not showing on Google Maps.
What should you review in a monthly GBP report?
Review profile activity, tagged website sessions, confirmed enquiries and qualified business outcomes for comparable periods. Record changes that could affect interpretation, including campaigns, website edits and tracking adjustments. The goal is to identify the weakest stage of the customer journey and choose a useful improvement, rather than report a larger number without explaining its business meaning.
| Measure | Useful question |
|---|---|
| Relevant native profile interactions | Are customers using different ways to contact us? |
| Tagged website sessions | Are recorded visits through our profile links changing? |
| Sessions with successful enquiries | Are those visits producing the intended outcome? |
| Qualified leads in business records | Are the enquiries relevant to our services? |
| Customers and actual sales | Are qualified enquiries becoming business? |
For example, suppose 200 recorded GBP campaign sessions include 12 sessions with a successful enquiry:
Session enquiry rate = 12 ÷ 200 × 100 = 6%This is an illustrative calculation, not a client result. If those sessions contain 15 submission events, the event count is 15 but the session-based rate remains 6%. Use the count of sessions containing the selected outcome, consistent with Google’s session key event rate definition.
If four of the enquiries become qualified opportunities, record that separately. Do not add form submissions, WhatsApp clicks and profile call clicks together and call the total “unique leads”.
Compare equal periods and note holidays, promotions and website changes. Preserve dated profile performance records separately if you need a longer historical series. Review the Google Business Profile optimization checklist when results suggest inaccurate details, weak presentation or broken customer-action links.
If an agency prepares the report, ask it to distinguish completed work, observed changes and confirmed outcomes. Our guide to choosing a Google Business Profile service provider explains what useful reporting should show.
Frequently asked questions
Yes, when you want a consistent label for website activity through the profile links you control. The native connection and website campaign tagging answer different questions. Add properly configured lead events if you also want to measure what visitors do after reaching the site.
The linked profile reporting includes call-button activity. It does not establish whether a call connected, was answered or produced a qualified enquiry. Those outcomes require suitable call records or another supported measurement process. Website phone-click tracking is a separate measure.
Not reliably when the same tagged profile link appears on both. A manually chosen source name labels that URL; it does not detect the Google surface. Avoid describing every session tagged google_maps as independently verified Maps traffic.
New tags do not rewrite past visits. You can review existing historical data, but you cannot reliably assign all previously unlabelled Google organic or direct sessions to GBP. Record when the new naming system began so comparisons remain understandable.
Tracking tags are measurement tools, not a ranking improvement by themselves. Their practical value is helping you identify which journeys produce useful outcomes and where customers encounter problems. A clearer destination and working enquiry process benefit customers regardless of the reporting label.
No. A campaign label identifies the tagged route; it does not reveal the search query behind each person. Use available GBP discovery information and Search Console’s aggregated website search data as supporting context, without claiming a complete keyword-to-customer record.
Turn your GBP reporting into useful improvements
Start with one consistent campaign convention and one dependable enquiry event. Test the complete journey, then review whether recorded visitors become relevant enquiries. Expand the setup only when another measurement will help you make a decision.
If the findings reveal gaps in your active profile’s information or presentation, explore our Google Business Profile optimization service. It includes one month of profile optimization and a completion report. If your eligible business needs a new profile, review our new-profile setup service.
Confirm custom GA4, GTM, booking and CRM implementation requirements separately before commissioning that work.
