Written by Sandra Lu, Head of Customer Solutions & Vicky Wong, Solutions Architect
TL;DR:
What should a GA4 audit actually check? Beyond tag firing, it should review implementation sources, duplicate pageviews and conversions, key event quality, parameter accuracy, event design, governance, and stakeholder alignment. The goal is to ensure your GA4 data is accurate, consistent, and usable for decision-making.
If you’ve ever looked at GA4 and thought “the numbers seem… off”, you’re not alone.
A lot of tracking issues don’t show up as obvious errors. Your GA4 can look stable for months while quietly collecting inflated, duplicated, or mislabeled data. This is why reviewing if events appear in DebugView isn’t enough as a GA4 audit. The objective is getting data that is accurate, consistent, and usable for decision-making.
Below is a practical checklist of what your analytics consultant should check in a GA4 audit, and why each area matters.
What a GA4 audit is (and what it isn’t)
A GA4 audit is not:
- “GA4 is installed, so we’re done.”
- “Events are firing, so tracking is working.”
A GA4 audit is:
- verifying how data is collected,
- confirming whether events and parameters are correct,
- identifying issues that potentially distort reporting, even if reports look “normal”
- creating a roadmap to fix the analytics structure so marketing, product, and agency teams can trust the numbers.
An analytics implementation on your site should just be one part of the job. The full scope of a GA4 audit should include measurement planning, implementation, QA and ongoing monitoring and maintenance.
What should actually be checked in a GA4 audit?
1- Review where the GA4 data is coming from
The first question to ask is: how is GA4 being implemented?
Your GA4 could actually be collecting data from more than one source simultaneously, like:
- a platform extension (like a WordPress plugin or Shopify app),
- a GTM container,
- and sometimes hard-coded scripts.
This is one of the most frequent causes of “everything looks fine, but numbers are inflated” because events can double-fire without anyone realising.
What your consultant should verify
- Which method is the “source of truth”
- Check for duplicate event firing.
- Whether responsibilities (e.g IT vs marketing vs agency) are clear
2- Page_view and auto events: are they firing once per intended action?
Pageviews and GA4’s auto-collected events are often assumed to be safe, but this usually isn’t the case. A common audit finding is that page_view (and related auto events) fire more than once due to overlapping setups. This can bloat sessions, engagement, and metrics while still looking “consistent” in trend lines.
What your consultant should verify
- page_view fires once per page load, and not twice via multiple systems
- auto events aren’t being triggered unexpectedly by site behaviour
3- Key events: are you tracking outcomes or noise?
One of the fastest ways to ruin GA4 decision-making is misconfigured conversions. We’ve seen cases where teams mark auto events like page_view or session_start as key events, which renders KPIs like engagement rate meaningless.
What your consultant should verify
- key events represent real business outcomes (e.g lead submit, purchase, signup, etc.)
- key events aren’t inflated by auto events or broad triggers
- key event definitions match how the business uses them
4- Purchase / lead events: are duplicates possible?
In terms of hygiene, it’s not enough to check whether a purchase event type is firing “correctly”. You should also test it under unusual situations like, if a user encounters an error on site.
A common example: lead events that can be triggered multiple times if:
- a user refreshes the confirmation page and the site sent a data layer event again
- or the trigger conditions are too broad.
If not checked, you could be in a situation where your revenue data looks great, but it’s not real.
What your consultant should verify
- purchase / lead events have safeguards against duplicates
- triggers are based on reliable signals (not just page load)
- event conditions are aligned with the site/app flow
5- Parameter accuracy: are you sending the right values and not just event names?
Many GA4 setups pass on the right event name, but wrong or incomplete parameters.
For example:
- revenue sent without currency,
- missing item-level data for ecommerce,
- wrong lead value,
- mismatched naming conventions that break reporting later.
This is where a proper audit catches problems that dashboards won’t show you until you start isolating performance by product, channel, or campaign.
What your consultant should verify
- parameter completeness for key events
- correct values and formats
- consistency across web/app and across markets (if applicable)
6- Event design: does the setup support marketing decisions?
A common mistake we find during GA4 audits is that the implementation is technically correct, but the collected data isn’t useful to marketing. This often happens when analytics is implemented by IT “by the book,” e.g using legacy structures or minimal transparency.
A consultant should audit whether the event model supports common questions marketers and agencies need to answer, such as:
- which content drives qualified intent,
- what actions represent a user’s progression through the funnel,
- and what can, and cannot be optimised via media.
7- Governance: can your company maintain the setup without breaking it?
The reality is that a good GA4 setup can still be obsolete over time. Contributing reasons can be: Tags get added, agencies change, websites get updated, people leave, and suddenly tracking becomes fragile. We’ve also had companies that don’t want to bother IT for every change, so fixes get delayed, or people avoid changing anything at all.
What your consultant should verify
- Is there a role in the company that can deploy changes
- Is there a tagging documentation and where is it stored
- approval process and change logging
- whether the setup is resilient to platform/site updates
8- Stakeholder alignment: will the fixes actually get implemented?
A solid audit often includes heavy coordination between marketing, IT, product, and agencies—because issues aren’t always technical. Operational challenges can come up as unclear ownership, unclear requirements, and misaligned priorities.
In practice, a good analytics partner should be a bridge of sorts by turning business goals into tracking requirements, and turning technical findings into an action plan people can execute.
Why marketers and agencies struggle may struggle with a GA4 audit
From our experience, it’s usually based on these 2 patterns:
1- Inherited setups
Agencies and new marketing teams often inherit a GA4 setup they didn’t design. Without an audit, it’s hard to validate whether the tracking is reliable—so optimisation becomes guesswork.
2- Underestimated effort
A proper audit isn’t a quick “check tags” job. Time depends on your stack, plugins, ecommerce platform, and how many stakeholders need to align before changes can happen.
What “good” looks like after a GA4 audit
After fixes are implemented, you should be able to say:
- “We trust our conversion numbers.”
- “Key events represent real outcomes—not noise.”
- “We can make tracking changes without chaos.”
- “New team members can understand what’s implemented and why.”
What you should invest in is a better Analytics foundation so your reporting and optimization is correct and secure, not muddied data.
A simple self-check: do you need a GA4 audit?
If any of these scenarios are occurring to you, you may need an audit.
- metrics suddenly spiked after a site change, without a real marketing reason
- conversions look inflated or inconsistent
- you’re not sure how GA4 is implemented (e.g plugin vs GTM vs hard-coded)
- you inherited a setup but you don’t fully trust it
FAQ
What should a GA4 audit actually include?
A proper GA4 audit should review more than whether tags are firing. It should check implementation method, duplicate event risk, pageview accuracy, key event quality, parameter completeness, event design, governance, and whether the setup supports reporting and optimisation.
How do I know if my GA4 setup needs an audit?
You may need a GA4 audit if conversions look inflated, metrics changed after a site update, reports do not match business reality, or your team is unsure how GA4 was implemented. Inherited setups and multi-platform tagging are also common reasons to audit GA4.
Why is checking ‘is it firing?’ not enough in GA4?
Because an event can fire and still be wrong. GA4 can collect duplicated, incomplete, or misleading data even when everything appears normal in DebugView or reports. A useful audit checks data quality, not just whether data is being sent.
What is the goal of a GA4 audit?
The goal of a GA4 audit is to make sure your analytics data is accurate, consistent, and usable for decision-making. A good audit helps marketing, product, and agency teams trust the numbers, fix tracking issues, and maintain a more reliable measurement setup over time.