Google Analytics setup for a local service business has five parts: create a Google Analytics 4 property, add a web data stream, install the Google tag, mark the actions that matter as key events, and check that data is arriving. This guide is for owners and office managers in the Twin Cities East Metro, the St. Croix Valley and western Wisconsin who want to know which pages and sources lead to calls and form submissions.
Every setup step below comes from Google's own Analytics Help pages, cited beside the step, and our own recommendations are labeled as ours.
How GA4 measures a website
Google Analytics 4 records everything as events. Google's About events page defines an event as a measure of a specific interaction on your website or app, such as loading a page, clicking a link or completing a purchase. Some events are collected automatically, some come from enhanced measurement, and others you implement yourself as recommended or custom events.
For a service business, a page view tells you someone arrived, and a key event tells you someone sent a request or tapped your phone number. Setup is mostly about recording those actions accurately.
Google Analytics setup step by step
Google's Set up Analytics for a website and/or app page covers the first three steps below.
Step 1: create the account and property
Go to analytics.google.com and click Start Measuring, or in Admin choose Create and then Account. Name the account for the business and set the data-sharing options. Then create the property: you need the Editor role, which you have automatically if you created the account.
The property asks for a name, a reporting time zone and a currency. Google gives this example: if a visitor arrives on a Tuesday in their time zone but it is Monday in yours, the visit is recorded as Monday. Choose Central time for an East Metro business. Google also notes that changing the time zone later affects only data going forward.
Step 2: add a web data stream
In Admin, under Data collection and modification, open Data Streams, click Add stream and choose Web. Enter your site's address and a stream name. Google recommends leaving enhanced measurement turned on at this point, and you can switch off individual events later.
Step 3: install the Google tag
The route you take depends on how your site is built.
- A field for the tag ID. Many website builders and content management systems have a field where you paste the Google tag ID, which starts with "G-" and is shown as the Measurement ID in the stream details. Google lists builders that work this way, including Wix, Squarespace, Duda and GoDaddy, along with WordPress plugins such as Site Kit.
- Custom HTML. If your builder has no tag ID field, Google says to paste the full Google tag into its custom HTML feature. In the stream, choose View tag instructions and then Install manually.
- The page code. If you control the HTML, Google says to paste the tag immediately after the opening head element on every page.
- Google Tag Manager. For basic collection, Google points to the Tag Manager help instructions for adding the Google Analytics configuration tag.
Google says data collection may take up to 30 minutes to begin.
That answers a question we hear about website builders and analytics. Google's setup page lists website builders and content management systems that have a field for the tag ID, and says to paste the tag into a custom HTML feature when a builder has no such field. The reports themselves come from GA4, so what a builder changes is how you install the tag and how easily you can add custom events and code. Check both before you pick one.
Turn on enhanced measurement and mark key events
What enhanced measurement collects
Google's Enhanced measurement events page says that enabling it for a web data stream sends events with no code changes. It covers page views, scrolls, outbound clicks, site search, video engagement, file downloads and form interactions, which are the form_start and form_submit events. The page states that you are required to ensure no personally identifiable information is collected. It describes outbound clicks as links leading away from your current domain, and a phone link is not on that list.
What a key event is
Google's About key events page says any event you collect can become a key event, which you use to count the actions most important to your business. Its instructions in Mark events as key events say to open Admin, then Events, find the event and click the star next to it. A standard property can have up to 30 key events, and Google says to allow up to 24 hours for a newly marked event to appear in standard reports.
Scroll to see all columns
| Action to measure | Where the event comes from | Our recommendation |
|---|---|---|
| Page view | Collected automatically | Leave as a plain event |
| Contact form sent | The enhanced measurement form_submit event, or the recommended generate_lead event | Mark as a key event after confirming it fires on your form |
| Phone number tapped | A custom event you create, for example with a Tag Manager click trigger | Mark as a key event |
| Booking request submitted | A recommended or custom event on the confirmation step | Mark as a key event |
| Estimate or brochure PDF opened | The enhanced measurement file_download event | Mark only if it signals real intent |
Recording phone taps and form sends
Google's Recommended events page lists generate_lead as the event for a user who submits a form or a request for information, and says recommended events are not sent automatically. For links, Google's click trigger page describes a Just Links trigger that fires on clicks on HTML links, which you can limit with a condition on the Click URL. In our reading, a phone number is an ordinary HTML link, so a Just Links trigger with a Click URL condition can match it and send a GA4 event that you then mark as a key event. Test it before you rely on it. A phone tap is also not a connected call, so compare the count against your call records.
Link Search Console, in one short step
Linking needs the Editor role on the Analytics property and verified ownership of the Search Console property, per Google's Connect Search Console to Google Analytics page. Our Google Search Console guide walks through the link and the two reports it adds in Analytics.
Set data retention
Google's Data retention page says a standard property can keep user-level data and key events data for 2 months or 14 months. It adds that the setting does not affect standard aggregated reports and only affects explorations and funnel reports. We recommend 14 months, since it is the longer option and a year-over-year comparison in an exploration is useful for seasonal trades. You need the Editor role, and Google waits 24 hours before applying a change.
Filter out your own visits
Google's Filter out internal traffic page has two steps. First, in the web stream's tag settings, choose Define internal traffic, name a rule, keep the traffic_type value "internal" and enter your IP address or range. Second, in Admin, open Data filters, create an Internal Traffic filter and choose Exclude.
Start the filter in Testing state and activate it once you have confirmed it works. Google warns that an active filter permanently changes the data, that excluded data is never processed, that you can create up to 10 data filters per property, and that a filter can take 24 to 36 hours to apply. In our experience, office IP addresses can change and technicians on mobile data will not match a rule, so treat the filter as a partial cleanup.
Verify that Google Analytics setup is working
Open Reports, then Realtime. Google's Realtime report page lists verifying that the measurement code works among its uses, and it shows active users and event counts by event name. It also describes the service as best effort without a formal service level objective, so a short delay is not proof of a failure.
For event-level checks, use Google's DebugView. It shows events from a device in debug mode in real time, and you turn debug mode on through Google Tag Assistant or preview mode. Google adds that events do not appear in DebugView when client-side privacy controls are in place or consent mode is in use and the user has not given consent for Analytics cookies. Submit a test form and tap your number to confirm both events appear.
Reading leads by city: an illustrative East Metro example
Here is an illustrative example with an invented company. Calderwick Plumbing serves Woodbury, Oakdale and Hudson. It marks three key events: a form send, a phone number tap and a booking request. A month later the owner opens the Demographic details report under User attributes and switches the location dimension to City to see where visitors are coming from.
Google's Demographic details report page says the City dimension is populated automatically and that Google derives location data from users' IP addresses. The page also says the report includes only aggregated data from users who consent to sharing demographics data, and that data thresholds may be applied when user counts are low. Its metrics include key events, so the same view can show how many key events came from each city. In our reading, an IP address maps to a network location and may not match the town where a person lives, and the consent condition and thresholds mean a small business may see thin or missing counts by city. Use the report to spot a pattern and confirm it against your call and form records. Our guide to traffic with no leads covers how to trace a lead across systems.
Our website design service includes wiring forms, booking widgets, call tracking and GA4 events into a build and testing them before launch. If your current tracking needs a second look, you can contact us.
Consent and privacy
Consent requirements depend on where your visitors are, which can include people outside Minnesota and Wisconsin. This is general information. It is not legal advice. Ask your attorney what applies to your site. Google describes consent mode as a way to control data collection based on user consent for advertising and analytics, in its consent mode guide for developers and its Tag Manager consent mode support page. Its enhanced measurement page also requires that no personally identifiable information is collected.