Why "we have analytics installed" does not mean "we have accurate data"
Data loss in a typical tracking setup rarely happens dramatically it happens at specific, identifiable points where tracking quietly fails to fire, fires incorrectly, or gets blocked, often without any visible error to alert the business owner that anything is wrong. Understanding these specific failure points is the fastest way to audit whether your own analytics can actually be trusted.
Where the gaps typically occur
Between the website and the tracking code being present at all. The most basic gap a tracking code that was correctly installed during the original website build but was accidentally removed or broken during a subsequent redesign, theme change, or migration, sometimes for months before anyone notices because the website itself still looks and functions normally to visitors.
Between a conversion happening and being tracked as one. As covered in event tracking for forms and calls, GA4 does not automatically know that a form submission or button click matters without explicit trigger configuration, real conversions happen on your website every day with zero corresponding record in your analytics.
Ad blockers and privacy browser settings. A meaningful percentage of internet users (varying significantly by audience, but often 10 30%) use ad blockers or privacy-focused browser settings that block standard analytics tracking scripts entirely meaning your reported traffic is always somewhat undercounted relative to actual visitors, a gap that is rarely zero and worth keeping in mind when interpreting absolute numbers.
Cookie consent tools blocking tracking by default. If your site has a cookie consent banner (increasingly necessary for privacy compliance, see privacy, consent and cookie basics in India), a misconfigured banner can block analytics tracking for every visitor who has not yet explicitly accepted cookies sometimes the majority of visitors, depending on banner design and default settings.
Cross-domain or subdomain tracking gaps. If your checkout process, booking system, or a key part of your customer journey happens on a different domain or subdomain than your main site (a common e-commerce or booking platform setup), the visitor journey can appear to "break" in analytics at that domain transition unless cross-domain tracking is specifically configured.
Server-side caching interfering with tracking scripts. Aggressive caching plugins, configured to improve page speed, occasionally cache a page in a way that interferes with dynamic tracking scripts loading correctly for every visitor, particularly on the first page someone lands on.
Manual data entry gaps for offline conversions. Phone calls, walk-ins, and referrals that result in a sale have no inherent digital footprint at all if these are not manually logged into your CRM with a source noted, this portion of your actual business activity is permanently invisible to any analytics system, digital or otherwise.
How to audit your own setup for these gaps
Use GTM's Preview mode and GA4's Realtime report (as detailed in how to set up GA4 the right way) to directly verify, rather than assume, that your tracking code is present and your key conversions fire correctly. Periodically cross-check a manually counted reality (actual enquiries received in a given week) against what your analytics reports for the same period a significant, consistent gap signals one of the issues above is likely present.
Frequently asked questions
No some data loss (ad blockers, privacy settings, untracked offline conversions) is essentially unavoidable with current web technology and increasing privacy expectations. The goal is minimising avoidable, fixable gaps (broken code, missing event configuration) rather than expecting perfect, complete data.
Some discrepancy between platforms is normal and expected, due to differences in how each measures and attributes activity. Significant, consistent discrepancies (one platform reporting dramatically more or fewer conversions than another) are worth investigating, but minor variance is a normal characteristic of working with multiple independent tracking systems.
A thorough check after any significant website change (redesign, new plugin, hosting migration) since these are the moments most likely to silently break existing tracking, plus a periodic quarterly spot-check as part of regular maintenance.