Tracking GBP Traffic in GA4
UTM parameters help separate Business Profile website sessions from broader organic search traffic. A consistent naming convention is more valuable than a complicated dashboard built on inconsistent tags.
UTM parameters make the GBP website link easier to identify inside GA4, but they are only one piece of local lead attribution. The profile-to-website measurement framework is explained in our Miami GBP analytics guide.
Tracking GBP Website Traffic With UTM Parameters
| Field | Example convention | Purpose |
|---|---|---|
| utm_source | Keeps the platform source consistent | |
| utm_medium | organic or a documented GBP-specific convention | Separates the traffic class in reporting |
| utm_campaign | gbp or location-specific campaign name | Groups Business Profile website sessions |
| Location identifier | A stable location slug or code when needed | Separates multi-location profiles without renaming campaigns |
Where UTM Tracking Stops
UTM parameters describe website sessions after a customer clicks the profile’s website link. They do not measure a direct profile call, and they do not tell you whether a website visitor became a qualified customer without additional conversion or CRM data.
YSH Pro Tip: Document one UTM convention and reuse it across every location.
Use a Stable UTM Convention for the Profile Link
Choose a simple naming convention and keep it stable so GBP sessions do not fragment across several source or campaign labels. The exact naming is less important than consistency. After the tagged link is live, validate that GA4 receives the expected source and campaign values and that important form, booking, or phone-click events are firing correctly on those sessions.
UTMs do not measure profile call-button clicks, because those calls can happen without a website session. GBP Performance remains the source for profile interactions such as calls and website clicks, while GA4 describes what happens after a user reaches the website. A call-tracking or CRM layer may be needed to connect those paths with qualified outcomes.
- Use one stable source and medium convention for GBP.
- Validate tagged sessions in GA4 after the change.
- Keep profile interactions separate from on-site events.
- Avoid adding totals from different systems without checking overlap.
For multi-location profiles, decide whether the campaign value will identify the location, the GBP program, or both, and keep that rule stable. Avoid creating a new campaign name every time the profile is edited. In GA4, validate that tagged sessions still preserve attribution when users move into booking tools, forms, or other domains. A clean convention should survive staff changes and reporting rebuilds without requiring someone to decode old labels.
GBP-to-GA4 measurement inside our local SEO service keeps profile sessions, website actions, phone outcomes, and qualified leads connected while preserving the different definitions used by each system. That separation makes it easier to spot whether a reporting gap belongs to the profile link, the website session, the phone path, or the CRM handoff.
Miami Scenario: Profile Click to Website Lead
A three-location business uses consistent location-specific campaign values, allowing GA4 to show which profile sent the visit and whether the session produced a form, phone click or booking.
Validate GBP UTM Tracking End to End
After adding the tagged website URL, open the profile from a clean browser session, click through, and confirm the session appears in GA4 with the intended source, medium, and campaign values. Trigger the important on-site actions and make sure they are recorded. If the site crosses into a scheduler or another domain, verify that attribution is not lost during that transition.
Document the convention so future profile edits do not introduce a second spelling or campaign name. Stable UTMs are boring by design. Their value comes from creating a durable reporting series that can be compared month over month without cleaning inconsistent labels every time.
Build One Local Reporting View From Several Sources
Combine GBP views and interactions with GA4 sessions and conversions, then add phone or CRM outcomes where available. Each system should keep its own definition. The reporting layer can connect them, but it should not pretend a website click, a call-button click, and a qualified lead are the same event.
The GBP UTM Rule
A clean GBP UTM convention makes website traffic from Business Profiles easier to analyze in GA4. Keep the naming stable, validate it end to end, and combine it with GBP interaction metrics and business-side call or CRM outcomes. UTMs identify the website session; they do not replace the rest of the attribution system.
Ready to stop guessing
and start growing?
One focused conversation. We will show you exactly where your growth is being blocked and how to fix it.