Setting up GA4 properly in the UK: consent, conversions and reports that matter

To set up GA4 properly for a UK small business, do four things in order. First, put a consent banner in front of it that meets UK GDPR and PECR, wired to Google Consent Mode v2. Second, track the handful of actions that make you money (form submissions, phone and email clicks, bookings or checkouts, and visits to key pages) and mark them as key events. Third, link Search Console and Google Ads. Fourth, check six reports once a month. Most small-business set-ups we audit get only one of those right. A careful set-up takes an experienced developer three to five hours.

That is the short version. The rest of this guide covers the consent rules in plain English, the five events most service businesses should track, how to name them so your reports stay readable, the linking steps, the reports worth your time and the mistakes we fix most often. There is a checklist at the end you can work through yourself or hand to whoever looks after your site.

Why “installed” is not the same as “set up”

Adding the GA4 tag to a website takes five minutes. Plenty of sites stop there, and the result is a property that counts visitors and page views but can’t tell you which pages bring enquiries, which channels are worth paying for, or whether last month’s drop was real or just people declining cookies.

A properly set-up property answers three questions without any digging: where did people come from, what did they do, and how many of them became leads or customers. Everything below serves those three questions. If a report or event doesn’t help answer one of them, you can usually ignore it.

Consent first: UK GDPR, PECR and the ICO

This section is our practical reading of the rules, not legal advice. If your business handles sensitive data or you’re unsure, speak to a data protection specialist.

Analytics cookies are governed mainly by the Privacy and Electronic Communications Regulations (PECR), with the standard of consent coming from UK GDPR. The ICO’s guidance has long said that analytics cookies are not “strictly necessary”, so they need consent: a clear opt-in, “Reject all” as easy as “Accept all”, no pre-ticked boxes, and a way to change your mind later.

The Data (Use and Access) Act 2025 relaxed this for some low-risk cookies, including certain analytics used only to understand and improve your own site, provided you tell people and give them a simple way to object. Whether a standard GA4 set-up fits that exemption is not clear-cut, because the data goes to Google, and the ICO’s guidance on the new exemptions is where you should check the current position. Our view: if you also run Google Ads, remarketing, Meta or LinkedIn pixels, you need a proper consent banner anyway, so the sensible default is to put GA4 behind the same banner. We cover banners in more detail in GDPR cookie banners in the UK: what’s actually required.

Consent Mode v2 in plain English

Consent Mode is how your banner tells Google tags what the visitor agreed to. Version 2 uses four signals: analytics_storage, ad_storage, ad_user_data and ad_personalization. Google requires these signals for UK and EEA traffic if you want to use Google Ads features such as remarketing and conversion measurement properly. There are two ways to run it.

If you aren’t sure, start with basic mode. It’s the cleanest position, and for a business spending a few hundred pounds a month on ads, the modelling in advanced mode rarely changes a decision. If you spend thousands a month and consent rates are low, advanced mode can recover a useful amount of conversion data, but take advice on how you describe it to visitors.

Two practical notes. Your consent platform (Cookiebot, Complianz, CookieYes and similar) must actually send the Consent Mode signals, which you can confirm in Tag Assistant. And expect GA4 to show fewer users than your old Universal Analytics reports did. That’s not a fault; it’s the people who said no.

The five conversions most service businesses should track

GA4 now calls conversions “key events”. Google Ads still calls them conversions. Same idea: the handful of actions that tell you the site did its job. For a plumber in Leeds, a solicitor in Cardiff or a consultancy in Manchester, these five cover nearly everything.

Why not just use enhanced measurement?

GA4’s enhanced measurement can log “form_start” and “form_submit” automatically. In our experience it is unreliable on WordPress: it fires on newsletter boxes, search forms and failed submissions, and misses forms that submit without reloading. Turn the form interactions option off and track the real success state instead. Keep the other enhanced measurement options (scrolls, outbound clicks, file downloads, site search) switched on; they cost nothing and are occasionally useful.

Bookings and checkouts

If you take bookings or sell online, track the value too. WooCommerce has well-maintained integrations that push purchase events with value, tax and items. Booking systems are messier, because many complete the booking on the provider’s own domain. If yours does, check whether it supports a GA4 or Tag Manager integration, or a redirect back to a thank-you page on your site. If it supports neither, you’ll be counting clicks on the “Book now” button, which tells you about intent but not about bookings. Our guide to booking systems, deposits and Stripe covers which systems handle this well.

Naming events so reports stay readable

Event names are permanent in practice. You can’t rename historical data, so a messy start stays messy. A few rules we use on every set-up:

• Use lower case with underscores (snake_case). GA4 is case-sensitive, so Click_Phone and click_phone are two different events.
• Use Google’s recommended event names where one fits (generate_lead, purchase, begin_checkout, sign_up). They feed built-in reports and map more cleanly to Google Ads.
• Name the action, not the page. One generate_lead event with a form_name parameter is better than contact_form_home, contact_form_footer and quote_form_services.
• Keep names under 40 characters and avoid GA4’s reserved names and prefixes (anything beginning ga_, google_ or firebase_).
• Register any parameter you want to report on as a custom dimension in Admin, otherwise it’s collected but you can’t see it in standard reports.
• Write the list down. A shared document with event name, trigger and purpose saves hours when someone else takes over.

Linking Search Console and Google Ads

Search Console

Search Console tells you which Google searches showed your pages and how often people clicked. GA4 tells you what they did next. Linking the two puts queries and landing pages next to engagement and key events.

In GA4, go to Admin, then Product links, then Search Console links, and choose your verified property and web data stream. You need to be an owner in Search Console and an editor in GA4. The two Search Console reports are not visible by default in many properties; open Reports, then Library, and publish the Search Console collection so the “Queries” and “Google organic search traffic” reports appear in your menu. Use a Domain property in Search Console if you can, so it covers www, non-www and any subdomains.

Google Ads

In GA4, go to Admin, then Product links, then Google Ads links. Once linked, import your key events into Google Ads as conversions, and decide which one is the primary conversion that bidding should aim for. For most service businesses that’s generate_lead plus click_phone; leave secondary actions like email clicks as “secondary” so they don’t distort bidding. Turn on auto-tagging in Google Ads so ad traffic is attributed correctly rather than landing in “Direct”.

If you already have a Google Ads conversion tag installed separately, decide on one source of truth. Counting the same lead through both the Ads tag and an imported GA4 event is a common way to double your reported conversions.

Six reports to check every month

You don’t need to live in GA4. Thirty minutes a month on these six reports is enough for most small businesses.

A sensible monthly habit: compare against the previous month and the same month last year, write two or three lines on what changed, and pick one thing to act on. The act-on part is what most people skip.

Common mistakes we fix

These come up on almost every GA4 property we’re asked to look at.

Double tagging

The GA4 tag is installed twice: once by a plugin (Site Kit, a theme option or a cookie plugin) and once through Tag Manager or a pasted snippet. Every page view counts twice, engagement rate looks oddly high, and conversions are inflated. Check with Tag Assistant or the Network tab in your browser: you should see one collect request per page view, not two.

Internal traffic counted as customers

Your own team visiting the site, checking the contact form and testing bookings all show up as visitors and leads. GA4 can exclude internal traffic, but it takes two steps: define the internal IP addresses in the data stream’s tag settings, then go to Admin, Data filters, and switch the internal traffic filter from “Testing” to “Active”. The second step is the one people miss. If your team works from home on changing IP addresses, a simple alternative is a browser extension or a cookie-based exclusion for staff devices.

Missing or broken consent

Either GA4 fires before anyone has agreed to anything, or the banner blocks GA4 permanently because the consent signal never reaches the tag. Both are easy to spot: load the site in a private window, reject cookies, and check whether analytics requests still fire with identifiers. Then accept, and check that they do fire.

The rest of the usual list

• Data retention left at the default two months. Set it to 14 months in Admin, Data collection, Data retention, or year-on-year comparisons in Explorations won’t work.
• Payment providers showing as referral sources. Stripe, PayPal and booking platforms steal the credit for your sales unless you add them to the unwanted referrals list.
• Test purchases left in the data. Use a separate test property or filter them before launch.
• Nobody owns the account. The property sits on a former employee’s or old agency’s Google account. Make sure the business owns it, with your developer added as a user.

A setup checklist

Work through this list in order. If you can tick every line, your GA4 is in better shape than most.

• GA4 property and web data stream created on a Google account the business owns
• One installation method only (we prefer Google Tag Manager), confirmed with Tag Assistant
• Consent banner installed, sending Consent Mode v2 signals, tested in a private window both ways
• Cookie and privacy notices updated to describe analytics and any advertising tags
• Enhanced measurement on, with form interactions turned off
• Five core events built and named in snake_case, with parameters registered as custom dimensions
• Lead, call and booking or purchase events marked as key events
• Internal traffic defined and the filter set to Active
• Unwanted referrals added for payment and booking providers
• Data retention set to 14 months
• Search Console linked and the Search Console report collection published
• Google Ads linked, auto-tagging on, key events imported with one primary conversion
• A test lead submitted and seen in DebugView and, a day later, in standard reports
• A one-page note of every event, trigger and purpose saved where the team can find it

Doing it yourself or getting help

If you’re comfortable in Tag Manager, the checklist above is a solid afternoon’s work. The fiddly parts are usually the form plugin, the consent platform and the booking system talking to each other properly.

If you’d rather hand it over, we do this as hourly work through our hire us page, under WordPress Development at £50 an hour. A typical small-business set-up takes three to five hours depending on how many forms and integrations you have:

Hours never expire, so any you don’t use on the set-up can go towards later changes. Volume discounts start at 10 hours, which makes sense if you’re combining analytics with other work such as speed improvements or new landing pages. For sites with custom checkouts, apps or CRM integrations, tracking usually sits inside a wider project through our API development and integration service. If you’re planning a new site, through our web development service or one of our fixed-price packages, ask for analytics and consent to be included in the brief. Building it in at the start is quicker and cheaper than retrofitting it later.

We’re based in London and do most of this remotely for businesses across the UK. If you’d like us to look at your current set-up first, send us a message with your website address and we’ll tell you what’s missing before you book anything.

Photo: Luke Chesser via Unsplash