How to Audit Your Analytics Setup in 30 Minutes

Your analytics data is only useful if it's accurate. A misconfigured tracking script, a missing filter, or a double-counted pageview can distort every report you rely on — and most teams don't notice until someone asks a question the data can't answer.

This audit takes 30 minutes. It covers the six areas where analytics setups most commonly break. Run through it once a quarter, or any time you change your site structure, tracking tools, or payment stack.

Minutes 0–5: Tracking Script Verification

Start with the basics. Is your tracking script actually loading on every page?

Check the script tag. Open your site in a private browser window. Right-click, view page source, and search for your analytics tool's script. It should be in the <head> section. Do this on at least three different page types — the homepage, a content page, and a conversion page (like signup or checkout).

Check all page templates. If your site uses different templates for different sections (blog, landing pages, app pages), verify the script is present on each. A common failure: the marketing site has tracking but the blog doesn't, or vice versa.

Verify the script loads. Open your browser's developer tools (Network tab), load a page, and filter by your analytics tool's domain. You should see at least one successful request. If you see a 403, 404, or blocked request, the script isn't working.

Check for duplicates. Search for your tracking script in the page source — if it appears twice (once directly and once through a tag manager), you're double-counting every pageview and event. Remove one.

Minutes 5–10: Data Accuracy

Now check whether the data being collected matches reality.

Compare pageviews to server logs. Your analytics tool reports client-side pageviews. Your server logs show all requests. If your analytics tool shows 10,000 pageviews but your server handled 50,000 requests, the gap is a mix of bot traffic, cached pages, and visitors with JavaScript disabled. A gap is normal — a growing gap means something changed.

Verify traffic source attribution. Click one of your own campaign links (with UTM parameters) in a private browser window, browse a few pages, and check whether the visit appears with the correct source, medium, and campaign in your analytics. If it shows as "direct" instead, UTM parameters are being stripped somewhere.

Spot-check a metric. Pick a number you can verify independently. For example: compare yesterday's signup count in your analytics with the actual count in your database or payment tool. If they don't match, there's a gap in your conversion tracking.

Check time zones. Confirm your analytics tool is set to the time zone your team uses. A mismatch means "today's" data includes yesterday's late-night traffic or excludes this morning's visits.

Minutes 10–15: Bot and Spam Filtering

Bots distort every metric they touch. Check whether your setup handles them.

Review your bot filtering settings. Most analytics tools have an option to exclude known bots. Make sure it's enabled. In Google Analytics, this is under Admin → View Settings → "Exclude all hits from known bots and spiders."

Check for suspicious traffic patterns. Look at your traffic by source for the past 30 days. Any referral source you don't recognize — especially one sending hundreds of sessions with 100% bounce rate and zero engagement — is likely spam or a bot.

Review geographic data. A sudden spike in traffic from a region where you have no customers, especially from cloud hosting IP ranges, usually indicates bot activity. Flag it and filter if your tool supports it.

Verify bot reporting. If your analytics tool separates bot traffic from human traffic (Trfyx does this by default), check the bot report. Know which crawlers are visiting, how often, and which pages they're hitting. This is also useful for understanding how AI crawlers interact with your content.

Minutes 15–20: Conversion Tracking

Conversion tracking is where analytics becomes actionable. A broken conversion setup means you're optimizing blind.

Test each conversion event. Complete your primary conversion (signup, purchase, form submission) in a private browser and verify the event appears in your analytics. Don't assume — actually test it.

Check the conversion rate. If your conversion rate is suspiciously high (above 20% for most sites) or suspiciously low (below 0.1%), something is likely misconfigured. A high rate might mean bot completions are being counted. A low rate might mean the tracking event isn't firing on all conversion paths.

Verify revenue data. If you track revenue, compare the total revenue in your analytics to your payment provider's actual revenue for the same period. Any discrepancy means events are being missed, duplicated, or incorrectly valued.

Check funnel analysis. If you have funnels defined, walk through each step yourself. Do the funnel steps match the actual user journey? Pages get renamed, URLs change, and funnels break silently.

Minutes 20–25: Reporting and Dashboards

Data you collect but never look at is wasted effort. Check that your reports are set up to surface what matters.

Review your main dashboard. Does it show the metrics your team actually uses to make decisions? If your dashboard still has default widgets from when you first set up the tool, it probably doesn't reflect your current priorities.

Check for broken reports. Open each saved report or custom dashboard. If any show zero data, an error, or obviously wrong numbers, the underlying query or filter may be referencing a metric or dimension that no longer exists.

Verify scheduled reports. If you have reports emailed to your team weekly, check that they're still being sent and that the data looks reasonable. Stale automated reports that nobody reads are a sign the reporting setup needs a refresh.

Confirm access. Make sure the right people have access to the analytics tool and the right reports. If team members are making decisions without data access, that's a setup problem.

Minutes 25–30: Action Items

Spend the last five minutes documenting what you found and what needs fixing.

Prioritize by impact. A missing tracking script on your conversion page is critical — fix it today. A slightly off time zone setting is low priority. Rank everything you found by how much it affects the accuracy of the data your team uses.

Document your setup. Write down where your tracking script is installed, what conversions you track, what filters are active, and what tag manager container you use. The next person who audits (or the next version of you, in three months) will thank you.

Set a reminder. Schedule the next audit for 90 days from now. Analytics setups drift — site changes, CMS updates, new campaign tools, and team turnover all introduce ways for tracking to break silently.

Run this audit regularly. Web analytics tools don't alert you when they're collecting bad data — they just report confidently wrong numbers. The only way to catch it is to check.