Advanced Google Analytics 4 Setup: A Guide for Business Owners

Google Analytics 4 (GA4) is free, and most business websites have it installed. Far fewer have it set up to answer the questions that matter to the person paying for the marketing.

A basic install will count visitors. It won’t reliably tell you which enquiries came from Google Ads, which pages lead to bookings or whether your marketing spend is paying off. That takes a more careful setup.

This guide explains what a proper GA4 setup includes. Use it to check your own, or to brief whoever looks after your website and advertising.

Make sure you own your analytics

Start here. Your GA4 account and property should belong to your business, not to a developer, agency or former staff member.

In GA4, go to Admin and open the access management settings. You should have administrator access through a business Google account. An agency can have its own access, but the business should hold the keys. The same applies to Google Tag Manager, Google Ads and Search Console.

While you are in Admin, check the data retention setting. GA4’s default keeps detailed event data for only two months. Standard properties can extend this to 14 months. It affects the detailed exploration reports rather than the standard ones, but there is rarely a reason to leave it short.

Decide what success looks like

Before changing any settings, write down what you want your website to do. For most local businesses, the important actions are:

• enquiry or quote form submissions
• taps on phone numbers
• bookings made through an online system
• purchases, if you sell online

These should be set up as key events in GA4. Google used to call them conversions, and you will still see that word in Google Ads.

Track the outcome, not the step before it. A form submission should only count when the form actually sends, usually by recording a thank-you page or confirmation message. Counting every click on a submit button inflates your numbers, because failed and repeated attempts are included.

Check for double counting

A common problem is the GA4 tag installed twice. It might be added once by a plugin and again by the theme, or once directly and again through Tag Manager. The result is doubled page views and events, and reports you can’t trust.

Google Tag Assistant and GA4’s DebugView show what fires when a page loads. Each page should send one set of GA4 data, not two.

Use Google Tag Manager for anything beyond the basics

GA4’s enhanced measurement records some actions automatically, such as scrolling, outbound clicks and file downloads. It is a helpful start. For forms in particular, the automatic tracking is often unreliable.

Google Tag Manager lets you set up accurate tracking for calls, form submissions, bookings and other actions. All your tracking tags sit in one place, and changes can be tested before they go live.

Booking systems and other domains

Many businesses send customers to a separate booking platform, payment page or portal on a different domain. Without the right setup, GA4 loses track of the visitor at that point. The booking may then be credited to the booking platform, rather than to the Google Ads click or search that actually brought the customer in.

GA4 has a cross-domain setting for domains you control. Third-party booking tools vary. Some have a GA4 integration, some support cross-domain tracking and some only let you track the click through to the booking page. Ask your booking provider what they support, then test it with a real booking.

Payment gateways and similar sites should also go on GA4’s list of unwanted referrals, so they don’t take credit for sales.

Filter out your own visits

Staff visit the website often. Set up an internal traffic filter in GA4 for your office internet connection so their visits don’t skew the numbers, and exclude developer and test traffic as well.

Connect Google Ads and Search Console

If you advertise with Google Ads, link it to GA4. You can then see what ad visitors do on your site, and import GA4 key events into Ads if that suits your setup.

Many advertisers also track their most important actions directly in Google Ads. Whoever manages your Google Ads should be clear about which source the campaigns are bidding on, and make sure the same enquiry is not counted twice. Poor tracking is one of the most common reasons Google Ads campaigns underperform.

Linking Search Console adds search query data, showing which Google searches bring people to your pages.

Tag your own links

GA4 needs help to recognise traffic from emails, social posts, QR codes and your Google Business Profile. Adding UTM tags to those links tells GA4 the source and campaign.

Keep your naming consistent, use lower case and keep a simple record of the tags you use. Mixed naming such as “Facebook”, “facebook” and “FB” splits your reports into pieces that are hard to add up.

Understand attribution

Customers rarely enquire on their first visit. They might find you through a Google search, come back through an ad and then type in your address a week later.

GA4 uses a data-driven attribution model by default, which shares credit across the steps that led to a key event. Google Ads works in a similar way. GA4 and Google Ads will rarely show exactly the same numbers, and neither will match your own records perfectly. That is normal. What matters is that each is set up correctly and the trends make sense.

Where the sale happens offline, consider recording which enquiries became paying jobs. Some CRMs can send that information back to Google Ads, which helps campaigns focus on enquiries that turn into work. This is a more advanced step and worth discussing with whoever manages your ads.

Server-side tagging and consent

Ad blockers and browser privacy features mean some visits are never recorded. Server-side tagging sends data through a server you control before it reaches Google. It can improve data quality and gives you more control over what is shared. It also adds setup and hosting costs, so it suits businesses with meaningful ad spend or online sales more than small brochure sites.

Google’s Consent Mode changes how tags behave depending on whether a visitor accepts cookies. It is required for some overseas markets and is less common in Australia, but privacy expectations here are rising. Your privacy policy should explain how you use analytics and advertising cookies.

Never send personal information such as names, email addresses or phone numbers into GA4, including through page addresses or form data. Google’s policies prohibit it. Health practices need extra care, because health information is treated as sensitive under Australian privacy law.

Test before you trust it

After setup, test every key event yourself. Submit each form, tap the phone numbers on a mobile and make a test booking, then check they appear in DebugView or the real-time report. Over the following weeks, compare GA4’s enquiry numbers with what actually landed in your inbox.

Test again after any website change, new plugin or form update. Tracking often breaks quietly during site updates.

Build a report you will actually use

GA4’s standard reports are detailed but can be overwhelming. A simple dashboard in Looker Studio, Google’s free reporting tool, or a custom report in GA4 can show just what matters:

• enquiries, calls and bookings by month
• enquiries by source, such as Google Ads, organic search and social media
• the pages that lead to enquiries
• cost per enquiry, if you advertise

SLINKY is a Perth digital agency founded in 1998. If you would like your GA4 checked or set up properly, get in touch. You will deal directly with senior people, with no lock-in contracts.