Analytics and tracking
What is a GA4 tracking audit, and what does the report look like?
A tracking audit tests what your site actually sends to GA4 and Tag Manager, and reports each check as pass or fail with a prioritised list of fixes. It is for sites that already have tracking but where you doubt the numbers.
Published . Last updated . By Hevaris.
What does a tracking audit check?
A tracking audit checks the places where tracking commonly goes wrong: tags, events, key events, filters, referrals, campaign links, Search Console and consent. Each check is tested on your live site and recorded as pass or fail.
| Check | What is tested | How it is tested |
|---|---|---|
| Duplicate or missing tags | Whether each page loads the tags it should, and only once | Tag Manager Preview and the page source |
| Key events | Whether each important action sends an event and is marked as a key event | Triggering the action and watching GA4 DebugView |
| Internal-traffic filter | Whether your own visits are excluded | The traffic rule and the data filter state |
| Referral exclusions | Whether unwanted referral domains are excluded | The referral exclusion list |
| Campaign link consistency | Whether utm values follow one naming rule | The tagged links you supply |
| Search Console link | Whether GA4 and Search Console are linked | The link and its reports |
| Consent behaviour | Whether tags respond to the visitor’s choice | A visit with consent accepted and one declined |
What does the report look like?
The report lists each check with its result, a priority and the fix. The table shows the layout.
Example format, not client data.
| Check | Result | Priority | Fix |
|---|---|---|---|
| Form submission event | Pass | None | None needed |
| Phone click event | Fail | High | Add the trigger and event tag, then test again |
| Internal-traffic filter | Fail | Medium | Define the addresses and create the filter in testing state |
| Search Console link | Pass | None | None needed |
Real results use the same layout with your checks, your findings and your fixes in priority order. A failed check always comes with a fix, and a passed check says what was tested.
What do I need to give you?
You need to give access by invitation, and a list of the actions that matter to your business. We do not ask for passwords.
- Read access to the GA4 property and the Tag Manager container, by inviting Hevaris as a user. Google lets an administrator invite people by email address and remove them later.
- The actions you care about, such as enquiry form submissions and phone, email or WhatsApp clicks.
- Your consent tool, if you use one, so consent behaviour can be tested.
- Your tagged campaign links, if you use any, for the naming check.
What happens after the report?
You get a prioritised fix list and decide what to do with it. You can fix the items yourself, give the list to your developer, or ask Hevaris for a setup quote.
What is outside an audit?
An audit does not include online purchase tracking, ad campaign management, server-side tagging, or legal advice on consent. The full list is on the what we do not take page.
The audit is also not a promise of more leads, better rankings or perfectly accurate data. No analytics tool records every visit, and an audit shows what your setup does record.
What sources does this guide use?
The primary sources are linked below, so each statement can be checked at its origin.
Frequently asked questions
Do you need my passwords for a tracking audit?
No. You keep the GA4 property and the Tag Manager container under your own Google account and invite Hevaris as a user. Hevaris is removed when the work ends, and you keep full ownership.
Does the audit change my tracking?
The audit is a report. It lists what passes, what fails and what to fix first. Changes are made only if you ask for them, and are quoted separately.
Is the sample report real client data?
No. The table below is an example format, not client data. It shows the layout of a report so you can see what you would receive. It is not a result from any real site.
What if the audit finds the setup needs rebuilding?
Then the report says so, and you can move to a setup quote. You are not obliged to. The fix list is yours to use with Hevaris, with another adviser or with your own developer.