Google Analytics is a free measurement platform that helps you understand how people find and use your website or app. It can show which marketing channels generate visitors, which landing pages attract engagement and which journeys result in enquiries, purchases or other valuable actions.
However, Google Analytics has changed significantly. Universal Analytics, with its familiar Audience, Acquisition, Behaviour and Conversion reports, has been retired. The current platform is Google Analytics 4, usually shortened to GA4.
GA4 uses an event-based measurement model. Page views, form submissions, purchases, video engagement, file downloads and other interactions can all be recorded as events. Important events can then be designated as key events and, where appropriate, used as advertising conversions.
This guide explains how GA4 works, how to configure it and how to turn its reports into practical marketing decisions.
What Is Google Analytics 4?
Google Analytics 4 collects information about interactions with your website or app. It organises that information into reports that help you analyse traffic acquisition, user behaviour, engagement, revenue and marketing outcomes.
A typical GA4 implementation can help answer questions such as:
How many people visit the website?
Which channels attract new users?
Which campaigns generate engaged sessions?
Which pages bring people into the website?
What do visitors do after arriving?
Which forms, calls, bookings or purchases are completed?
Which products generate the most revenue?
Where do potential customers leave a funnel?
Which devices and browsers are being used?
How does paid advertising compare with organic search, email and social media?
GA4 is not simply a website traffic counter. When configured properly, it becomes part of a wider measurement system connecting marketing activity with meaningful business outcomes.
How GA4 Differs From Universal Analytics
Older tutorials frequently refer to Universal Analytics concepts such as views, goals, bounce rate and Behaviour reports. These instructions should not be used as a guide to the current platform.
The principal differences include:
| Universal Analytics | Google Analytics 4 |
|---|---|
| Sessions and page views formed the main measurement model | Almost every interaction is recorded as an event |
| Goals measured important actions | Important events are designated as key events |
| Views were used to organise and filter data | GA4 primarily uses accounts, properties and data streams |
| Behaviour reports contained page data | Pages, landing pages and events are generally found within Engagement reports |
| Audience reports contained user information | Demographics and technology data appear within User reports or business-objective collections |
| Ecommerce used a separate transaction structure | Ecommerce interactions use events such as view_item, add_to_cart and purchase |
| Reporting focused mainly on websites | Websites and apps can be measured within the same property |
| Bounce rate was a prominent quality metric | Engaged sessions and engagement rate receive more emphasis |
The change to event-based measurement makes GA4 more flexible, but it also means that account configuration is more important. Installing the base tag is only the beginning.
Start With a Measurement Plan
Before creating tags and events, decide what the business actually needs to measure.
A local service company may need to record:
Contact-form submissions
Telephone calls
Appointment bookings
Quote requests
Live-chat enquiries
Qualified leads
Completed sales
Revenue
An ecommerce company may need:
Product views
Product-list interactions
Add-to-basket events
Checkout progression
Purchases
Revenue
Coupons
Refunds
A content-led website may focus on:
Landing-page engagement
Article views
Newsletter registrations
Resource downloads
Video engagement
Contact enquiries
Avoid treating every available interaction as equally important. A page view, scroll and purchase may all be events, but they do not have the same commercial value.
A useful measurement plan defines:
| Element | Example |
|---|---|
| Business objective | Generate more qualified sales enquiries |
| User action | Submit the consultation form |
| GA4 event | generate_lead |
| Useful parameters | Form name, page location, service type |
| Key event status | Yes |
| Advertising conversion | Yes, if used for campaign measurement or bidding |
| Commercial outcome | Qualified opportunity or completed sale recorded in the CRM |
This provides a clearer foundation than installing Analytics first and deciding what the data means later.
How to Set Up Google Analytics 4
Create an Account and Property
Sign in to Google Analytics and create an account if the business does not already have one.
Within the account, create a GA4 property. Configure the property using the correct:
Business name
Reporting time zone
Currency
Industry category
Business objectives
The time zone and currency deserve particular attention. Incorrect settings can make daily reporting confusing and can produce inconsistencies when comparing GA4 with advertising platforms, ecommerce systems or CRM reports.
Create a Web Data Stream
A data stream is the source from which GA4 receives information. For a website, create a web data stream and enter the main website URL.
The stream will be assigned a Measurement ID beginning with G-. This identifies the GA4 data stream when the website sends data to Google Analytics.
Install the Google Tag
The Google tag must be installed across the website. Common installation methods include:
A native website or ecommerce-platform integration
A content management system integration
Google Tag Manager
Manual placement within the website code
Google recommends placing its tag across the relevant website pages and avoiding duplicate installations. The official instructions explain how to install the Google tag and connect a website to GA4.
Google Tag Manager is often the most flexible approach because it can manage GA4 events, Google Ads tags and other measurement scripts from one container. It also provides preview and debugging tools before changes are published.
Whichever method you use, make sure GA4 is not installed twice through different integrations. Duplicate tags can inflate page views, events and conversions.
Configure Enhanced Measurement
Enhanced Measurement can automatically collect several common website interactions without requiring separate code for each one.
Depending on the website and configuration, these may include:
Page views
Scrolls
Outbound link clicks
Site-search activity
Video engagement
File downloads
Form interactions
Google provides a full description of its Enhanced Measurement events and settings.
Do not assume that an automatically collected event is necessarily accurate enough to serve as a business conversion. For example, a generic form interaction may not prove that a valid form was successfully submitted. Important lead events should be tested against the website’s actual confirmation behaviour.
Configure Consent and Privacy Controls
UK and European websites must consider privacy, cookie consent and data protection when implementing analytics and advertising tags.
A suitable setup may require:
A consent management platform
Clear cookie and privacy information
Consent Mode configuration
Appropriate data-retention settings
Controls for advertising personalisation
Exclusion of unnecessary personal data
Processes for handling data-subject requests
Consent Mode communicates a user’s consent choices to Google tags. It is not a cookie banner, consent management platform or substitute for an appropriate legal basis.
Google provides dedicated guidance for consent settings in GA4. Businesses should obtain appropriate legal advice for their specific circumstances rather than treating an Analytics setting as proof of compliance.
Never send names, unencrypted email addresses, telephone numbers or other prohibited personally identifiable information through ordinary GA4 event parameters or page URLs.
Set Data Retention
Review the property’s data-retention settings before relying heavily on Explorations.
Retention settings affect how long certain user-level and event-level data remains available for exploratory reporting. They do not necessarily affect standard aggregated reports in the same way.
Google recommends that organisations review their GA4 data-retention controls. Select a period that supports the organisation’s analytical requirements while remaining consistent with its privacy policy and data-governance obligations.
Exclude Internal and Developer Traffic
Visits from employees, developers and agencies can distort results, particularly on smaller websites.
Configure and test internal traffic rules where appropriate. Do not immediately activate a permanent exclusion without confirming that it identifies the correct traffic. An incorrectly configured filter can remove legitimate data, and filtered historical data cannot simply be restored.
Developer traffic can also be separated so that testing remains visible in DebugView without contaminating routine reporting.
Configure Cross-Domain Measurement
Cross-domain measurement may be necessary when a customer journey spans more than one domain, such as:
A main website and separate booking platform
A marketing website and externally hosted checkout
Multiple related domains within the same user journey
A website and customer portal
Without correct cross-domain configuration, GA4 may start a new session as the user moves between domains. The booking or payment platform may then appear as the referral source, obscuring the marketing channel that originally attracted the customer.
Google’s cross-domain measurement instructions explain how to identify the domains that should be measured together.
Payment processors and other external tools may also need to be added to the unwanted referrals list. This must be handled carefully because excluding a genuine referral source would also make reporting less accurate.
Understand the Main GA4 Concepts
Users
Users represent people or devices that interact with the website or app, subject to the available identifiers, consent status and identity configuration.
GA4 can report several user metrics, including:
Total users
Active users
New users
Returning users
These metrics are not interchangeable. Check which user metric is being displayed before comparing two reports.
Analytics cannot perfectly identify every human being. Someone using several devices, clearing cookies or refusing consent may be counted differently from a signed-in user whose activity can be connected across devices.
Sessions
A session is a period of interaction with the website or app.
Sessions help you understand individual visits rather than only the total number of people. One user can generate several sessions over time and may return through different marketing channels.
Events
Events are the foundation of GA4 measurement.
Automatically collected events can include actions such as:
first_visitsession_startpage_viewuser_engagement
Enhanced Measurement adds other interactions where enabled. Google also provides recommended event names for common business activities, including:
generate_leadsign_uploginsearchview_itemadd_to_cartbegin_checkoutpurchase
Use Google’s recommended event names where they accurately describe the action. This improves consistency and can populate predefined reports more effectively than an unnecessary custom naming system.
Event Parameters
Parameters add context to an event.
A generate_lead event might include parameters indicating:
Which form was submitted
Which service was selected
Which page contained the form
Whether the form was in the header, body or footer
The stated lead value, if one can be assigned responsibly
A purchase event should include appropriate ecommerce information such as:
Transaction ID
Currency
Revenue value
Product identifiers
Product names
Quantity
Tax and shipping where relevant
Parameters are essential when one event name covers several forms, products or content areas. Some parameters must be registered as custom dimensions or metrics before they can be used conveniently within standard reports and Explorations.
Key Events and Advertising Conversions
An event becomes a key event when it represents an action that is especially important to the business.
Common key events include:
A genuine lead-form submission
A completed appointment
A new account registration
A purchase
A subscription
A telephone enquiry
Google’s current measurement structure distinguishes between an event, a GA4 key event and an advertising conversion:
Event: An interaction recorded by Analytics.
Key event: An event identified as important to the business.
Conversion: A key event used for advertising measurement and optimisation, including integration with Google Ads where applicable.
Google describes this as an event-to-key-event-to-conversion process.
Do not mark every micro-interaction as a key event. If scrolls, button clicks, page views and genuine enquiries all appear as equivalent outcomes, reports become harder to interpret and advertising algorithms may optimise towards actions with little commercial value.
The Main Google Analytics Reports
GA4 reporting can vary according to the property’s business objectives and the report collections published in its Library. Two users may therefore see slightly different navigation.
Reports generally include overview reports, which summarise a subject, and detail reports, which provide more granular analysis.
Reports Snapshot
The Reports snapshot gives a high-level view of recent activity. It may include users, traffic sources, engagement, key events and revenue.
Use it for a quick status check, but do not use it as the only source for diagnosing performance. Summary cards can conceal important differences between channels, campaigns, landing pages and user groups.
Realtime Reports
Realtime shows recent activity and is useful for:
Confirming that the website is sending data
Watching activity after a campaign launch
Checking which pages are currently being viewed
Testing basic source and event information
Identifying sudden traffic spikes
The Realtime pages report can show the pages currently being viewed and the number of active users on them.
Realtime is helpful for preliminary checks, but it is not a substitute for DebugView or a complete implementation test. Some data is processed differently before appearing in standard reports.
Acquisition Reports
Acquisition reports explain how people arrived at the website.
Two reports are particularly important:
User acquisition reports how new users were first acquired. It commonly uses dimensions such as First user default channel group or First user source/medium.
Traffic acquisition reports where sessions came from, including sessions generated by new and returning visitors. It commonly uses Session default channel group or Session source/medium.
This distinction matters. A user may originally discover the business through organic search and return later through paid search. User acquisition retains the first-user perspective, whereas traffic acquisition examines the source of individual sessions. Google provides a useful comparison of User Acquisition and Traffic Acquisition.
Traffic channels may include:
Organic Search
Paid Search
Organic Social
Paid Social
Display
Referral
Email
Direct
Cross-network
Unassigned
An increase in Direct or Unassigned traffic does not necessarily mean that more people typed the website address into their browsers. It can indicate missing campaign tags, redirects removing parameters, consent limitations, unsupported source information or incorrectly formatted UTMs.
Engagement Reports
Engagement reports help you understand what visitors do after arriving.
Useful reports can include:
Events
Key events
Pages and screens
Landing pages
The Pages and screens report focuses on content that users viewed during their sessions. The Landing page report focuses on the first page viewed during each session.
A high-traffic page is not automatically a high-performing page. Review traffic alongside:
Engagement rate
Average engagement time
Key-event rate
Leads or purchases
Revenue
Exit behaviour
Device category
Traffic source
A landing page for PPC advertising should ultimately be assessed against the action it is expected to produce, rather than page views alone.
Monetisation and Ecommerce Reports
For a correctly configured ecommerce website, monetisation reports can show information about:
Items viewed
Products added to baskets
Checkout activity
Purchases
Revenue
Promotions
Coupons
Refunds
Subscription or advertising revenue where applicable
These reports require structured ecommerce event data. Installing the standard GA4 tag does not automatically produce complete ecommerce reporting.
Always send a unique transaction ID with purchase events. This helps prevent duplicate purchases when a confirmation page is refreshed or revisited.
GA4 revenue should be reconciled with the ecommerce platform, payment processor or accounting system. Differences can occur because of consent, attribution, refunds, tax treatment, currencies, duplicate events, processing rules and implementation errors.
Businesses taking payments through Stripe can learn more about connecting Stripe transactions with GA4.
Retention Reports
Retention reports help show whether people return after their first visit.
This is particularly useful for:
Subscription services
Membership platforms
Ecommerce brands with repeat purchases
SaaS products
Content websites
Mobile apps
Many lead-generation websites have longer or less frequent journeys, so retention data may be less immediately useful than acquisition, landing-page and CRM reporting.
User Attributes and Technology Reports
User reports can provide aggregated information about:
Country and region
Language
Device category
Browser
Operating system
Screen resolution
Platform
Treat inferred demographic data cautiously. It may be incomplete, thresholded or unavailable because of consent, Google signals and reporting-identity requirements.
Technology reports are often more actionable. If mobile visitors generate substantial traffic but convert poorly, investigate mobile page speed, form usability, call functionality and layout before assuming that the audience is less valuable.
How to Answer Common Business Questions in GA4
How Much Traffic Does the Website Receive?
Review active users, sessions and views for the required date range. Compare the current period with a meaningful previous period, such as the previous month or equivalent trading period.
Do not rely on one metric in isolation:
Users estimate audience size.
Sessions represent visits.
Views represent pages or screens viewed.
Engaged sessions indicate more meaningful interaction.
Where Does the Traffic Come From?
Open Traffic acquisition and analyse:
Session default channel group
Session source/medium
Session campaign
Engaged sessions
Key events
Session key-event rate
Revenue
This shows whether channels attract traffic that takes useful action, not merely traffic volume.
Which Marketing Activity Attracts New Customers?
Use User acquisition to understand the first recorded source associated with new users.
For a stronger customer-acquisition view, connect analytics data with ecommerce transactions or CRM lifecycle information. GA4 can identify website behaviour, but it may not know whether a lead became a qualified opportunity or customer unless that outcome is sent back through an appropriate integration.
Which Landing Pages Perform Best?
Use the Landing page report and compare:
Sessions
Engagement rate
Average engagement time
Key events
Session key-event rate
Revenue
Segment the results by channel and device. A page can perform strongly for brand searches but poorly for generic paid traffic, and a blended total can hide that difference.
Which Content Is Most Popular?
Use Pages and screens to compare views and users, but also examine engagement and onward actions.
For a blog, useful outcomes may include:
Newsletter registrations
Contact enquiries
Downloads
Visits to service pages
Assisted customer journeys
Raw page views tell you what was opened. They do not necessarily tell you what created business value.
Where Do Users Leave a Funnel?
Use an Exploration to build a funnel containing the relevant steps.
For ecommerce, this could include:
Product viewed
Product added to basket
Checkout started
Shipping or payment details submitted
Purchase completed
For lead generation, it could include:
Service landing page viewed
Form started
Form submitted
Appointment booked
Qualified lead recorded
Large losses between steps can reveal technical problems, unclear messaging, weak offers, unexpected costs or poor form usability.
Campaign Tracking With UTM Parameters
UTM parameters help GA4 identify traffic from marketing links that would otherwise be grouped incorrectly.
The principal parameters include:
utm_source— the platform, publisher or listutm_medium— the marketing mediumutm_campaign— the campaign nameutm_content— the advert, creative or link variationutm_term— the keyword or other relevant targeting detail
For example:
https://example.co.uk/service/?utm_source=linkedin&utm_medium=paid_social&utm_campaign=crm_consulting&utm_content=video_testimonial
Use a documented naming convention. Inconsistent capitalisation and spelling can fragment one channel into several rows because Facebook, facebook and fb may be treated differently.
Avoid adding UTMs to internal website links. Internal UTMs can overwrite acquisition information and start misleading sessions.
Google Ads should normally use auto-tagging so that Google’s click identifiers and campaign information can be transferred appropriately. Manual UTMs may still support reporting requirements, but they should complement rather than interfere with auto-tagging.
Linking GA4 With Other Google Products
Google Ads
Linking GA4 and Google Ads can support:
Campaign reporting within Analytics
Audience sharing, subject to eligibility and consent
Advertising reports
Importing suitable key events as conversions
Cross-channel analysis
However, GA4 reporting and native Google Ads conversion tracking are not identical.
When Google Ads bidding is the primary requirement, we generally prefer a properly configured native Google Ads conversion action rather than relying exclusively on a GA4 import. GA4 remains valuable for cross-channel analysis, landing-page reporting and customer-journey analysis.
Be careful not to count the same action twice by importing a GA4 event while also recording an equivalent native Google Ads conversion as a primary goal.
Google Search Console
Connecting Search Console adds information about organic Google Search performance, including search queries and landing pages. It helps connect pre-click search visibility with post-click website engagement.
Google provides instructions for connecting Search Console with GA4.
Search Console and GA4 will not produce identical click, session or user totals because they measure different things and apply different processing rules.
Looker Studio
Looker Studio can turn GA4 data into dashboards tailored to stakeholders, clients or internal teams.
A useful dashboard might combine:
Website users and sessions
Channel performance
Landing pages
Lead or purchase events
Revenue
Google Ads performance
Search Console data
CRM outcomes
Our free GA4 Looker Studio report template provides a starting point for building a more accessible reporting view.
BigQuery
GA4 can export event-level data to BigQuery. This is useful when a business needs more advanced analysis, longer-term data ownership, custom modelling or integration with other data sources.
BigQuery is not necessary for every beginner, but enabling the export early can preserve raw event data for future analysis. Google makes the BigQuery export available for GA4 properties, subject to applicable limits and cloud usage costs.
GA4, PPC and Conversion Tracking
GA4 is particularly useful for comparing paid advertising with other marketing channels, but traffic reporting alone does not provide a complete view of PPC performance.
A reliable PPC measurement system may include:
Native advertising-platform conversion tracking
GA4 for cross-channel and website analysis
Enhanced conversion measurement
Call tracking
Ecommerce transaction data
CRM lifecycle stages
Offline conversion imports
Revenue and profit data
A reporting dashboard
For lead generation, the initial form submission is only the beginning of the commercial journey.
A campaign generating 100 leads at £30 each may appear stronger than one generating 50 leads at £45 each. If the second campaign produces substantially more qualified opportunities and sales, it may actually be the better investment.
This is why offline conversion tracking for Google Ads and CRM integration are becoming increasingly important. Advertising platforms need information about qualified leads, customers and revenue—not just form completions.
Enhanced conversions can also improve measurement by supplementing conversion events with consented, hashed first-party customer data. Learn more about enhanced conversion tracking for GA4.
Understanding Attribution
Attribution determines how credit for an important outcome is assigned across marketing interactions.
A customer might:
Discover the business through organic search
Return after seeing a social advert
Click a paid-search advert
Revisit the website directly
Complete a purchase
Different reports can assign credit differently because they use different scopes and attribution logic.
This explains why Google Ads, GA4, Meta Ads, a CRM and an ecommerce platform may report different conversion totals. They may use different:
Attribution models
Lookback windows
Event times
Click and impression data
User identifiers
Consent signals
Time zones
Counting methods
Deduplication rules
Do not expect every platform to match perfectly. The objective is to understand why the numbers differ and determine which system should be the source of truth for each decision.
For example:
Google Ads can be the operational source for Google Ads bidding.
GA4 can support cross-channel website analysis.
The CRM can be the source of truth for lead quality and sales progression.
The ecommerce or accounting platform can be the source of truth for completed revenue.
Common GA4 Mistakes
Installing the Tag Without Configuring Events
A base installation normally records page views and some automatically collected interactions. It does not automatically understand the business’s forms, bookings, lead quality or revenue.
Treating Every Button Click as a Conversion
A click on a submit button does not always mean the form was accepted. Validation errors, duplicate clicks and technical failures can create false conversions.
Where possible, trigger the lead event after a confirmed successful submission.
Counting Confirmation-Page Refreshes Repeatedly
If a conversion is based only on viewing a thank-you page, refreshing or revisiting that page may create duplicates. Use robust event logic and unique transaction identifiers where appropriate.
Failing to Test the Implementation
Use Tag Manager preview, browser diagnostics, Realtime and GA4 DebugView to confirm that:
Events fire at the correct time
Events do not fire twice
Parameters contain the expected values
No personal information is collected
Ecommerce values and currencies are correct
Consent choices are respected
Using Poor Campaign Naming
Inconsistent UTMs fragment campaign data and make comparisons unreliable. Maintain a central naming convention shared by everyone creating marketing links.
Relying on GA4 as the Only Revenue Record
Analytics is a marketing measurement platform, not an accounting system. Reconcile purchases and revenue with the ecommerce platform, payment processor and financial records.
Ignoring CRM Outcomes
Lead volume does not equal lead quality. Connect web enquiries with qualified leads, opportunities, customers and revenue wherever practical.
Assuming Missing Data Means No Activity Occurred
Consent choices, browser restrictions, ad blockers, implementation errors and identity limitations can all create gaps. Analytics data should be treated as measured evidence rather than a perfect record of every person and action.
A Practical GA4 Reporting Routine
Weekly Checks
Review:
Sudden changes in users or sessions
Channel and campaign performance
Key events and revenue
Landing-page performance
Tracking anomalies
Direct and Unassigned traffic
Device-specific problems
Weekly reviews are useful for detecting issues, but avoid making major strategic decisions from very small samples.
Monthly Analysis
Compare:
Marketing spend
Sessions and engaged sessions
Leads or purchases
Cost per conversion
Revenue and return on advertising spend
Qualified opportunities
Customers
Customer acquisition cost
Landing-page conversion rates
Add annotations or maintain a change log covering campaign launches, tracking updates, website releases, promotions and external events. This makes changes in the data easier to explain.
Quarterly Measurement Review
Periodically audit:
Tags and triggers
Events and key events
Google Ads conversion settings
Consent implementation
Referral exclusions
Cross-domain measurement
Internal traffic
Custom dimensions
Ecommerce data
CRM and offline conversion integrations
User access and permissions
Measurement systems deteriorate as websites, forms, platforms and marketing processes change. Regular validation prevents the business from optimising campaigns using inaccurate signals.
What Good Google Analytics Reporting Looks Like
An effective GA4 setup should provide more than charts showing traffic growth.
It should connect:
Marketing source
Campaign
Landing page
User engagement
Lead or purchase
Commercial quality
Revenue
For lead-generation businesses, the strongest reporting model combines GA4 with advertising-platform tracking and CRM outcomes. For ecommerce businesses, it combines GA4 with the ecommerce platform, payment records and product-level profitability.
The objective is not to collect the maximum possible amount of data. It is to collect accurate, relevant information that improves decisions.
Summary
Google Analytics 4 helps businesses understand how people discover, use and convert through their websites and apps. Its event-based model is more flexible than Universal Analytics, but it requires a considered measurement plan and careful implementation.
Beginners should focus first on:
Installing one accurate base tag
Configuring consent appropriately
Measuring genuine business actions
Using recommended event names
Designating only meaningful key events
Understanding User Acquisition and Traffic Acquisition
Reviewing landing pages and engagement
Linking relevant Google products
Testing every important event
Connecting website activity with sales and revenue
Once these foundations are reliable, GA4 can support more advanced funnel analysis, audience creation, advertising measurement, Looker Studio reporting, BigQuery analysis and CRM integration.
The most useful Analytics account is not necessarily the one with the most events or dashboards. It is the one that helps the business distinguish traffic from engagement, enquiries from qualified opportunities and reported conversions from genuine commercial results.