Before the redesign.
Carry the measurement requirements into the new website.
MVA / TRACKING
GA4 and GTM tracking implementation and repair.
I help marketing teams and agencies implement or repair tracking for the outcomes they need to measure. We agree on the events and journeys in scope, which changes I make, and where your developers or other partners need to be involved.
Discuss tracking work
When tracking needs attention
- A new website or journey needs measurement.
- Conversions appear to be missing or counted more than once.
- You have inherited a GA4 property or GTM container.
- A website or platform change needs its tracking checked.
THE DELIVERABLE
What you receive
Depending on the scope, you receive implemented tracking changes or implementation requirements, documented event definitions, and validation of the agreed journeys. We review what changed and any remaining limits together.
- Agreed changes or requirements
- Documented event definitions
- Validation evidence and remaining questions
Who makes the changes?
I make the changes we agree belong with me. Your developers or other partners may handle website code, form behavior, platform settings, or permissions outside that scope.
We identify those responsibilities before implementation. Requirements should tell the person doing the work what to change and how we will check it, with a named owner for each next step.
How we check the result
The check starts with the business outcome and follows it through the website, the tracking configuration, and the data destination. We review the journeys in scope and retain the evidence behind the handoff.
The outcome
An inquiry accepted by the website.
What your team wants to count.
The definition
Record success after the form is accepted.
Agree on when the event should fire.
The journey
Follow a successful inquiry and a rejected attempt.
Observe the agreed paths, including failures.
The evidence
Check the event, destination, and recorded result.
Document what worked and any remaining limits.
This is an example of the method, not a client result. A successful check of one journey does not establish that every event is correct.
When an audit should come first
If the cause or scope of the problem is unclear, an audit can establish what is happening before we agree on repairs. If the requirement is already clear, implementation can be the starting point.
What needs to be measured or repaired?
Tell me about the journey, the platforms involved, and what your team needs to count.