Studio 46 Studio 46
Discuss a project
Menu

GA4 & GTM audits · New Zealand

GA4 & Google Tag Manager audits

Know which numbers you can trust before you use them to make a decision.

When analytics, advertising and customer records tell different stories, another report rarely resolves the problem. I review the measurement behind the numbers, test the agreed customer journeys and explain what the evidence can support.

Scope & deliverables

What you receive.

Marketing managers, business owners and agency teams who need an independent view of an existing setup.

  • A measurement brief

    The questions you need answered, the systems in scope and your definitions of an enquiry, conversion or customer.

  • A review of the setup

    An agreed review of GA4, Google Tag Manager and relevant website journeys, with advertising or CRM checks where included.

  • Evidence from selected journeys

    Documented checks that distinguish a click, an attempted submission and a confirmed action.

  • Findings in priority order

    What is unreliable, why it matters and which issues deserve attention first.

  • A practical next-step plan

    Recommendations your team or developer can use, with an explanation of open questions and limitations.

The audit is a defined diagnostic engagement. Repairs can be commissioned afterwards or handed to your developer. Any wider review of campaign profitability or business systems is agreed separately.

Why it matters

A useful decision at the end of the audit

You should be able to decide which reports are useful now, which decisions need better evidence and what to fix first. I connect technical findings to their consequences for enquiries, customers and reporting, so the work can be discussed with both developers and management.

Working together

How the work proceeds.

  1. Agree the questions

    We confirm the business questions, key journeys, access and the boundaries of the review.

  2. Inspect and test

    I inspect the configuration and test the agreed journeys, documenting the evidence and any gaps.

  3. Work through the findings

    You receive a written report and a discussion of the priorities and implementation options.

Anonymised work example

An example from practice.

In an independent review for a specialist service business, I found that website completion events did not provide a dependable count of confirmed customers. The delivered report separated the business definitions, test evidence and recommended repairs.

Read the example and its scope

Useful questions

Before we start.

Is this an automated GA4 audit?

Automated checks can help identify issues, but the work also considers your business definitions, website behaviour and the evidence behind your reports. The scope is agreed around the decisions you need to make.

Will you fix the issues as part of the audit?

The diagnostic scope and any implementation work are agreed explicitly. You can use the findings with your existing developer or ask me to scope the repairs.

What access do you need?

Usually access to the relevant GA4 property and GTM container, plus the website journeys in scope. Advertising, CRM or developer access may also be useful. We confirm what is needed before starting.

How much does an audit cost?

I quote after confirming the websites, properties, journeys and systems involved. You receive a defined scope and fee before the work begins.

Start a conversation

Tell me what needs to be clearer.

Describe the decision, the reporting problem or the journey you need to measure.

Discuss an analytics audit