Analytics
GA4 Implementation Built Around the Questions Your Business Needs Answered
A GA4 property is easy to create and hard to get right. I design it from a measurement plan - what you need to know, what has to be counted to know it, and how - then implement, test and document every piece so it keeps working after launch day.
- years in SEO
- 6+
- client websites worked on
- 60+
- person doing the work
- 1
When a fresh GA4 implementation makes sense
A GA4 implementation is the design and build of a Google Analytics 4 property from a written measurement plan, and three situations call for one rather than a repair. The first is a new site or a new business with nothing to inherit. The second is a relaunch: a redesign, a move to a new CMS or store platform, or a merger of several sites into one. The third is a property so tangled that fixing it would cost more than starting over - wrong account ownership, events named by four different agencies, years of staff traffic mixed in with customers.
If you are not sure which of those applies, the honest answer is often an audit first. A property with a sound structure and a handful of faults should be repaired, not replaced, because a new property starts with no history. That decision belongs to a GA4 audit, and I will not sell you a rebuild the audit does not support.
Setup suits businesses that intend to use the data: to decide where marketing budget goes, to judge whether new pages produce enquiries, or to give ad platforms an accurate signal to bid against. If the site is a brochure that nobody plans to market, a basic install is fine and you do not need me for it.
Key takeaways
- The measurement plan comes before any tag. It turns business questions into a short list of events, parameters and key events.
- Property design decisions - streams, domains, retention, identity, custom dimensions - are cheap to make at the start and painful to change later.
- Key events should be few and commercial. Everything else is tracked as supporting behaviour, not counted as success.
- A setup is finished when it is tested in the browser, reconciled against a real enquiry or order, and written down.
- Relaunches and replatforms are the best time to implement, because the data layer can be specified alongside the build.
What's included in my GA4 implementation
Each part below is a few minutes of thought at the start and a real headache to reverse once data has been collected. I walk through them with you rather than picking defaults.
A measurement plan that turns business questions into a short event list
One or two working sessions with the people who will use the numbers, not only whoever manages the website. We list the decisions the data must support, agree what counts as success and define each outcome in plain words - a lead is a submitted, validated form, not a click on the submit button. The table further down shows what the result looks like for a service business.
- Decisions and questions the data must answer
- Success definitions in plain language
- Events, parameters and key events per question
- Google's recommended event names wherever one exists
Account ownership and property structure decided before any data arrives
The GA4 account sits under a company Google login you control, with agencies and freelancers added as users; properties created inside an agency's account are the most common reason businesses lose their history. A single website normally gets one property and one web stream. Separate brands, markets run by separate teams or an app alongside the site change that, and staging sites stay out of production data entirely.
- Company-owned account, access granted by role
- Property and data stream structure
- Staging and test sites excluded
- Room for an app stream if you have one
Retention, identity and traffic filters set so a full year can be compared
Event data retention goes to the longest option your property allows, so explorations can compare one season with the last. Google signals and reporting identity are chosen with your consent approach and reporting needs in mind. Internal traffic rules, unwanted referrals and the list of domains that share journeys are set and recorded, along with time zone, currency and session timeout.
- Event data retention
- Google signals and reporting identity
- Internal traffic rules with active filters
- Unwanted referrals and cross-domain domains
Events, custom dimensions and the few key events worth counting as success
Only the parameters you will report on are registered as custom dimensions, because standard properties limit how many you can create and a dimension only collects from the day it is registered. High-cardinality values such as unique IDs belong in BigQuery, not standard reports. Key events stay few and commercial: an enquiry, a booking, an order. For online stores the plan includes GA4's recommended e-commerce events from product view through to purchase.
- Event dictionary with trigger conditions
- Custom dimensions for reported parameters only
- Key events limited to commercial outcomes
- Recommended e-commerce events for stores
- Audiences built from the plan
Campaign naming rules and channel groups agreed before the first campaign runs
A short UTM convention is agreed up front, so email, social and partner traffic lands in a sensible channel instead of Unassigned. Where your marketing mix does not fit the default channel definitions, custom channel groups are added. The convention is written down with worked examples, because whoever builds next quarter's newsletter links will not have been in the planning session.
- UTM source, medium and campaign rules
- Worked examples for each channel you use
- Custom channel groups where needed
Google Ads, Search Console and other product links connected from day one
Google Ads, Search Console, Merchant Center and BigQuery are linked where relevant. On the ads side, auto-tagging is confirmed so paid clicks are attributed correctly from the first day, and key events are ready to import as conversions. The Search Console link gives search traffic its query view next to GA4's landing page data, with its reports published to the library so people can find them.
- Google Ads link and auto-tagging
- Search Console link with published reports
- Merchant Center and BigQuery where relevant
A tested Tag Manager build for GA4, handed over with full documentation
Most builds run through Tag Manager using the Google tag and GA4 event tags, named and foldered to a written convention, with the data layer pushes your developers add specified field by field. Every event is checked in DebugView on desktop and mobile with consent accepted and declined, then a real test enquiry or order is followed through to confirm it appears once, with the right source.
- Google tag and GA4 event tags in a tidy container
- Data layer specification for developers
- Test log and a reconciled test conversion
- Updated specification and a short training session
Experience
GA4 Implementation from someone who has done it many times
You work with me from the first call to the last report. No account managers, no hand-offs to a junior team.
Book a free call- years in SEO
- 6+
- client websites worked on
- 60+
- documented case studies
- 35
What this is not
Setup is the design and build of GA4 itself
Reviewing a property you already have is the audit. Untangling a container that holds years of other vendors' tags is Google Tag Manager work, though a new setup includes a tidy container for the GA4 tags it adds. Running your ad campaigns and deciding what your cookie policy permits stay with your ads team and your legal adviser.
From business question to GA4 event
This is the core of the measurement plan, shown here for a service business. Each row starts with something a person in the business wants to know and ends with exactly what gets implemented.
| Question the business asks | What has to be counted | Implementation | Key event? |
|---|---|---|---|
| Which pages and channels produce enquiries? | Confirmed form submissions, by form | generate_lead with a form name parameter, fired on the success state | Yes |
| Do people call instead of filling in the form? | Clicks on phone links, by page | Custom event with the number clicked and the page it was on | Usually yes, flagged as a softer signal |
| Which services attract the most interest? | Views of service pages, grouped by service | Page grouping parameter pushed through the data layer | No |
| Does the pricing calculator help or distract? | Calculator started and completed | Two custom events with the option chosen as a parameter | No - used in comparisons and audiences |
| Are booked consultations coming from search or ads? | Booking confirmations from the scheduling tool | Custom event on the confirmation step, cross-domain tracking if the tool is hosted elsewhere | Yes |
| Which content gets read rather than skimmed? | Engaged reading of articles | Enhanced measurement scroll plus engagement time, reviewed against article type | No |
Event names in the real plan follow GA4's recommended events wherever one exists, so reports and ad platform imports recognise them. Custom names are used only where Google has no recommended equivalent.
Free review
Get a free GA4 Implementation review
Send me your site. Before the call I look at your rankings and pages, then tell you what I would fix first and what it is likely worth.
The implementation process
For a typical service or B2B site this runs over three to five weeks, depending on how much developer work the data layer needs.
- 1
Measurement planning session
Working sessions with the people who use the numbers. The output is a measurement plan they have read and agreed, not a document only the analyst understands.
- 2
Property design
Account, property, streams and settings created in your company's name, with every choice recorded alongside the reason for it.
- 3
Technical specification
Every event, parameter and data layer push written out with the exact trigger condition, so developers know what to build and testers know what to expect.
- 4
Build
Tags, custom dimensions, key events and product links configured in a separate Tag Manager workspace, so nothing reaches the live site untested.
- 5
Test and reconcile
DebugView checks across devices and consent states, then a real enquiry or order traced from click to report.
- 6
Launch, compare, document
If an old setup exists, both run side by side for a short period so differences are understood before the old one is switched off. The specification is updated to match what shipped.
Planned implementation versus the tag-first install
Most GA4 properties I meet were set up by adding the tag and switching everything on. It works, in the sense that numbers appear.
Tag first, think later
- Measurement ID pasted into a theme field or plugin
- Every enhanced measurement option on, nobody checks what it catches
- Key events picked by whoever happened to set it up
- No record of what any event means
- Property owned by an agency or an individual's account
- Problems found months later, with no way to fix the history
Plan first, then tag
- A written plan agreed with the people who use the data
- Automatic events kept only where they measure something reliably
- Key events limited to outcomes with commercial value
- An event dictionary anyone in the team can read
- Ownership with the business, access granted by role
- Every event tested and reconciled before the launch date
Mistakes I design out from the start
Counting intent as success. A click on a submit button is not a lead, because forms fail validation, spam filters reject entries and people double-click. Events fire on the confirmed state - a success message, a thank-you page reached from the form, or a data layer push from the form handler.
Forgetting the journey leaves your domain. Booking tools, payment pages and application portals on other domains break sessions unless cross-domain measurement is set up and tested. I map every point where a visitor leaves the main site before writing the specification.
Leaving personal data in URLs. Some form tools append names or email addresses to the confirmation URL. GA4 offers data redaction for email addresses and chosen query parameters on web streams, but the better fix is to stop the data reaching the URL at all.
Where SEO meets CRO
Plan the events organic search will be judged on
Search traffic usually lands on guides, service pages and category pages rather than the homepage, so the plan includes page grouping and landing page reporting that let you see which organic entry points lead to enquiries. Supporting events such as calculator use or video views stay out of key events but give conversion work the behaviour data it needs, and the Search Console link gives SEO its query view alongside it.
Timing, access and what I need from you
Plan for three to five weeks on a typical site and longer for complex journeys, several domains or a platform migration happening at the same time. The planning sessions need the people who will use the data, not only the person who manages the website.
I need admin access to GA4 (or the ability to create the property under your account), publish rights in Tag Manager, a developer contact for any data layer work, and a way to place a test enquiry or order. If your sector handles sensitive information - health, finance, children - say so at the start, because it affects what should be collected at all, and your legal adviser should sign off on the plan.
If the setup is part of a redesign or replatform, bring me in while the build is still being specified. The tracking plan should sit inside the SEO migration checklist so both are checked at launch.
What usually comes next
A sound property is the start, not the finished product. Once a few months of data have built up, a short check against the plan - the same reconciliation used in a GA4 audit - confirms nothing drifted after launch. If other teams keep adding pixels, the governance rules from Google Tag Manager work stop the container filling up again.
With enquiries and orders measured properly, SEO can be judged on the pages that produce leads rather than on traffic alone. The Google Analytics consulting overview shows how the three services connect.
Growth from real projects
Learn more about ga4 implementation
GA4 Implementation FAQs
How long does a GA4 implementation take?
Three to five weeks for most service and B2B sites, from the first planning session to documented launch. Online stores, sites spanning several domains and projects tied to a replatform take longer. The biggest variable is usually developer availability for data layer changes rather than the GA4 work itself.
Can you set up GA4 without Google Tag Manager?
Yes, by adding the Google tag directly to the site, and for very simple sites that can be enough. I recommend Tag Manager for most businesses because it lets events be added, tested and changed without a code release each time, and it keeps every marketing tag in one place.
Will a new GA4 property lose our historical data?
A new property starts empty; GA4 cannot import history from another property. That is why I only recommend a fresh build when the old data is unreliable or the old property is unusable. Where possible both run in parallel for a while, and old reports can be exported for reference.
What is the difference between an event and a key event?
An event is any interaction GA4 records, such as a page view, scroll or form submission. A key event is an event you have marked as important to the business, so GA4 reports it separately and it can be imported into Google Ads as a conversion. Most sites need only a few.
Do you set up GA4 for apps as well as websites?
I focus on websites. A GA4 property can hold app streams alongside a web stream, and I will design the property so app data fits cleanly if you have one, but app instrumentation itself is work for your mobile developers using the Firebase SDK.
Who owns the property after you build it?
You do. The property sits in an account under your company's Google login, with my access granted as a user that you can remove at any time. All documentation is yours as well, written so another analyst could pick up the setup without speaking to me.
Planning a GA4 implementation for a new site or relaunch?
Book a free 30-minute call while the project is still being planned. Tell me how the site makes money and which tools sit around it, and I will outline what the measurement plan should cover and where the tricky parts of your journey are likely to be.