To set up GA4, create a property, add a web data stream, install the measurement tag through Google Tag Manager or your site, then configure your events, mark the important ones as conversions, link Search Console, set data retention and test everything in DebugView before trusting reports.
- One GA4 property can hold several data streams, but keep test data separate.
- Enhanced measurement collects many basic events automatically.
- Define business goals first, then mark matching events as conversions.
- Test with DebugView and Tag Assistant before relying on any report.
- Document your naming and review access, retention and filters regularly.
What do you need before starting a GA4 setup?
Before touching settings, write down what the website is for and what counts as success. For a service business this may be enquiry form submissions, calls and WhatsApp clicks. For a store it is purchases and add-to-basket actions. A GA4 setup is only useful if it measures actions that matter to the business, and that list should come first.
You will need a Google account with access to the site, the ability to edit the website or a tag manager, and a clear owner for the analytics account. Using a company-controlled account rather than a personal one avoids lost access later. Google changes the interface regularly, so menu names below may differ slightly from what you see.
How do you create a GA4 property and data stream?
Work through the steps in order.
1. Create the account and property. In Google Analytics, create an account (usually one per organisation) and a GA4 property inside it. Set the correct time zone and currency, since these affect reporting.
2. Add a web data stream. Enter your website address and name the stream clearly. Google generates a Measurement ID beginning with G-.
3. Review enhanced measurement. This feature can automatically record events such as page views, scrolls, outbound clicks, site search, file downloads and some video interactions. Switch off anything that does not fit your site.
4. Install the tag. The cleanest method for most sites is Google Tag Manager: add the GA4 configuration tag with your Measurement ID and fire it on all pages. Alternatively, paste the Google tag directly into your site's head section. Use only one method to avoid double counting.
A frequent beginner mistake is installing the tag twice, once through a plugin and once through Tag Manager, which doubles page views. After installing, view the page source or use Tag Assistant to confirm only one GA4 tag loads.
5. Handle consent. If your audience includes regions with consent rules, connect your cookie banner so tags respect user choices. Check current guidance for your markets.
How do GA4 events work, and which should you set up?
In GA4 everything is an event: a page view, a click, a form submission, a purchase. Events can carry parameters that add detail, such as the button text or the value of an order. There are four broad groups: automatically collected events, enhanced measurement events, recommended events with names Google suggests, and custom events you define.
Use recommended names where one fits, for example generate_lead or purchase, because they work better with standard reports. For everything else, create a simple, consistent naming convention using lowercase and underscores, and record it in a shared document.
A starter event list for a lead generation site
Track form submissions, click-to-call links, WhatsApp or email link clicks, brochure downloads and key button clicks such as 'book a consultation'. Our guide to conversion tracking for lead generation walks through forms, calls and WhatsApp in detail.
A starter event list for an online store
Track view_item, add_to_cart, begin_checkout and purchase, with product details and value parameters. Most store platforms offer an official integration or app, which is usually safer than hand-written code. Verify the data against your store's own order reports.
How do you mark conversions in GA4?
The idea is simple: choose the events that represent real business outcomes and mark them as conversions so they appear in conversion reporting and can be imported into Google Ads.
Be selective. A site with twenty conversions has none. Pick one to five that reflect genuine value, such as a submitted enquiry form or a completed purchase, and leave softer actions like scrolls as ordinary events. Where possible, pass a value so you can compare channels by worth rather than only by volume.
Consider creating a separate property or data stream for testing and staging sites, so experiments and developer visits do not pollute live reports. At minimum, filter out known test hostnames.
If you run paid campaigns, link your Google Ads account and import the conversions you want to optimise towards. Our PPC advertising service relies on exactly this kind of clean measurement.
Which settings should you configure in the first week?
A few admin settings prevent common problems later.
- Data retention. Check the event data retention period and set it to the longest option available for your property type.
- Internal traffic. Define your office IP addresses and create a filter so staff visits do not distort data. Test the filter before activating it.
- Referral exclusions. Add payment gateways or other domains that send users back to your site mid-journey, so they do not appear as new sessions.
- Search Console link. Connect Search Console to see organic queries and landing pages alongside behaviour data.
- Google Ads link. Connect if you advertise.
- User access. Give team members and agencies only the roles they need, and keep at least two administrators.
How do you test and maintain your GA4 setup?
Test before you trust. Open DebugView in GA4 and use Google Tag Assistant or Tag Manager's preview mode to watch events fire as you click through the site. Submit a test form, trigger a call click and, on a store, complete a test order. Confirm each event name, its parameters and that it appears once, not twice.
Then check real-time reports, and after a day or two look at standard reports to make sure data is flowing. Expect some processing delay and some differences from other tools, since each system counts a little differently.
Finally, keep a one-page measurement plan: business goals, event names, which are conversions, who owns them and when they were last tested. Recheck after any site redesign, plugin update or cookie banner change, since these are the usual causes of silently broken tracking.
Finally, learn a handful of reports before exploring everything. Start with acquisition reports to see where visitors come from, the pages and screens report to see what they read, and the events and conversions views to see what they do. Build a small set of saved explorations for the questions you ask every month, such as which channels produce the most enquiries.
If you would rather not do this alone, our web analytics service covers setup and audits, or you can contact us for a review of your current property.
Frequently asked questions
Do I need Google Tag Manager to use GA4?
No, you can add the Google tag directly. Tag Manager is usually easier to maintain because you can add and edit events without changing site code each time. Whichever you choose, use only one method to avoid duplicate data.
What is the difference between an event and a conversion in GA4?
An event is any recorded interaction, such as a click or page view. A conversion is an event you mark as important to the business, such as a form submission or purchase. Mark only genuinely valuable actions.
Why do GA4 numbers differ from other tools?
Different tools define sessions and users differently, treat consent and ad blockers differently, and process data on different schedules. Small differences are normal. Large gaps usually point to a tracking fault, so test your tags and compare against actual orders or enquiries.
