How to Set Up Google Analytics 4 (GA4) and Understand Key Metrics
GA4 replaced Universal Analytics with an event-based model that trips up a lot of business owners used to the old interface. Here's what to set up first, and which metrics actually matter for a small or mid-sized business site.
Setting up your GA4 property
Create a property at analytics.google.com, add a Web data stream for your site, and install the tracking snippet (or use Google Tag Manager, which makes future changes easier without touching code again). Confirm data is flowing in the Realtime report before moving on.
The metrics worth watching
- Engaged sessions — sessions lasting 10+ seconds or with a conversion, a better quality signal than raw pageviews
- Conversions — set these up explicitly (form submits, calls, purchases) or GA4 won't know what matters to your business
- Traffic acquisition — which channels (organic search, paid, social, referral) actually bring people in
- Landing page performance — which pages people arrive on, and whether they convert or bounce
The mistake most businesses make
Watching total users and pageviews as the headline numbers. Neither tells you whether the traffic is doing anything for your business — conversions and engaged sessions do. Set up conversion events in your first week, not your first year.
Setting up conversion tracking properly
A conversion in GA4 isn't automatic — you have to tell it what counts. For most small business sites that means marking events like form_submit, phone_click, or purchase as key events (GA4's term for what used to be called goals). Without this step, you can have thousands of visitors and genuinely no idea whether any of them did anything that mattered to your business.
The most common gap we find auditing a new client's GA4 setup is a contact form that submits successfully but was never wired up as a tracked event — meaning months of real enquiries were invisible in the reporting the whole time. This is exactly the kind of gap we check first during an SEO audit, because decisions made on incomplete conversion data are often worse than decisions made with no data at all.
Connecting GA4 to Search Console
Linking your GA4 property to Google Search Console (under Admin → Product Links) pulls organic search queries and landing page performance directly into your GA4 reports, instead of switching between two separate tools. This is genuinely useful once you're doing any keyword research work — you can see, side by side, which search terms are actually bringing in engaged sessions versus which just generate impressions with no real interest behind them.
Using GA4 data to guide your SEO priorities
Traffic acquisition and landing page reports are where GA4 earns its keep for SEO decision-making. A page with strong organic traffic but a high bounce rate and low engaged-session rate is telling you something concrete: the content doesn't match what the search query promised, which is a job for content optimisation, not more traffic. A page with almost no organic traffic despite targeting a real keyword usually points to an on-page or technical issue worth investigating.
For a business serving a specific area, filtering the traffic acquisition report by landing page and cross-referencing it against your local SEO pages shows exactly which locations are pulling their weight in search and which need more work — data that's hard to get any other way.
GA4 for paid campaigns, not just organic
If you're running or considering paid advertising, GA4's channel grouping report is the fastest way to see whether paid traffic is actually converting at a rate that justifies the spend, compared to your organic or referral traffic. Businesses often discover through this report that a campaign generating plenty of clicks is bringing in visitors who bounce immediately — a landing page mismatch problem, not a targeting problem, and one that's cheaper to fix than to keep paying to send more traffic into.
The same logic applies to a lead generation funnel: GA4's funnel exploration reports (under Explore) let you see exactly which step of a multi-page signup or checkout process loses the most visitors, rather than guessing based on the overall conversion rate alone.
A realistic first-month checklist
- Confirm the data stream is live and Realtime is showing your own test visits
- Mark your genuine key events — form submissions, calls, bookings, purchases — don't rely on GA4's automatic events alone
- Link Search Console under Admin → Product Links
- Check the Traffic acquisition report weekly, not the homepage overview — that's where the decisions actually live
- Revisit this setup after any major site change, since a redesign or new form provider can silently break event tracking without any error appearing
Common GA4 setup mistakes worth avoiding
Beyond missing conversion tracking, the second most common issue is internal traffic pollution — your own team's visits, and any developer or agency work on the site, getting counted as real visitor sessions and quietly skewing every report. GA4's internal traffic filtering (under Admin → Data Streams → Configure tag settings) excludes known internal IP ranges, and it's worth setting up in the first week rather than discovering months later that a chunk of your "traffic" was actually just your own team testing the site.
A related mistake is never revisiting the setup after launch. GA4 configuration isn't a one-time task — new landing pages need conversion events wired up as they're built, and a site redesign or new booking system can silently disconnect existing tracking without throwing any visible error. Treating analytics setup as ongoing maintenance, not a launch-day checkbox, is what actually keeps the data trustworthy long enough to base real business decisions on it.