How Does Google Analytics Work? (Complete Beginner's Guide).
Google Analytics shows you how people find and use your website. The version you use today is Google Analytics 4 (GA4). The old version, Universal Analytics, stopped processing data on July 1, 2023, and Google removed access to historical Universal Analytics data the week of July 1, 2024. If a guide still talks about "hits," "views," and `UA-` tracking IDs, it is describing a product that no longer runs. Everything below is GA4.
This guide explains how GA4 actually works: what it collects, how it sends that data to Google, and how to read the reports.
What is Google Analytics?
Google Analytics is a free measurement platform from Google. It records how visitors interact with your site and turns those interactions into reports you can act on.
Run an ecommerce store and you can see how many people visited, where they came from, which device they used, which products they viewed, and which steps they completed before buying. GA4 is the most widely used analytics platform on the web, so most teams already have a property to work with.
What Does Google Analytics Do?
GA4 answers the questions that drive business decisions. The core jobs:
- Measure how your site performs against goals you define.
- Show whether your marketing is working, channel by channel.
- Reveal which content earns attention and which products get viewed.
- Group users into audiences by behavior, device, location, and more.
- Track conversions so you can tie traffic to revenue.
You decide what counts as success. Mark a purchase, a form submit, or a demo request as a conversion (GA4 calls these "key events"), and the platform reports on them across every channel.
RELATED: How to Grant User Access in Google Analytics
How Does Google Analytics Collect Information About Visitors?
GA4 is built on an event model. This is the biggest change from Universal Analytics. In GA4, every interaction is an event: a page view is a `page_view` event, a scroll is a `scroll` event, and an outbound click, a video play, or a purchase each becomes an event with its own parameters. There are no separate "hit types" anymore. This single model is why GA4 measures websites and apps the same way.
Collection starts with the Google tag (`gtag.js`), a small snippet you add to your site, usually through Google Tag Manager. When someone loads a page, the tag fires, captures the relevant events, and sends them to Google's servers.
You connect the tag to GA4 through a data stream, and each web data stream carries a Measurement ID in the format `G-XXXXXXXXXX`. That ID, not the retired `UA-` number, is how GA4 knows which property the data belongs to.
Some events fire automatically through GA4's enhanced measurement: scrolls, outbound clicks, site search, video engagement, and file downloads. You can add custom events for anything specific to your business, such as a pricing-page view or a checkout step.
The data collected can include the page you are viewing, technical information about your device, how you arrived at the site, and the way you navigate it. GA4 sends that data to Google's servers, the same global infrastructure that runs the rest of Google's products.
GA4 is the most widely used analytics platform on the web, and Google built it for a privacy-first web.
Rather than collecting information about a specific person and tying it to their name, GA4 reports patterns across audiences. It does not log or store IP addresses, it supports consent mode so measurement adapts to the choices visitors make in your cookie banner, and it can model conversions when cookies are unavailable.
So GA4 will not tell you "Tim from Boston viewed three pages." It tells you that visitors from a given source, region, and device viewed three pages.
RELATED: Google Performance Max Checklist To Get You Ready
Why does any of this matter?
There are two takeaways from how GA4 collects data that matter to any site owner.
Visitors who block the Google tag, or whose browsers never run it, are under-counted in Google Analytics.
GA4 reports aggregated behavior, not deep individual session replay.
GA4 depends on the Google tag firing in the browser. Visitors who block scripts, use strict privacy tools, or decline consent will be missed.
Most modern computers, tablets, and phones run the tag by default. But strict privacy settings, ad blockers, and script blockers stop it. Those visitors never appear in your reports.
So if you need an exact count of exactly how many times your site has been accessed, GA4 alone will not deliver it. Pair it with server logs or a server-side tagging setup for a complete count.
GA4 can also miss a meaningful share of your traffic if your audience leans heavily toward strict-privacy or script-blocking users. If that describes your visitors, supplement GA4 with a server-log based measurement.
RELATED: Google Classroom: Online Virtual Learning
How important are the restrictions of Google Analytics?
Neither limit is a major drawback for most sites. GA4 remains the most widely used analytics platform on the web for good reason.
GA4's headline metrics describe engagement, not raw pageviews. Engaged sessions are sessions that lasted longer than 10 seconds, had a key event, or included at least two page views. Engagement rate is the share of sessions that were engaged. Average engagement time shows how long your site held attention. Events and conversions are the interactions you chose to track. Bounce rate still exists in GA4, but it is now the inverse of engagement rate, not the old Universal Analytics single-page-visit metric.
Google Analytics is an excellent tool to track customer behavior on your site and to measure the performance of Google Ads and SEO. You can set goals, measure conversions and conversion rates, and gather insights about traffic sources and how visitors move through your site.
For deeper qualitative insight, such as why users abandon a flow, a GA4 account alone may not be enough. Teams that want richer behavioral and user-experience data often add session-recording or heatmap tools alongside GA4.
