GA4 has been the only version of Google Analytics for over two years now, and most small business sites we audit in Calgary still have it misconfigured. Half have the default two-month data retention nobody changed. A quarter have no internal traffic filter, so the owner's own visits inflate every report. And almost none have marked the events that actually matter to their business.
The interface doesn't help. Google rebuilt Analytics from scratch and somehow made it harder to find basic information. But the tool itself is genuinely useful once you get past the setup, and this guide covers exactly what to configure, what to track, and what to ignore.
Create your property and data stream the right way
If you already have GA4 installed, skip to the settings section. If not, here's the short version.
Go to analytics.google.com, sign in with a Google account, and click "Start measuring." You'll name your account (your business name works fine), then create a property. The property is where your data lives. Set your time zone to Mountain Time and your currency to CAD. Google defaults to USD, and if you don't change it before collecting data, your currency-related reports will be off.
Next, create a web data stream. Enter your domain and give it a name. GA4 will generate a Measurement ID that starts with "G-" followed by a string of characters. This is what connects your site to your analytics property.
For installation, you have three options. If you're on WordPress, a plugin like Site Kit by Google handles it without touching code. If you're using Google Tag Manager (and you should be), add the GA4 Configuration tag with your Measurement ID. If you're doing it manually, paste the gtag.js snippet Google provides into the <head> of every page on your site.
We'd recommend Google Tag Manager for anyone who expects to track more than basic page views. It keeps all your tracking in one place and means you don't need a developer every time you want to track a new button click or form submission. Our SEO and analytics implementation work almost always starts with a proper GTM setup for exactly this reason.
One thing to verify immediately after installation: go to Admin > Data Streams, click your stream, and confirm Enhanced Measurement is turned on. This setting automatically tracks page views, scroll depth, outbound link clicks, site search queries, video engagement, and file downloads without any extra code. It's on by default for new properties, but we've seen cases where it was disabled during setup and nobody noticed for months.
The five settings most people miss
GA4's default configuration is incomplete. Google ships it in a state that works but leaves several useful settings turned off and at least one that will cost you data. Here's what to change right after installation.
Change data retention to 14 months
This is the single most missed setting in GA4. By default, event-level data is retained for only two months. After that, it's gone. Your standard reports (the ones in the left sidebar) aren't affected because they use aggregated data. But Explorations, the custom reports where you dig into specific user paths, funnels, and segments, rely on event-level data. With two-month retention, you can't look back further than eight weeks in any custom report.
Go to Admin > Data Collection and Modification > Data Retention. Change "Event data retention" from 2 months to 14 months. Also toggle on "Reset user data on new activity" so that returning visitors don't have their data expire while they're still active.
This change takes 24 hours to apply. If you've had GA4 running with two-month retention for a while, the older data is already gone. You can't recover it. Change this setting today.
Filter out your own traffic
Every visit you make to your own site shows up in GA4. So does every visit from your developer, your content writer, and anyone else who works on the site regularly. For a small business that gets a few hundred visits a month, internal traffic can seriously distort your data.
Go to Admin > Data Streams, click your stream, then Configure Tag Settings > Show More > Define Internal Traffic. Add a rule, give it a name like "Office IP," set the match type, and enter your office IP address (Google has a "What's my IP address?" link right there). If your team works from multiple locations, add each one.
Then, and this is the step people forget, go to Admin > Data Collection and Modification > Data Filters. You'll see a filter called "Internal Traffic." It defaults to "Testing" mode, which means it labels internal traffic but still includes it in your reports. Change it to "Active" to actually exclude it.
Be aware that data filters are permanent. Once active, excluded traffic is never processed and can't be recovered. If you want to test first, leave it in Testing mode and use a comparison in your reports to see what would be excluded.
Turn on Google Signals
Google Signals gives you cross-device reporting. If someone browses your site on their phone during lunch and comes back on their laptop that evening, Signals can connect those two sessions into a single user journey. Without it, that looks like two separate visitors.
Go to Admin > Data Collection and Modification > Data Collection, and toggle on "Google signals data collection." You'll need to acknowledge that you have appropriate privacy disclosures in place. If your privacy policy mentions analytics cookies and cross-device tracking, you're covered. Alberta businesses should also be aware of PIPA’s consent requirements, which go beyond what most generic privacy policies address.
One trade-off: enabling Signals can cause data thresholding in your reports. When the number of users in a report segment is too small, Google hides the data to protect privacy. This happens more often on low-traffic sites. If you're seeing "(other)" in your reports or data seems to be missing, Signals thresholding is the likely cause. For most small businesses, the cross-device insight is worth the occasional data gap.
Set up cross-domain tracking (if you need it)
If your website sends users to a separate domain at any point -- a booking system on a different URL, a payment processor, or a subdomain that runs different software -- you need cross-domain tracking. Without it, GA4 treats each domain hop as a new session, and you lose the connection between the visitor's journey on your main site and what they did on the other domain.
Go to Admin > Data Streams, click your stream, then Configure Tag Settings > Configure Your Domains. Add every domain your users might pass through. GA4 handles the rest automatically by appending a linker parameter to cross-domain URLs.
You'll also want to check Admin > Data Streams > Configure Tag Settings > List Unwanted Referrals. If a payment gateway like Stripe or PayPal shows up as a traffic source in your reports, add its domain here. This tells GA4 to ignore it as a referral and keep the original source intact.
Connect Search Console
This one takes 30 seconds and gives you search query data inside GA4.
Go to Admin > Product Links > Search Console Links. Click "Link," select your verified Search Console property, and choose your web data stream. Once connected, you'll find a Search Console section under Reports > Acquisition that shows which search queries brought people to your site, along with impressions, clicks, and average position.
This data exists in Search Console on its own. But having it inside GA4 means you can see what happens after the click. Did people who searched "Calgary web developer" actually spend time on your site, or did they bounce immediately? That's a question only the combined data can answer.
Events that matter for small businesses
GA4 is built around events. Every user interaction is an event: page views, clicks, scrolls, form submissions, video plays. Enhanced Measurement covers the basics automatically, but the events that tie to your actual business goals need manual setup.
Here's what we set up for most small business clients. Your list might differ, but this is a strong starting point.
Form submissions. If your site has a contact form, quote request form, or any other form that represents a lead, track the submission as a custom event. In Google Tag Manager, create a trigger that fires when the form submit confirmation appears (a thank-you message, a redirect to a confirmation page, or a dataLayer push from your form plugin). Create a GA4 Event tag that sends an event called generate_lead or form_submit to your property.
Phone number clicks. If your phone number is a clickable tel: link (it should be), track clicks on it. In GTM, use a Click URL trigger that matches tel: and send a phone_call event. For a local Calgary business, phone calls might be your most valuable conversion.
Button clicks that matter. Not every button needs tracking. But clicks on "Get a Quote," "Book Now," or "Schedule a Call" buttons represent real intent and should be tracked as events. Use GTM's Click Element trigger with a CSS selector that matches the button.
Scroll depth beyond the default. Enhanced Measurement tracks a single scroll event when someone reaches 90% of the page. That's binary -- they either scrolled or they didn't. If you want to know whether people are reading your content or just skimming, set up custom scroll tracking at 25%, 50%, 75%, and 90% thresholds using GTM's Scroll Depth trigger.
Once you've set up your events, mark the ones that represent real business outcomes as key events (what GA4 used to call conversions). Go to Admin > Events, find the event in the list, and toggle "Mark as key event." For a typical small business, generate_lead, form_submit, and phone_call should be key events. Scroll depth and general button clicks should not -- they're useful for analysis but don't represent a conversion.
The biggest mistake we see with GA4 events is tracking everything and marking nothing as a key event. If every event is important, none of them are. Mark three to five events that represent actual business outcomes, and use the rest for context.
The reports worth checking (and those you can ignore)
GA4 has dozens of report views. Most of them aren't useful for a small business checking in once a week. Here are the ones that actually tell you something actionable.
Realtime. Reports > Realtime. Good for one thing: confirming your tracking works. After installing GA4 or setting up a new event, open your site in another tab, trigger the event, and watch it appear in the Realtime report. Beyond that, you don't need to check it regularly.
Traffic Acquisition. Reports > Acquisition > Traffic Acquisition. This shows where your visitors come from: organic search, direct, social, referral, paid. Check this monthly. If organic traffic is flat or declining, that's a signal to look at your Core Web Vitals or content strategy. If referral traffic spikes from an unfamiliar domain, investigate -- it could be a good backlink or spam referral.
Landing Pages. Reports > Engagement > Landing Pages. This shows which pages people arrive on most often and how they perform. Sort by sessions to see your most visited entry points. Check the engagement rate (the percentage of sessions that lasted more than 10 seconds, had a key event, or included two or more page views). A landing page with high traffic but low engagement rate is leaking visitors.
Events and Key Events. Reports > Engagement > Events. This shows every event GA4 has recorded. Scroll down to find your custom events and check their counts. The Key Events report (under Engagement) shows only the events you've marked as key events, with counts per traffic source. This is where you answer the question: which channels are actually generating leads?
Search Console. Reports > Acquisition > Search Console (if connected). Check which queries are bringing people to your site and whether click-through rates are improving over time. If you're working on getting your site recommended by AI search, this data shows whether your traditional search visibility is also improving.
Reports you can mostly skip: the Demographics section (unreliable at low traffic volumes), the Tech reports (useful once a year to check device splits, not weekly), and Monetization (irrelevant unless you're running e-commerce).
GA4 setup checklist for small businesses
- Install via Google Tag Manager -- keeps all tracking in one place and makes future changes easy
- Change data retention to 14 months in Admin > Data Collection and Modification > Data Retention
- Define and activate the internal traffic filter -- define IPs in your data stream settings, then activate the filter under Data Filters
- Turn on Google Signals in Admin > Data Collection and Modification > Data Collection
- Connect Google Search Console under Admin > Product Links > Search Console Links
- Set up custom events for form submissions, phone clicks, and key button clicks via GTM
- Mark three to five business-outcome events as key events -- not everything, just the ones that mean money
- Set up cross-domain tracking if your users pass through a separate domain (booking system, payment gateway)
- Check Traffic Acquisition and Landing Pages monthly -- these two reports cover 80% of what you need to know
Stop drowning in data and start with what matters
GA4 can track almost anything. That's both its strength and the reason so many small business owners open it, feel overwhelmed, and close the tab. The interface is cluttered, the terminology keeps changing (conversions are now key events, views are now explorations), and Google adds new features faster than they document them.
But you don't need to use all of it. A properly configured GA4 property with five or six custom events, a clean internal traffic filter, and 14-month data retention gives you more actionable information than most enterprise setups we've seen running 200 tracked events with no clear purpose.
Set it up once, correctly. Check two or three reports monthly. And when something changes -- traffic drops, a landing page stops converting, a new traffic source appears -- you'll have the data to understand why and the context to act on it.
If analytics setup is on your to-do list and keeps getting bumped, that's the kind of thing we handle in a morning. The configuration itself isn't complicated. Getting it right the first time is the part that matters.
Sources
- Enhanced measurement events — Google Analytics Help -- Official documentation on GA4's automatic event tracking, including page views, scrolls, outbound clicks, site search, video engagement, and file downloads
- Recommended events — Google for Developers -- Google's reference for recommended event names and parameters for different business types
- Data retention — Google Analytics Help -- Documentation on GA4 data retention settings, 2-month default, 14-month maximum, and the impact on Explorations
- Filter out internal traffic — Google Analytics Help -- Step-by-step instructions for defining internal IP addresses and activating traffic exclusion filters
- Activate Google signals — Google Analytics Help -- How Google Signals works, cross-device reporting, thresholding behaviour, and regional controls
- Set up cross-domain measurement — Google Analytics Help -- Official guide to configuring cross-domain tracking and managing the linker parameter
- Conversions vs. key events in Google Analytics — Google Analytics Help -- Explanation of the terminology change from conversions to key events and how they function in GA4
- Set up events — Google for Developers -- Technical documentation for implementing custom events via gtag.js and GTM
- Set up Google Analytics events in Tag Manager — Google Tag Manager Help -- Step-by-step guide for creating GA4 event tags inside Google Tag Manager