GA4 can be collecting data every day and still give you numbers you can't confidently use.
A duplicate GTM tag, an event firing under the wrong conditions, missing ecommerce parameters, or an incorrect consent configuration can all compromise your reporting. These problems are often difficult to spot because GA4 continues collecting data that looks reasonable.
If you rely on GA4 for campaign reporting, conversion measurement, client reporting, or ecommerce analysis, the quality of your setup matters as much as the reports themselves.
Keep reading for seven common GA4 and GTM mistakes that affect data accuracy, and how to fix them.
1. Duplicate GA4 Tags and Events
Duplicate tracking is one of the most common ways GA4 data gets inflated. Within GTM, multiple tags or overlapping triggers can fire the same event more than once.
If you sense the numbers are higher than expected, it might be that your GA4 property is installed both directly on the website and also via GTM. A plugin or ecommerce platform might also send events independently of GTM.
This can inflate:
- Users and sessions
- Events
- Key events
- Purchases
- Revenue
Start by checking: Multiple GA4 installations, duplicate event tags, overlapping triggers, and events sent by both your website platform and GTM.
2. Incorrect GTM Triggers and Event Tracking
A tag can be configured correctly and still send inaccurate data when its trigger is too broad. The event appears in GA4, but it doesn't represent the business action you're trying to measure.
For example, a lead conversion might fire when someone clicks a form button instead of when the form is successfully submitted. Or a purchase event might fire whenever someone visits a thank you page, including when an existing customer refreshes the page.
Start by checking: Triggers based on generic clicks, page views, URLs, or other conditions that don't reliably confirm the intended action.
3. Missing or Incorrect Data Layer Variables
GTM often relies on the website's data layer to pass information into GA4. When that information is missing, inconsistent, or mapped incorrectly, GA4 receives incomplete or inaccurate event data.
A purchase event, for example, could arrive without the correct revenue, currency, transaction ID, or product information.
This is particularly important for ecommerce, where GA4 uses both event-level and item-level parameters. A well-structured data layer provides a consistent source for the information passed to GTM and GA4.
Start by checking: Missing variables, incorrect mappings, inconsistent naming, undefined values, and data layer information that doesn't match the underlying transaction.
4. Consent Mode and Tag Firing Issues
Your consent management platform, GTM, and Google tags need to work together correctly.
Problems arise when consent defaults are configured incorrectly, consent updates reach GTM too late, or tags use inconsistent consent settings. GTM's Consent Initialization trigger is designed to establish consent settings before other tags fire.
Consent choices also affect how much data GA4 receives. When users decline analytics storage, observed data is reduced. Eligible GA4 implementations can use behavioral modeling to estimate some of the missing data, but accurate consent signals and sufficient data are required.
Start by checking: Consent defaults, consent updates, tag behavior before and after consent, and differences in implementation across geographic regions.
5. Incorrect Ecommerce and Revenue Tracking
If you run an ecommerce site, revenue tracking deserves particular attention.
Common problems include duplicate purchase events, incorrect revenue values, missing currencies, incomplete product data, and missing or inconsistent transaction IDs.
Transaction IDs help GA4 identify duplicate purchase events. Each completed order should pass a unique transaction ID with the purchase event.
Start by checking: GA4 purchases versus actual orders, transaction IDs, revenue and currency values, product information, refunds, and the conditions that trigger the purchase event.
6. Cross-Domain and Referral Tracking Errors
Your acquisition data becomes misleading when GA4 doesn't correctly recognize a user's journey across multiple domains.
This is common with booking engines, payment providers, ecommerce platforms, and other third-party services. Without proper cross-domain configuration, GA4 can treat visitors moving between domains as separate users or sessions, which affects attribution and session reporting.
Unwanted referrals and inconsistent UTM parameters can create additional attribution problems.
Start by checking: Self-referrals, payment or booking domains appearing as referral sources, broken cross-domain journeys, inconsistent UTM parameters, and internal traffic appearing in reports.
7. Outdated Tracking Code and Incorrect Key Events
Older tracking code can continue affecting your measurement setup after a website migrates to GA4 or changes its tracking strategy.
This includes Universal Analytics tags, advertising pixels, plugins, and duplicate tracking code left behind from previous implementations. These remnants add unnecessary complexity and can contribute to duplicate events or conflicts with current tracking and consent configurations.
Your GA4 key events also need to represent meaningful business outcomes. Counting a form start as a lead or an add-to-cart as a sale gives reporting credit to an action that doesn't represent the actual conversion.
Start by checking: Deprecated Universal Analytics tracking code, duplicate pixels, outdated tags, unnecessary events, key events that don't represent business outcomes, and conversions generated from the wrong source.
When It's Time for a GA4 Audit
You don't need to wait until you know something is broken. Certain warning signs indicate that your GA4 and GTM setup deserves a closer look.
It's worth considering a GA4 audit if:
- GA4 revenue doesn't match your ecommerce or sales platform.
- Traffic or conversion numbers changed unexpectedly after a website update.
- Your cookie consent banner was recently implemented or significantly changed.
- Your website uses multiple domains, booking engines, or third-party payment systems.
- You inherited the GA4 setup and don't have documentation explaining how it works.
- Your GTM contains years of tags, triggers, and variables that nobody has reviewed.
- GA4 and other reporting platforms consistently show significant discrepancies.
An audit should go beyond checking whether your tracking code is installed.
You can evaluate the relationship between your website, data layer, Google Tag Manager, GA4, consent management platform, ecommerce platform, and other systems that contribute to your reporting. Reviewing those connections helps identify where data is being lost, duplicated, or attributed incorrectly.
At Calibrate Analytics, we perform GA4 and GTM audits to help businesses understand how their tracking works and where data quality can be improved.
If you're questioning the accuracy of your GA4 data, get in touch and we can take a closer look at your setup.
