Products Solutions Templates Pricing Resources

Missing data and incomplete tracking: identifying gaps in your collection

Home / Everything About / Everything About Analytics / Missing data and incomplete tracking: identifying gaps in your collection

You check your analytics. Traffic looks normal. Conversions look normal. Then you compare to your payment processor and find you're missing 15% of transactions.

The tracking is there. It's just not complete. Some visitors are untracked. Some events don't fire. Some pages aren't measured. The data you do have is real. The data you don't have creates blind spots.

Common sources of missing data

Incomplete page tagging

Not every page on your site has tracking code. New pages launched without adding the tracking snippet. Old pages never got tagged. Dynamically-generated pages that skip the tracking tag. Some pages are measured. Others are ghosts—visitors go there but you never see them.

Lost tracking data in redirects

A user lands on Page A. Page A redirects to Page B. The tracking code on Page A fires, but the redirect happens before the tracking request completes. The data gets sent but never reaches your analytics server. The visitor disappears.

Pageviews on single-page applications

Single-page apps don't do full page reloads. They change the URL and update content without refreshing. Tracking code designed for traditional page loads doesn't fire when there's no page load. You see the first page visit but not subsequent navigation within the app.

Mobile app tracking gaps

Mobile apps require special tracking setup. If that setup is incomplete or the tracking library was implemented incorrectly, you lose data. Events might fire sometimes but not consistently. Some screens might be completely untracked.

Offline conversion tracking

Sales that happen offline (by phone, in person) never reach your analytics. You track online conversions but lose visibility of offline sales. Your conversion rate looks worse than it actually is.

Third-party platform tracking gaps

Your checkout is on Shopify but you're trying to track it from your marketing analytics tool. Shopify has its own tracking. The two don't always sync perfectly. Revenue tracked in Shopify might not appear in your analytics.

How to identify missing data

Compare analytics to server logs

Server logs record every request to your server. Analytics records pageviews and events that fire properly. Compare the two. If server logs show 1000 requests but analytics shows 800 pageviews, you're losing 20% of traffic.

Compare analytics to payment processor

For e-commerce sites, this is the most important comparison. Payment processors show actual conversions. Analytics shows tracked conversions. The gap is your tracking gap. If your payment processor shows 100 transactions but analytics shows 85, you're missing conversion data.

Compare between your analytics tools

If you use multiple analytics tools (Google Analytics and Mixpanel, for example), compare them. One tool might track some events the other doesn't. The difference reveals gaps in both.

Look for zero-value transactions

Transactions showing $0 value in your analytics often indicate incomplete tracking. The tracking fired but the revenue value didn't populate. This signals the tracking is broken, not missing.

Check for missing segments in reports

Run a report segmented by traffic source. Add up the traffic from all sources. Does it match your total traffic number? If not, some traffic isn't being properly tagged with a source. That traffic is missing from your analysis.

How to find and fix tracking gaps

Audit all pages and applications you want to track

List every page, application, and conversion point you want to measure. Verify that tracking code is present on each. Look at the page source to confirm the tracking snippet is there and properly implemented.

Test every tracking implementation

Don't assume tracking works. Test it. Create a test transaction and verify it appears in your analytics. Navigate through your app and confirm each screen fires tracking. Use your tool's debug mode to watch data in real time.

Fix single-page app tracking

Most analytics libraries now support single-page apps and have methods to track virtual pageviews. Call the pageview method when the app changes screens. This fires tracking without a page reload.

Implement proper mobile app tracking

Use your analytics tool's mobile SDK. Implement it correctly in your app. Test that events fire and data reaches your analytics server. Test on real devices and network conditions.

Create redundant tracking for critical conversions

For revenue-critical conversions, implement tracking in two places. Track in your analytics tool. Also send conversion data from your server to your analytics server. If one tracking fails, the other captures it.

Set up CRM sync for offline conversions

If you have sales reps or offline channels, import those conversions into your analytics. Most tools can import offline data through their APIs. This closes the gap between online and offline data.

The cost of missing data

Underreported conversions

Your conversion rate looks worse than it actually is. You make decisions assuming lower conversion than reality. You might skip optimizations that would actually work.

Incomplete customer journeys

You can't see the full path users take through your business. You track some pages but not others. You see some conversions but not all. Your understanding of user behavior is incomplete.

Wrong budget allocation

If some channels aren't tracked, they look worthless even if they're actually valuable. You might defund channels that work and overfund channels that don't.