Lead Tracking After a Website Relaunch
Every confirmed lead counted once, per site, in four tools
Read case studyMost Google Analytics 4 (GA4) setups I inspect are technically “installed” and of little use: one tag on every page, a handful of default events, and a dashboard nobody trusts enough to decide anything with. My job is to close the gap between having analytics and getting answers from it.
This note covers how GA4 models data, what I put into a setup, the mistakes I run into most, and the steps I follow. It is one of four notes on the measurement stack, together with Google Tag Manager, Consent Mode V2, and Google Ads Conversion Tracking.
GA4 is event based, so you can track almost anything, which is also why so many implementations fall apart. Nobody decides up front what should be measured, so every campaign or feature adds a few events in its own style. A year later the property looks like this:
form_submit, formSubmit, and contact_form.The reports still load, so nobody notices. The problem surfaces later, when someone asks a hard question and the data cannot answer it.
Four building blocks make the rest of the setup easier to reason about.
Events
Everything in GA4 is an event: a page view, a scroll, a form submission, a purchase. Some are collected automatically, some come from enhanced measurement, and the rest are custom events you define.
Parameters
Each event carries parameters that describe it, such as the form name, the value of a purchase, or the plan a user picked. A parameter only appears in standard reports after you register it as a custom dimension or metric.
User properties
These describe the user rather than one action, for example customer type or membership level, and they are useful for segmenting audiences across sessions.
Key events
These are the events you mark as important to the business. GA4 used to call them conversions. They drive reporting and can be imported into Google Ads.
Most of a good setup comes down to deciding these four things on purpose: which events exist, which parameters each one carries, which user properties matter, and which events count as key events.
I build around the journey the business cares about, from first visit to conversion, instead of the default template. In practice that means:
generate_lead or purchase, I use it.The tracking plan turns the taxonomy into a document that developers and marketers can both check. For an illustrative lead generation site, part of it might look like this:
| Event | When it fires | Key parameters |
|---|---|---|
view_item |
A visitor opens a service or product page | item_id, item_category |
form_start |
A visitor interacts with a form for the first time | form_id |
generate_lead |
A form is submitted and the server accepts it | form_id, lead_type, value |
purchase |
An order is confirmed | transaction_id, value, currency |
generate_lead fires when the server accepts the form, so failed submissions never count as leads. Small definitions like that are what make the numbers line up with the CRM later.
GA4 sits at the end of the measurement chain and can only report what the layers before it let through.
Events reach GA4 through Google Tag Manager, and Consent Mode V2 decides whether they may be stored at all. The same events often become the conversions that Google Ads Conversion Tracking bids on, so a naming mistake in GA4 can turn into a bidding mistake in Ads.
The checklist I run before I call a GA4 setup done:
Bad tracking leads to bad decisions, usually before anyone notices the numbers are off. Budget goes to the wrong channel, a “high-performing” campaign turns out to be a tracking artifact, and the part of the funnel that drives growth stays invisible because GA4 was never set up to see it.
With a sound setup, a disagreement about a campaign can be settled by opening the report.
1. Audit
I review the current setup to find what is firing, what is duplicated, what is missing, and where the data disagrees with reality.
2. Map the customer journey
From first touch to conversion, and after conversion where it matters, for this particular business model.
3. Architect the tracking plan
I define the events, parameters, and key events, then build them in Google Tag Manager as a documented structure the team can maintain after I leave.
4. Validate
Every event is checked against real user behavior in DebugView and Preview mode before it ships.
5. Hand off
With documentation and reports that marketing, product, and finance can all read the same way.
If you want a second look at your setup, hire me.
Every confirmed lead counted once, per site, in four tools
Read case study8+ issues fixed in 2 days, every conversion verified
Read case studyOne event standard across every data flow
Read case studyNext step
See how I work and what it costs, or email me. I usually reply within one working day.