Local visibility
Track Business Profile Website Visits with UTM Links
Create a consistent tagged website link, test redirects, and interpret Analytics attribution without confusing visits with customers.
A tagged website link helps distinguish visits that arrive through a specific link on your Business Profile. It does not identify every customer who saw your listing, and it cannot measure phone calls by itself. Use it as one part of your attribution setup.
Choose a naming convention before editing
Google Analytics supports campaign parameters such as source, medium, and campaign. Consistent names make reports easier to compare. Decide the convention once and record it for everyone managing the profile. Google Analytics URL guidance.
An illustrative link is:
https://example.com/services/?utm_source=google&utm_medium=organic&utm_campaign=business_profile&utm_content=main_location
Replace the example domain and location label with your real destination and approved naming. These values are a suggested convention, not Google's mandatory labels. Keep spelling and capitalization stable so you do not create several reporting rows for the same source.
Tag the link, not the customer
Use a nonpersonal branch identifier when you need to distinguish locations. Do not put names, emails, phone numbers, or job addresses in URL parameters. The tag should describe the marketing placement, not the person clicking it.
If the destination already has a question mark and parameters, append additional parameters correctly instead of adding a second question mark. Use a URL builder or have the site administrator validate the final link. Save the original website URL before updating the profile.
Test the complete destination
Open the tagged link on mobile and desktop. Confirm the expected service or location page loads and that redirects preserve the parameters where needed. Check that the visitor can still call or submit a request. A tracking label is not worth breaking the customer journey.
With the site's analytics configured and the applicable consent choice made, inspect an appropriate test view or report to see whether the source information is captured. Test traffic, reporting delays, consent choices, and blockers can affect what appears. Do not expect every profile click to match a recorded analytics session one for one.
Read the result at the correct scope
Select the intended date range and acquisition dimension in Analytics. Session-level traffic and first-user acquisition answer different questions. Keep the report definition fixed when comparing periods, and document the date you added or changed tagging.
Connect visits to separately configured inquiry events or business records only when that measurement is available. A session does not automatically mean a new customer, and a submitted form does not automatically mean a booked job.
Frequently asked questions
### Will UTM tags improve my rankings? They are measurement labels, not a ranking tactic.
### Should every internal website link use UTM tags? Do not apply this campaign convention indiscriminately to internal navigation. This workflow is for identifying the external profile placement.
### What should I document? The original URL, final tagged URL, naming convention, edit date, tested destination, and report used to evaluate it.
Sources and further reading
Continue with this related guide
Reviewed September 5, 2026. Practical examples are illustrative, not client results.