Google Analytics 4 Setup Checklist for Small Business Websites

Most small business websites have GA4 installed. Most of them are tracking almost nothing useful. The property exists, a stream is connected, and the session count goes up every day, but the data does not actually answer the questions the business needs answered.

This is a practical setup guide. Twelve steps that take a properly configured GA4 property from nonexistent to genuinely useful. Skip any of these and the gaps will show up when you need the data most.

Why GA4 Setup Still Gets Botched

GA4 replaced Universal Analytics in July 2023. Two years later, a meaningful number of small business websites are still on incomplete setups, either migrated without proper configuration or set up once by someone who followed a tutorial that stopped at "add the tag." The default GA4 property gives you pageviews and sessions. It does not give you which pages led to enquiries, which traffic sources drive bookings, or whether your Google Ads campaigns are actually converting. You have to build that.

Start to finish, a proper setup takes three to four hours. That investment pays back every time you need to make a decision about where to spend marketing budget.

Step 1: Create the GA4 Property

Go to analytics.google.com and sign in with the Google account that owns the business assets. Click Admin, then Create Property.

Name the property clearly: "Business Name - Website" is clean and searchable. Set the industry category accurately. Set the reporting time zone to Australian Central Time (ACST or ACST+30 depending on season). Set currency to Australian Dollar (AUD). These defaults affect all reporting, and fixing them later is tedious.

Step 2: Create the Data Stream

Inside the new property, click Data Streams, then Add Stream, then Web. Enter the website URL exactly as it appears with the correct protocol (https:// not http://). Name it to match the property, for example "Website."

GA4 will generate a Measurement ID in the format G-XXXXXXXXXX. Copy this. You will need it in the next step.

Step 3: Install via Google Tag Manager

Do not add the GA4 tag directly to the website code. Use Google Tag Manager. GTM gives you the ability to add, modify, and test tags without touching the codebase every time something changes.

In GTM, create a new tag, select Google Tag as the tag type, and paste the Measurement ID. Set the trigger to All Pages. Publish the container.

Verify it is working by opening the GA4 property, going to the DebugView, and loading the website in a browser with the Tag Assistant Chrome extension active. You should see pageview events appearing in DebugView within seconds. If nothing appears after two minutes, the tag is not firing.

Step 4: Configure Key Events

GA4 calls conversions "key events." By default, GA4 tracks session_start, first_visit, and page_view. None of those are conversions for a small business.

The events you need to mark as key events depend on the business type, but for most service businesses and restaurants this list covers the priorities:

• form_submit or generate_lead (contact form or booking request submitted)
• phone_call_click (user taps a phone number on mobile)
• click to booking platform (clicks to an external system like Quandoo or OpenTable)
• purchase (if the site processes transactions)

Set these up via GTM triggers, then go to GA4 Admin, Events, and toggle each event as a key event once the events are appearing in the interface. Key events appear in the Conversions report and are available for use in Google Ads import.

Step 5: Link Search Console

Go to GA4 Admin, scroll to Product Links, and click Search Console Links. Connect the Google Search Console property that matches the website.

This connection enables the Queries report inside GA4, which shows which Google search terms brought traffic to the site. For a small business trying to understand organic search performance, this is one of the most useful reports available. Without the link, GA4 shows (not set) for organic search queries.

The Search Console property needs to be verified and in the same Google account, or the linking account needs admin access to both properties.

Step 6: Link Google Ads

If the business runs Google Ads, link the Ads account to GA4. Go to Admin, Product Links, Google Ads Links. Complete the connection and confirm that auto-tagging is enabled in the Ads account settings.

Once linked, GA4 imports Google Ads cost, click, and impression data alongside session and conversion data. This connection also enables the import of GA4 key events as conversion actions in Google Ads, which is more reliable than the Google Ads conversion tag for some event types.

Step 7: Set Up Audiences

GA4 audiences let you segment users for reporting and for remarketing. Create these 4 audiences from day one.

First: All Converters. Condition: key event is true (any key event). This audience contains everyone who completed a meaningful action on the site.

Second: High Engagement. Condition: session duration greater than 90 seconds OR pages per session greater than 3. This captures users who are clearly evaluating the business but have not converted yet.

Third: Specific Page Visitors. For restaurants: users who visited the menu page or reservations page. For service businesses: users who visited a specific service page.

Fourth: Returning Users. Session count greater than 1. These users already know the business. They convert at higher rates and are worth targeting specifically in paid campaigns.

Step 8: Enable Google Signals (If Applicable)

Google Signals allows GA4 to use cross-device data for users who are signed into a Google account and have personalised ads enabled. Go to Admin, Data Settings, Data Collection, and toggle Google Signals on.

Note the trade-off: Google Signals can cause thresholding in reports, where GA4 suppresses data in smaller segments to preserve anonymity. For small businesses with modest traffic, this can cause gaps in demographic reports. Enable it, watch for thresholding warnings in reports, and decide if the cross-device data benefit outweighs the reporting gap for your traffic volume.

Step 9: Configure Data Retention

By default, GA4 retains event data for two months. For any meaningful year-on-year analysis, this needs to change.

Go to Admin, Data Settings, Data Retention. Change Event Data Retention to 14 months. This is the maximum available on the free tier. The 14-month window allows you to run a full year comparison without losing the earliest data in the comparison window. Save this setting immediately after creating the property. Data retention settings are not retroactive.

Step 10: Exclude Internal Traffic

Your own visits to the website inflate session counts, skew time-on-page metrics, and pollute the conversion data if you test forms or buttons. Exclude internal traffic by IP address.

In GTM, create a GA4 Configuration tag or edit the existing one to include a traffic type parameter. Alternatively, go to Admin, Data Streams, open the web stream, click Configure Tag Settings, then Show All, then Define Internal Traffic. Add the IP address or IP range for the office and any team members working from fixed locations.

Then go to Admin, Data Filters, create a filter type "Internal Traffic," set it to active. This removes matching traffic from the processed reports going forward.

Step 11: Install the GA4 DebugView for Ongoing Verification

DebugView is under Admin, DebugView, but you access real-time debug data via the Tag Assistant Companion in Chrome. Use this any time a new event is added to verify it fires correctly, the parameters look right, and the event name matches exactly what is expected.

A common mistake is setting up a key event in GA4 using a name that does not exactly match what the GTM trigger is sending. If the GTM trigger sends "form_submission" but the GA4 key event is named "form_submit," it never marks as a key event. Case-sensitive, character-for-character match required.

Step 12: Know What to Ignore in Reports

GA4 gives you a large number of reports. Most small businesses should focus on three.

The Acquisition report shows where traffic comes from. Channels, campaigns, and source/medium breakdown. This tells you which marketing channels are driving visits.

The Engagement report (specifically Pages and Screens) shows which pages get the most visits and which ones hold attention. For a restaurant, is the menu page getting traffic? Is the reservations page? Those questions are answerable here.

The Conversions report shows key event counts by channel, campaign, and page. This is the core question: which traffic sources are producing actual conversions, not just visits.

What to ignore early on: the Monetisation reports unless you run eCommerce, the Demographics reports if you have thresholding warnings showing, and the Explore section until you have enough volume to make custom analyses meaningful. The standard reports answer 80% of the questions a small business needs to answer.

Get the setup right once and GA4 becomes a reliable decision-making tool. Leave any of these steps incomplete and you are making marketing budget decisions without the data to support them. If you want help configuring tracking that connects properly to your ad campaigns, talk to us.