measuring traffic properly (GA4 basics)

measuring traffic properly (GA4 basics)

Accurate traffic measurement is the foundation of any sensible optimisation plan, and Google Analytics 4 is the modern tool to use for that purpose. This step-by-step tutorial walks through the essential GA4 set-up and verification tasks you should complete before trusting numbers for decisions. The goal is to reduce measurement errors, avoid inflated or missing sessions, and produce a reliable dataset you can use for SEO and growth analysis.

Step 1 is creating the GA4 property and data stream for your site. In the Admin area create a new GA4 property and add a Web data stream, noting the measurement ID supplied. Decide whether you will install the gtag snippet directly or manage tags through Google Tag Manager, and make a note of the stream-level settings such as enhanced measurement toggles. Keep naming consistent so you can identify the property and stream later when troubleshooting or comparing data across environments.

Step 2 covers tag installation and immediate verification. Add the chosen tag to your site and open GA4 Realtime to confirm events arrive within seconds, then use DebugView during development to inspect event parameters for individual sessions. If events do not appear, check for duplicate tags, blocked third-party scripts or consent banners preventing collection. Verifying early prevents days or weeks of flawed data that would otherwise affect trend analysis and campaign assessment.

Step 3 focuses on events and conversions rather than pageviews alone. Review the automatic events GA4 provides and create custom events where necessary to capture meaningful user actions such as sign ups, downloads and purchases. Use consistent event names and attach relevant parameters like value, currency and content_type, then mark the most important events as conversions so they surface in standard reports. Avoid creating multiple overlapping events that represent the same action, since that will fragment conversion counts.

Step 4 is about excluding internal and test traffic, which otherwise biases metrics like bounce rate and conversion rate. Define internal traffic rules in the GA4 Admin settings or use a query parameter or cookie during development to flag test sessions, then add a data filter to exclude them from reporting. If you are experimenting or running frequent QA, keep one unfiltered view for diagnostics and use filtered reporting for performance analysis, and remember to check our our SEO & Growth tag page for related guides and examples.

Step 5 deals with attribution and campaign tagging so traffic is counted to the correct sources. Apply consistent UTM parameters to marketing links and document a naming convention to avoid variants that split campaign data. Review GA4 attribution settings and conversion windows to match your business model, and set up cross-domain measurement if users move between related domains during a single journey. Proper campaign tagging and attribution settings ensure you can trust channel and campaign performance figures.

• Verify only one tag is firing per page to prevent double-counting sessions and events.
• Use DebugView during development and keep a short list of test cases for common user journeys.
• Document your event naming and UTM conventions in a short internal guide.
• Exclude internal traffic and retain an unfiltered property for troubleshooting.

Step 6 is establishing routine checks and building reports you will actually use in decision making. Create core explorations and a small set of standard reports showing acquisition, engagement and conversions, and schedule a weekly sanity check to ensure events are still firing and no unexpected spikes or drops have appeared. Watch for common pitfalls such as changes in site code that remove parameters, consent changes that block collection, and inconsistent event naming caused by multiple developers, and keep a log of any tracking changes so you can explain sudden metric shifts when they occur. For more builds and experiments, visit my main RC projects page.