Free tools Windows power users keep installed
One-click scans. No signup required.
To track website traffic and conversions, set up an analytics property and web data stream, add the tracking tag, review pageviews and traffic-source dimensions, and record important actions as events. Then verify those events in Analytics and configure tags to respect visitors’ consent choices.
Decide what you want to measure
Start with the questions your site needs to answer. For traffic, that might mean which pages people view or which sources bring visitors to the site. For conversions, identify actions that matter to your business, such as a completed lead form, an order, or a qualified signup. Define what counts as completion before configuring tracking so that the event represents a meaningful outcome.
As an Amazon Associate I earn from qualifying purchases.
Use a consistent name for each action. If the same outcome is recorded under several different event names, it can become harder to interpret reporting. Google distinguishes recommended events from custom events; use an applicable recommended event where it fits, and define a custom event when the action calls for one. Google’s GA4 event guide describes how to set up both.
Create a Google Analytics 4 web setup
GA4 setup involves an Analytics account, a property, and a web data stream. You then need to tag the website so it sends data to that stream. Google’s GA4 setup guide explains the account, property, and stream steps.
#1 Best Overall
You can configure events using Google tag code or Google Tag Manager. Google recommends Tag Manager as a way to make tagging configuration changes more easily without editing site code for every change. The right installation steps depend on your website platform and any tags already in place; avoid adding a second implementation that duplicates existing tracking. See Google’s Tag Manager documentation for its role in managing tags.
Use pageviews and traffic sources to understand visits
Page activity
GA4 records page loads with the page_view event. For standard websites, pageviews are automatically collected; enhanced measurement can also trigger a pageview when browser history state changes. Check your site’s behavior and measurement settings so you understand which navigation actions generate pageviews. Google describes these behaviors in its pageview documentation.
Acquisition
Traffic-source dimensions help describe where traffic originated and the methods or marketing efforts associated with a visit. Choose dimensions that match the question you are investigating, such as the source or campaign behind visits, and compare equivalent date ranges using consistent metrics. These dimensions help organize acquisition data; they do not guarantee that every visit will have a source attribution. Google explains the available concepts in its traffic-source dimensions guide.
Track conversions as events
For each business action, specify the condition that means it is complete, then send an event when that condition occurs. For example, a lead-form conversion should represent a successful submission rather than merely a click on the submit button. An order event should correspond to the intended completed purchase state.
Implement the event with Google tag code or Google Tag Manager, using a recommended event when appropriate or a custom event for a site-specific action. Add parameters when context makes the data more useful: parameters are key-value pairs that can describe details such as a transaction value or an interaction type. Include only information needed for analysis, and do not send sensitive personal information in event data. Google’s event parameter guide explains how parameters provide additional context.
Test that tracking works as intended
- Perform the action: Use the site as a visitor would, completing the form, purchase, or other action you have defined.
- Check event activity: Look in the Analytics Realtime report and DebugView to see whether the event arrives. Google identifies both as places to observe events in its event documentation.
- Inspect the details: Confirm the event name and any parameters match the naming and context you intend to report.
- Check firing conditions: Confirm the event fires once for the intended completed action, rather than on an earlier step or multiple times.
These checks validate the behavior you observe during testing; they are not a substitute for monitoring the implementation as the site changes.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Configure analytics around consent choices
Google consent mode communicates consent choices to Google tags and affects their behavior. In a basic implementation, tags are blocked until consent is granted. In an advanced implementation, tags load with default settings and adjust their behavior when consent changes. The two approaches therefore differ in when tags load and how they respond. Google outlines the options in its consent mode overview.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Consent mode is a technical feature, not a determination that a website complies with privacy law. Applicable obligations depend on the site’s jurisdiction, data, and implementation; consult relevant legal and privacy guidance for your circumstances.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
