All articles
5 min read

How to Audit Your Analytics Setup in One Afternoon

A step-by-step analytics audit you can run in one afternoon: dead scripts, broken goals, duplicate events, decayed funnels, and consent drift, all checked without a developer.

How to Audit Your Analytics Setup in One Afternoon

Most analytics setups rot quietly. Someone installs a tracking script in year one, nobody revisits it, and by year three half the events are firing twice, a third of the goals point at pages that no longer exist, and the team is making decisions on numbers nobody trusts. The fix does not require a consultant or a week-long project. A focused afternoon, with the right checklist, is enough to find and fix the worst of it.

This guide walks through a practical audit you can run yourself, in order, without needing to touch code for most of it.

Start With What You Actually Have Installed

Open your site in a fresh browser tab, open developer tools, and look at the network requests firing on page load. You are checking for two things: scripts that should be there and are not, and scripts that should not be there anymore but still are.

It is common to find two or three analytics tools layered on top of each other after years of trials and vendor switches. An old Google Tag Manager container next to a replacement, a heatmap trial that never got removed, a pixel from a campaign that ended eighteen months ago. Each one adds load time and noise to your data. List everything you find, then decide what earns a place on the page and what gets deleted today.

Check Whether Your Goals Still Match Your Business

Goals and conversion events get set up once, usually when a site launches, and then nobody looks at them again even as the business changes. A goal built around a contact form that was replaced two redesigns ago is still sitting in your dashboard, quietly reporting zero.

Walk through your current conversion paths: signup, purchase, booking, demo request, whatever applies. For each one, confirm the tracked event still fires and still matches a real action on the live site. If you cannot remember the last time a goal fired, that is reason enough to check it.

Look for Duplicate or Phantom Events

Duplicate tracking is one of the most common and most damaging issues in an analytics setup. A button click that fires the same event twice inflates every downstream number: conversion rate, revenue per visitor, campaign performance. It usually happens when a script gets added in two places, once in the page template and once in a tag manager, and nobody notices because the totals still look roughly plausible.

Filter your event reports by count per session. A real user rarely triggers the same precise event ten times in one visit. If you see that pattern across many sessions, you likely have a duplicate firing, not an engaged user.

The most dangerous number in analytics is not the one that's wrong. It's the one that's wrong but still looks reasonable enough that nobody questions it.

Compare What the Dashboard Says to What You Can See Yourself

This is the step most teams skip, and it is the one that catches the most problems. Pick five real sessions from your session replay tool and watch them from start to finish. Then check whether your dashboard logged those same sessions with the events you expect: page views, scroll depth, the form field they actually filled in, the button they actually clicked.

If you are using LeadFnF, this comparison takes a few minutes because session replay, heatmaps, and funnels all sit next to each other instead of living in three separate tools you have to cross-reference manually. Watching a handful of real sessions alongside your reported numbers is the fastest way to catch tracking gaps that pure dashboard review will never show you.

Audit Your Funnels for Steps That No Longer Exist

Funnels decay the same way goals do. A checkout funnel built around a three-step process breaks silently the day the checkout gets redesigned into two steps. The funnel keeps reporting data, just data that no longer maps to reality, and the drop-off percentages you are reading become meaningless.

Open each funnel you rely on and manually walk through the live flow on your site, step by step, confirming each tracked stage still corresponds to a real page or action. Rebuild anything that drifted. This is also a good moment to delete funnels nobody has opened in the last quarter. A cluttered funnel list is its own kind of noise.

Confirm Your Privacy and Consent Setup Still Matches What You Collect

If your analytics setup has grown since your privacy policy was last updated, there is a good chance the two no longer match. Check that whatever you disclose in your policy reflects what you are actually tracking today, and that your consent banner, if you run one, correctly blocks or allows the right scripts.

A privacy-first, cookieless approach to analytics sidesteps a lot of this maintenance burden, since there is less to disclose and less consent logic to keep in sync with a policy document. Either way, this is worth a five-minute check during the same afternoon rather than leaving it for a separate audit later.

Write Down What You Changed

The last step is the one that prevents you from doing this same audit again in six months for the same reasons. Keep a short running note, even a single document, of every tracking change you make: scripts removed, goals rebuilt, funnels fixed. The next person who touches your analytics setup, including future you, will thank you for it.

An afternoon spent this way pays for itself quickly. Clean data means decisions based on what is actually happening on your site, not on numbers that drifted away from reality months ago without anyone noticing.

Ready to see your sessions, heatmaps, and funnels in one place instead of stitched together across tools? Start a free trial with LeadFnF and get a clearer picture of what your visitors are actually doing.

Try LeadFnF free for 14 days

Session replay, heatmaps, real-time analytics — one script, no cookies.

Start free trial