Tracking audit

By TienWave Labs - Published 2026-05-31 - Updated 2026-05-31

Example GA4 and GTM Check for a Small Business Website in NZ

This anonymised example shows the shape of a useful tracking check for a small NZ business website.

The point is not to collect every possible event. The point is to prove whether the site records the actions that matter commercially.

Container health comes first

A GTM container can be published and still fail to give the business useful measurement. The first check is whether the tag is detected, whether the live version is the expected version, and whether the container has urgent diagnostics.

Events should match real intent

  • CTA clicks on primary contact paths.
  • Contact form starts.
  • Successful contact form submissions.
  • Click-to-call and mailto actions where they matter.
  • High-intent service page views.

The form path needs a success signal

A form-start event is useful, but it is not enough. The business needs to know whether valid submissions are recorded after the form actually succeeds, not merely when someone clicks the submit button.

Key events should be business actions

GA4 key events should mark actions that represent commercial intent. Page views and scrolls can help diagnose behaviour, but they should not be confused with enquiries.

Recommended next actions

  1. Confirm GTM is detected with Tag Assistant.
  2. Confirm GA4 receives the expected contact and CTA events.
  3. Mark successful enquiry events as key events.
  4. Connect Search Console so page visibility can be read alongside lead actions.

Turn the guide into action.

If this matches what is happening on your site or workflow, send the rough version. The useful first step is usually a focused fix, not a big vague project.