Tracking audit: the complete checklist to know if your data collection is "healthy"

Tracking can be set up without actually being reliable. Between GA4 events, Google Tag Manager tags, the CMP, advertising conversions and analytics reports, there are many possible points of friction. A tracking audit is precisely what lets you check whether the data collected is consistent, usable and aligned with your business goals. In this article, we will see what a tracking audit is, why it matters and which actions to check in order to control the quality of your collection.

What is a tracking audit?

Before getting into the checklist, it is important to understand what we are really trying to check. The goal is not only to see whether “data is coming through”, but to know whether it is coming through correctly!

Definition

A tracking audit consists of analysing the quality of your data collection on a website or an application. It lets you verify that the expected events, conversions, parameters and user data are properly collected, correctly named and usable in your analytics tools or ad platforms. Concretely, a tracking audit can cover several elements:

• The GA4 events sent from the site.
• The tags and triggers configured in Google Tag Manager.
• The tracked Google Ads conversions, Google Analytics 4 or Microsoft Ads.
• The parameters sent with each event.
• Respect for user consent via the CMP or Consent Mode.
• The consistency between the tagging plan and the data actually collected.

The idea is simple: if your data is wrong, incomplete or poorly structured, your analyses will be too. And if your analyses are bad, your marketing decisions are likely to be as well.

To go further on the logic of events, you can also read the article dedicated to Google Analytics events to track based on your business.

Which tools should you check during a tracking audit?

A tracking audit is not limited to looking at the reports in GA4. You also need to check the tools that fire the tags, collect consent, receive conversions or use marketing data.

Depending on your setup, several tools may be involved:

• The analytics tools, such as Google Analytics 4, Matomo, Piano Analytics, Adobe Analytics, Amplitude or Mixpanel.
• The tag management tools, such as Google Tag Manager or another tag manager.
• The advertising platforms, such as Google Ads, Microsoft Ads, Meta Ads, LinkedIn Ads or TikTok Ads.
• The CMS and e-commerce platforms, such as Shopify, PrestaShop, WooCommerce or Webflow, because some important data can come directly from the site.
• The CMP, to check that user consent is properly respected before data is sent.
• The CRM, to compare the leads actually received with the conversions reported in the analytics or advertising tools.
• The dashboarding tools, such as Looker Studio, to check that the data used in the reports is consistent.

If you don’t use GA4 or if you are looking for a solution better suited to your constraints, you can also read the article dedicated to the 10 Google Analytics alternatives.

The goal is to follow the full journey of the data: from the action taken by the user on the site to its display in the reports. It is this global view that lets you identify collection errors, duplicates or gaps between tools.

Why audit your tracking regularly?

A tracking audit should not be carried out only at the initial setup stage. Data collection evolves with your site, your campaigns, your tools and your marketing needs. A website redesign, the addition of a new form, a change to the purchase funnel, a change of CMP or a new Google Tag Manager configuration can quickly create errors.

Some of them go unnoticed for several weeks, until the analytics reports become inconsistent.

Auditing your tracking regularly therefore lets you detect problems before they distort your decisions. This is especially important if you run paid acquisition campaigns, because advertising algorithms also use conversions to optimise performance.

A good audit notably lets you answer very concrete questions:

• Are the important actions on the site properly measured?
• Do conversions come through only once, without duplicates?
• Is the data consistent between GA4, GTM and the advertising platforms?
• Is user consent properly respected?
• Do the reports really allow you to make decisions?

In other words, running the diagnosis of your tracking is an analytics quality control step. It lets you move from an “installed” collection to a truly reliable one!

The complete checklist to audit your tracking

An effective tracking audit must be carried out step by step, starting from the important actions to measure through to the quality of the data in the reports. The goal is to spot the errors that can distort your analyses, your conversions or your marketing decisions.

1) Check the actions, events and conversions collected

The first step is to check the important actions actually collected. In a tracking audit, we are not only trying to know whether events come through in GA4: above all we want to know whether the right interactions are measured, at the right moment and in the right tools. Whether you use GA4, Matomo, Piano Analytics, Google Ads, Microsoft Ads or a CRM, the logic stays the same: each important action must be able to be linked to a business goal.

A submitted form, a purchase, a booking or a click on a phone number should not be treated as simple secondary interactions.

You need to compare what is collected with what should be collected. This is where a tagging plan audit becomes useful. Indeed, the tagging plan serves as a reference: it indicates the important actions to measure, the expected event names, the parameters to send and the triggering rules.

For example, for a lead generation site, the important actions could be:

• Submitting a contact form.
• Clicking on a phone number.
• Booking an appointment.
• Downloading a document.
• Signing up for a newsletter.

For an e-commerce site, you will instead check the steps of the purchase funnel: viewing a product, adding to cart, starting the checkout, payment and final purchase. If you work on this type of site, you can also read the guide dedicated to Enhanced E-commerce GA4 to better structure your e-commerce events.

The goal is not to track everything. Above all, you need to measure the actions that have business value. Too many useless events can make the reports hard to read, while a lack of important events prevents you from understanding what really drives performance.

2) Debug the tracking: test the tags, triggers and data sent

Once the important actions have been identified, you need to move on to the debug phase. This step lets you technically check what happens when a user performs an action on the site: click, form submitted, add to cart, purchase, sign-up or booking. We often talk about GA4 GTM debugging, because Google Analytics 4 and Google Tag Manager are very widely used, but the logic also applies to the other analytics, advertising or CRM tools connected to your site!

The goal is not only to see whether a tag fires. You also need to check that the right data is sent, at the right moment, to the right tool.

A tag may well fire in Google Tag Manager but send an incomplete event, a wrong parameter or a duplicate conversion.

In Google Tag Manager, Preview mode lets you see which tags fire, at what moment and with which variables. In GA4, DebugView lets you check whether the events arrive properly in the analytics property. For the other tools, you also need to use the appropriate testing solutions: Tag Assistant, Meta Pixel Helper, UET Tag Helper for Microsoft Ads, the Google Ads conversion diagnostics or the reports of your analytics tool.

At this stage, you notably need to check:

• The tag firing at the right moment.
• The consistency between the user action and the event sent.
• The presence of the right variables in the Data Layer.
• The name of the event sent in GA4 or in the tool concerned.
• The parameters sent with the event.
• The absence of duplicates for a single user action.
• Respect for consent before the data is sent.
• The proper reception of the event in the analytics or advertising tools.

This work can seem technical, but it is essential. For example, a form may be tracked on the click of the “Submit” button, while the actual submission then fails because of a forgotten required field. In that case, your data overestimates conversions and gives a distorted view of performance.

Another frequent example: a purchase event may come through correctly in GA4, but without a value, without a currency or with a missing transaction ID. The event does exist, but it becomes far less usable in the reports, especially to analyse revenue or optimise advertising campaigns.

Once the anomalies have been identified, you need to fix the configuration and then redo the same tests. It is this final check that lets you confirm that the error is really fixed and that the data sent is now reliable.

3) Check the consistency of the data in the analytics reports

After checking the actions collected and the technical firing of the tags, you need to check the quality of the data in the reports. This step lets you verify whether the data received is consistent, usable and aligned with business reality.

An event may well be sent correctly from the site but become hard to analyse afterwards. For example, a conversion may come through without a reliable traffic source, a purchase may arrive without a value, or a form may be recorded in GA4 without any information about the page or the type of request.

In analytics quality control, you notably need to check:

• Duplicate conversions or events.
• The gaps between tools, for example between GA4, the CRM and the advertising platforms.
• Missing or poorly filled parameters.
• Inconsistent values, such as revenue at zero or a missing currency.
• Collection breaks after an update of the site, GTM or the CMP.
• The readability of the reports for the marketing teams.

This is also the stage where you compare the analytics data with other sources of truth.

For an e-commerce site, you can reconcile the GA4 purchases with the real orders in Shopify, WooCommerce or PrestaShop.

For a lead generation site, you can compare the reported conversions with the leads actually received in the CRM.

The goal is not to get perfectly identical numbers everywhere, because each tool has its own logic of attribution and data processing. However, the gaps should stay understandable. If GA4 shows 200 submitted forms while the CRM only contains 80, you need to investigate!

4) Identify the hidden costs of bad tracking

Bad tracking often has invisible costs. It does not always cause an obvious breakdown, but it can gradually degrade the quality of your marketing decisions:

• If your conversions are poorly measured, your advertising campaigns may be optimised on the wrong actions.
• If your analytics reports are incomplete, you risk cutting off well-performing channels or investing more in low-return sources.
• If your e-commerce data is poorly sent, you can have a wrong view of revenue, average basket or user journey.

The impacts can be significant:

• A misdirected advertising budget.
• Campaigns optimised on the wrong conversions.
• Unreliable analytics reports.
• Time wasted looking for the source of the gaps.
• SEO, SEA or CRM decisions made on incomplete data.
• Difficulty identifying the actions that are really profitable.

This is precisely why a tracking audit should not be seen as a simple technical check. It also lets you secure the business decisions that depend on your data!

What to do after a tracking audit?

A tracking audit is only valuable if it leads to concrete actions. The goal is not only to produce a report, but to fix what prevents your data from being usable.

Prioritise the important fixes

Not all errors are equal; some completely block the measurement of conversions, while others are secondary optimisations.

After this expertise, you therefore need to prioritise the fixes. The problems that affect the main conversions, the advertising campaigns or the critical business data must come first. Naming adjustments, additional parameters or secondary events can come afterwards.

Good prioritisation helps you avoid wasting time on details while the most important data is not reliable!

Document the fixes in an action plan

Once the problems have been spotted, the goal is to build a clear action plan. For this analysis to be truly useful, you need to compile the detected anomalies in a shared document: Google Sheets, Notion, Airtable, Trello or even a simple Google Doc depending on how you work!

This document could for example contain:

• The problem detected.
• The tool concerned: GA4, GTM, CRM, CMP, advertising platform, etc.
• A concrete example or a screenshot.
• The possible impact on the data.
• The level of priority.
• The action to take to fix the problem.

This documentation lets you turn the audit into a real roadmap. It also makes exchanges easier between the marketing, data and development teams when a fix requires several people.

Set up a regular analytics quality control

Once the fixes have been applied, it is important not to consider tracking as “finished”. A collection can degrade over time, especially after a change to the site, Google Tag Manager, the CMP or a conversion funnel.

The idea is not to redo a full audit permanently, but to plan a regular quality control on the most important data: main conversions, key events, essential parameters and gaps between tools.

This control can be carried out every month or every quarter depending on your activity. It lets you quickly detect an anomaly before it distorts your reports or your advertising campaigns for several weeks!

FAQ - Tracking audit