GA4 for small businesses: what to track and how to set it up
Install GA4, mark enquiries, calls and WhatsApp clicks as key events, keep 14 months of data, exclude your own visits and link Search Console. That is all.
By Sohail Hussain21 November 20265 min read
For a small business website, Google Analytics 4 needs to answer three questions: how many people visit, where they come from, and how many of them contact you. To get there, create a property, install the tag, mark form submissions, phone clicks and WhatsApp clicks as key events, exclude your own visits, extend data retention to 14 months, and link Search Console. That takes about an hour. Everything else in GA4 is optional until those basics are right.
The third question is where most setups fall short. The tag is installed, page views arrive, and nothing records an enquiry, so the reports show traffic but not whether the site earns its keep.
What should a small business track in GA4?
Fewer things than the interface suggests. This list covers almost every company website:
| What | GA4 event | How it is collected | Key event? |
|---|---|---|---|
| Page views and sessions | page_view | Automatically | No |
| Where visitors came from | Session source and medium | Automatically | No |
| Contact form submitted | generate_lead | Thank-you page or a custom event | Yes |
| Phone number tapped | Custom, such as phone_click | A click trigger in Tag Manager | Yes |
| WhatsApp link tapped | Custom, such as whatsapp_click | A click trigger in Tag Manager | Yes |
| Brochure or price list downloaded | file_download | Enhanced measurement | Optional |
| Scroll depth, outbound clicks, site search | Built-in events | Enhanced measurement | No |
Resist adding more. Dozens of custom events with no key events marked answers nothing. If you run campaigns, tag the links with the UTM builder so each one shows as its own source.
Setting up analytics is part of every site launch we do, and on sites under website care and maintenance we check quarterly that key events still fire, because a redesigned form or a new thank-you page silently breaks tracking.
How do you set up the property and install the tag?
Google's own setup guide has the full detail. In short:
- In Google Analytics, open Admin, click Create, then Property. Enter the name, reporting time zone and currency, then your business details.
- In Admin, under Data collection and modification, open Data streams, click Add stream, choose Web, and enter your site's address. Leave Enhanced measurement on.
- Copy the Measurement ID, which starts with
G-. - Install the tag. On WordPress, Shopify, Wix or Squarespace, paste the ID into the platform's Google Analytics field or an official plugin. On a Next.js site, the
@next/third-partiespackage includes a Google Analytics component for the root layout. If you use Google Tag Manager, add a Google tag there instead, and do not also install it directly, or every page view counts twice.
Use one property for the website. Separate properties for staging or test sites keep test data out of your real reports.
How do you track enquiries as key events?
A key event is what GA4 calls an action that matters to the business. Google renamed them from "conversions" in 2024. Standard properties can have up to 30.
Form submissions. The most reliable method is a thank-you page. If your form sends people to /thank-you after a successful submission, open Admin, then Events under Data display, and click Create event. Name it generate_lead, and set it to match when event_name equals page_view and page_location contains /thank-you. Then mark it as a key event with the star icon. Enhanced measurement has its own form events, but they miss many JavaScript-based forms and can count attempts that failed, so do not rely on them for leads.
Phone and WhatsApp clicks. In Google Tag Manager, create a click trigger for links whose URL starts with tel:, and another for links containing wa.me. Attach a GA4 event tag to each, then mark both events as key events in GA4 once they have appeared. If you are adding a WhatsApp button, the WhatsApp link generator builds the link in the format the trigger expects.
Google's guide to marking key events covers the menus if they have moved since this was written.
Which settings should you change on day one?
Three settings are wrong by default for most businesses:
Data retention. GA4 keeps detailed event data for 2 months unless you change it. In Admin, under Data collection and modification, open Data retention and set it to 14 months, the maximum for standard properties. This affects explorations and funnel reports, not the standard reports, but you will want a year-on-year comparison in an exploration sooner or later.
Internal traffic. Your own team visits the site more than anyone. Open the data stream, go to Configure tag settings, then Define internal traffic, and add your office IP address. Then, in Data filters, change the internal traffic filter from Testing to Active. Remote teams on changing home IP addresses are harder to exclude; accept some noise.
Search Console link. In Admin, under Product links, open Search Console links and link your verified site. You then see the search queries that bring visitors alongside what those visitors did. The Google Search Console guide covers setting up Search Console itself.
Does GA4 need a cookie consent banner?
It depends where your visitors are. For visitors in the EU, EEA and UK, GA4's cookies need consent before they are set, and Google requires Consent Mode for its advertising features there. India, the UAE and Saudi Arabia have their own rules. Cookie consent banners: what the law asks for covers each, and the cookie consent banner generator builds a banner that blocks analytics until a visitor agrees.
Expect consent to lower the numbers GA4 reports. That is not a fault in the setup; declining visitors are simply not counted.
How do you check it is working?
Submit a real enquiry through each form and tap the phone and WhatsApp links on a phone. Within a minute or two, each should appear in the Realtime report. If one does not, use Tag Assistant and the DebugView report to see which tag fired.
Then, once a month, compare the number of generate_lead key events with the enquiries that actually arrived in your inbox. They will not match exactly: ad blockers and consent choices mean GA4 always under-counts. A steady gap is fine. A sudden drop to zero means tracking broke.
Once key events are reliable, the useful monthly report is short: enquiries by source, and the pages those visitors landed on. For engagement figures in GA4 terms, the bounce rate calculator converts sessions and engaged sessions into rates. The rest of the monthly routine, including the analytics check, is in the website maintenance guide.
Was this guide useful?