Track Google Business Profile Traffic in GA4

To track visits from a Google Business Profile in GA4, add a documented UTM-tagged URL to the profile’s website field, verify the live profile link, and inspect the resulting traffic in GA4’s session-scoped acquisition reports. Measure enquiries with a separate lead event or key event.

This distinction matters for a local-business owner and the web designer maintaining the site: a Google Business Profile website click, a GA4 session, and a completed enquiry are different measurements. They can inform one another, but Google does not provide a rule saying that their totals must match.

What each number means

Business Profile Website clicks: Google defines this as the number of times people clicked the website link on a Business Profile. It is a profile interaction, not a confirmed website session or lead. See Google’s Business Profile performance guidance.
GA4 sessions: A session is a measured visit to the website. GA4 can classify the session using acquisition dimensions such as Session source, Session medium, and Session campaign.
Lead key events: These are tracked business actions, such as a completed enquiry form or a confirmed appointment request, that you have configured as meaningful events in GA4.

Because the measurements come from different systems and represent different stages, do not label every Business Profile click as a lead. A click can end before the site loads, a session can contain no enquiry, and a form submission can still require validation before it becomes a qualified business lead.

Choose the landing page and UTM convention first

Start with the canonical landing page you want visitors to use. It might be the home page, a location page, or a service page. Confirm that the page loads over HTTPS, works on mobile, and is the URL you want customers to see after any redirects.

Document the naming convention before applying it to multiple locations. Use utm_source=google and utm_medium=organic for an unpaid profile website link, and identify the placement with utm_campaign=business_profile. This keeps the medium consistent with standard organic reporting while the campaign separates profile traffic. Existing custom conventions can work, but verify their default or custom channel classification before changing them; changing values also splits reporting rows.

Hypothetical tagging example

https://example.com/?utm_source=google&utm_medium=organic&utm_campaign=business_profile

This is a naming example, not a Google-required standard. A custom medium such as gbp does not automatically mean Unassigned. Google’s default channel rules also consider the source; Unassigned means that no channel rule matched. Check Session default channel group alongside Session source / medium. In this example:

utm_source=google identifies the source.
utm_medium=organic identifies the unpaid acquisition medium.
utm_campaign=business_profile identifies the campaign or placement convention.

Google Analytics documents that UTM parameters on final URLs provide source, medium, campaign, and related traffic-source information. See Google Analytics: About traffic-source dimensions.

Put the tagged URL in the Business Profile

Append the agreed UTM parameters to the canonical landing-page URL.
Open the Business Profile editing interface available to the business.
Enter the complete URL, including https://, in the website field.
Save the change.
Open the public profile in a browser or search result, rather than relying only on the editing screen.
Click the profile’s website link and inspect the final browser URL.

Google’s Business Profile editing guidance says the website field should use a full URL and that Googlebot should not be blocked from accessing the site. The exact interface can vary by account, device, region, or Google product surface, so verify the live link rather than assuming that a saved edit is the end of the process.

The final address should retain the intended UTM query string after redirects. If it does not, inspect the redirect chain, canonicalization rules, link-management tools, and server or WordPress redirects before evaluating the GA4 data.

Find the visits in GA4

Use the Traffic acquisition report for this question. Add or inspect these session-scoped dimensions:

Session source
Session medium
Session campaign
Session source / medium

Look for the values created by your convention, such as google, organic, and business_profile. Google describes these as session-scoped acquisition dimensions in GA4’s Traffic acquisition report guidance. Do not substitute user-acquisition dimensions when the question is how a particular visit began.

The Manual report is also useful when checking whether manually tagged traffic is being classified from the UTM parameters. Google says this report includes manual source, medium, campaign, and related session dimensions when the parameters are successfully collected. See Google Analytics: Manual report.

Session acquisition and event attribution answer different questions. Google’s guidance on attribution and traffic-source dimension scopes distinguishes session-scoped dimensions, which describe how a session began, from event-scoped dimensions used when assigning credit to key events. For this implementation, use Traffic acquisition to inspect the visit, then evaluate the lead event separately.

Measure the enquiry separately

Define the action that represents a meaningful enquiry for the business. Depending on the site, that could be a form completion followed by a real success message, a booking request reaching the business system, or another confirmed contact action.

GA4 Enhanced Measurement can collect form_start and form_submit for supported configurations, but a generic form submission does not automatically mean a qualified, unique, valid, or sales-ready lead. Custom JavaScript, AJAX forms, embedded forms, and unusual success handling may also require specific implementation work.

For a business-relevant action, create or validate a specific event and mark it as a key event when appropriate. Google’s guidance on measuring key events recommends defining the meaningful lead action rather than treating every form interaction as the business outcome. Review the related Enhanced Measurement documentation when deciding whether the built-in form events fit the site.

Verification checklist

Use a controlled test before relying on the report. Start from a fresh browser session in which the site has not already been visited, and record the consent choice. Clicking a tagged link during an existing GA4 session can leave its session source unchanged, so that is not a clean test of session acquisition. See Google’s traffic-source scope example. Then check:

Profile link: Confirm that the public Business Profile website link points to the full tagged URL or to a redirect that preserves the parameters.
Final browser URL: Click the live profile link and inspect the address bar after all redirects. Confirm that the expected utm_source, utm_medium, and utm_campaign values remain.
GA4 collection: Check Realtime for activity from the test visit.
Event details: If using a debug-enabled device, inspect DebugView for events and parameters.
Acquisition row: After processing time, inspect Traffic acquisition and the Manual report for the expected session dimensions.
Lead outcome: Complete a controlled test using the actual business success condition and confirm that the intended lead event or key event was recorded.

Google’s Realtime and DebugView guidance supports implementation checks with recent events and parameters, but cautions that DebugView has limited attribution analysis. Use acquisition reports for historical attribution rather than treating a DebugView observation as the final reporting result.

If the UTM-tagged row is missing

Check the problem in this order:

Test source: Make sure the test began by clicking the live website link on the public Business Profile. A copied untagged URL will not test the profile link.
Redirects: Compare the URL before and after each redirect. A redirect that removes the query string can prevent the intended manual classification.
Consent: Check whether the test device declined analytics consent or whether the consent implementation delayed or prevented the GA4 tag from loading.
Tag loading: Use the site’s tag diagnostics or browser developer tools to check that the GA4 tag is present and fires on the landing page.
Duplicate or missing tags: Look for a missing measurement implementation or multiple conflicting GA4 implementations that could make testing and reporting unreliable.
Report timing: Allow for reporting processing before deciding that the row is absent.

Traffic can also appear as direct or unassigned when source information is unavailable. Google’s documentation on direct traffic and missing traffic-source information lists possible causes including missing parameters, redirects, direct visits, consent or privacy conditions, and blockers. These are diagnostic possibilities, not a diagnosis of any particular discrepancy.

How to report the results

Keep the three measurements in separate columns in the monthly report:

Measurement	Question it answers
Business Profile Website clicks	How many times was the profile website link clicked?
GA4 sessions from the tagged profile URL	How many measured sessions were classified with the profile convention?
Lead key events	How many tracked business actions met the defined lead condition?

Hypothetical example: A report might show 25 Business Profile website clicks, 19 observed GA4 sessions, and 3 lead key events. Those are three separate observations. They do not prove that 22 clicks were lost, and they do not mean that all 19 sessions were prospects. Differences can reflect reporting scope, consent, privacy controls, redirects, blockers, automated activity, tag implementation, and other conditions that require investigation.

The practical goal is not to force the totals to reconcile. It is to make each number answer a clear question, verify the path from the live profile link to the GA4 session, and connect lead events to the business’s actual enquiry process.

Which part of your current measurement is hardest to validate: preserving UTMs through redirects, classifying the session in GA4, or confirming that a form event represents a real enquiry?

Sources

Google Business Profile: Understand your Business Profile performance & insights

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.