GA4 Setup Guide: From Installation to First Report

Getting Google Analytics 4 installed is straightforward. Getting it set up correctly is where most businesses stumble. A rushed or default installation leads to months of collecting incomplete data, which means months of making marketing decisions without the full picture.

This guide covers the complete GA4 setup process from creating your property to building your first actionable report. Whether you are setting up GA4 for the first time or resetting a poorly configured implementation, following these steps in order will give you a solid analytical foundation.

The goal is not just to collect data. It is to collect the right data, structured in a way that answers your most important business questions from day one.

Creating Your GA4 Property

Start in your Google Analytics admin panel by creating a new GA4 property. Set your reporting time zone to your primary business location, typically AEST or AEDT for Australian businesses. Set your currency to AUD. These settings affect how your data is aggregated and reported, and changing them later does not retroactively adjust historical data.

During property creation, Google will ask about your business objectives. Select the options that most closely match your priorities, as these influence which default reports GA4 surfaces. You can change these later, but starting with accurate selections saves time.

Create a web data stream for your website. Enter your full domain including the protocol. Enable enhanced measurement, which automatically tracks page views, scrolls, outbound clicks, site search, video engagement, and file downloads. These provide a baseline of useful data without any additional configuration.

GA4 will generate a Measurement ID starting with G-. You will need this for the installation step.

Installation via Google Tag Manager

While GA4 can be installed directly with a code snippet, Google Tag Manager provides significantly more flexibility for managing your tracking configuration. If you do not already have GTM installed, add the GTM container snippet to every page of your website.

In Google Tag Manager, create a new tag using the Google Analytics GA4 Configuration tag type. Enter your Measurement ID. Set the trigger to fire on All Pages. Publish the container.

Verify the installation using the GA4 DebugView in real time. Navigate to your website with the Google Analytics Debugger Chrome extension enabled, then check the DebugView report in GA4 to confirm events are flowing. You should see page_view events appearing within seconds.

If you are running a content management system like WordPress, Shopify, or a headless CMS with a Next.js frontend, ensure the GTM snippet loads on every route including dynamically rendered pages. Single-page applications require additional configuration to track virtual page views correctly.

For businesses prioritising data accuracy, consider implementing server-side tracking alongside your client-side setup from the beginning rather than retrofitting it later.

Essential Configuration Settings

With GA4 collecting data, configure the settings that affect data quality and usability. In the GA4 admin panel, set your data retention period to 14 months, the maximum available on the free tier. The default is 2 months, which severely limits your ability to analyse trends over time.

Enable Google Signals if you want cross-device reporting and demographic data. Be aware that enabling Google Signals can trigger data thresholding, where GA4 withholds data from reports to protect user privacy when sample sizes are small. For smaller websites, this trade-off may not be worthwhile.

Configure your internal traffic filter. Define the IP addresses used by your team and create a filter to exclude them from reporting. This prevents your own browsing from inflating traffic numbers and skewing engagement metrics.

Set up cross-domain tracking if your user journeys span multiple domains. This is common for businesses using separate domains for their main website and their checkout or booking system. Without cross-domain tracking, a user moving between domains appears as two separate users, breaking your funnel analysis.

Connect your GA4 property to Google Ads, Google Search Console, and any other Google products you use. These integrations flow data between platforms and unlock features like audience sharing and search query reporting.

Defining Your First Conversions

Conversions tell GA4 which user actions represent business value. Without defined conversions, GA4 tracks everything equally, and your reports lack the focus needed for decision-making.

Identify three to five key actions on your website that represent meaningful business outcomes. For most Australian businesses, these include contact form submissions, phone call clicks, email link clicks, and purchase completions. Mark the corresponding events as conversions in the GA4 admin panel.

If the events you want to track as conversions do not exist yet, create them. Use GA4's event creation feature for simple cases, like creating a conversion event when a user reaches a thank-you page. For more complex tracking, create the events in Google Tag Manager with appropriate triggers.

Test each conversion by completing the action yourself and verifying it appears in the Conversions report and DebugView. Conversion tracking errors compound over time, so catching misconfigurations early saves significant data cleanup later.

These conversions become the foundation for your conversion rate optimisation efforts, so invest the time to define them accurately.

Building Your First Meaningful Report

With data flowing and conversions defined, build a report that answers your most pressing marketing question. For most businesses, that question is: which channels are driving conversions?

Navigate to the Acquisition section in GA4's standard reports. The Traffic Acquisition report shows how users arrive at your website broken down by channel group. Add a secondary dimension of Session default channel group and filter to show only sessions that included a conversion event.

For a more tailored view, use GA4 Explorations. Create a Free Form exploration with dimensions for Session source/medium and Event name, and metrics for Sessions, Conversions, and Engagement rate. Apply a filter to show only your defined conversion events. This gives you a clear view of which traffic sources drive the most valuable actions.

Save this exploration and schedule it as an email report to arrive weekly. Having a consistent report delivered regularly builds the habit of data-informed decision-making and helps you spot trends early.

As your comfort with GA4 grows, expand your analysis to include funnel explorations that map the user journey from landing page to conversion, and path explorations that reveal the most common navigation patterns on your site.

Common Setup Mistakes to Avoid

The most frequent GA4 setup mistake is leaving enhanced measurement at its defaults without reviewing which events are relevant. Scroll tracking, for example, fires at the 90% threshold by default. For long-form content, this may be meaningful. For short pages, it fires on nearly every visit and adds noise to your data.

Another common mistake is not filtering internal traffic. Even a small team visiting the website daily can meaningfully skew engagement metrics, especially for lower-traffic sites.

Avoid creating too many conversions too early. Start with three to five high-confidence conversion events and expand as your understanding of the data matures. Marking dozens of events as conversions from day one dilutes the signal.

Finally, do not ignore the data retention setting. The default 2-month retention means you lose access to user-level data in Explorations after just 60 days. Set it to 14 months immediately after setup.

A clean GA4 setup is the foundation for effective marketing analytics. The time invested in proper configuration pays off every time you make a decision based on your data.

Need help setting up GA4 properly for your business? Get in touch to discuss your analytics requirements.