Data you cannot trust is worse than no data at all. Bad data gives you confidence in the wrong decisions — you spend money on campaigns that do not work, ignore channels that do, and wonder why growth has stalled. An analytics audit is how you find out whether your tracking is actually telling you the truth.
I run analytics audits for clients at least twice a year, and I find problems in nearly every single one. Duplicate tracking snippets inflating pageviews. UTM parameters that are inconsistent across campaigns. Conversion goals that stopped firing months ago. These are not edge cases — they are common issues that silently corrupt your data.
This analytics audit checklist gives you a structured process to verify your tracking setup, find the gaps, and fix them. You do not need a technical background — just access to your analytics tool and 60-90 minutes.
Why You Need an Analytics Audit
Tracking setups degrade over time. Websites change — new pages get added, forms get rebuilt, plugins get updated, team members add tracking codes without telling anyone. What worked perfectly six months ago might be silently broken today.
Here are the most common consequences of unaudited analytics:
- Inflated traffic numbers from duplicate tracking or bot traffic
- Missing conversions because goal tracking stopped working after a site update
- Inaccurate source data from inconsistent or missing UTM parameters
- Wasted marketing budget based on decisions made from flawed data
- False confidence that everything is fine when it is not
An audit takes this uncertainty away. After running through this checklist, you will know exactly what is working, what is broken, and what needs attention.
The Analytics Audit Checklist
Work through each item below. I have organised them from the most fundamental checks (is tracking even running?) to more advanced concerns (is the data accurate?). For each item, I have included what to check, how to check it, and what to do if you find a problem.
1. Is the Tracking Snippet on Every Page?
- View source on your homepage — confirm the analytics snippet is present
- Check 3-5 other pages (blog post, product page, contact page, thank-you page)
- Check pages added recently — new landing pages often miss the tracking code
- Verify the snippet loads in the
<head>section (not the footer)
How to check: Right-click any page, select “View Page Source,” and search for your analytics tool’s domain (e.g. plausible.io, matomo, or umami). Alternatively, use your browser’s developer tools (Network tab) and filter for your analytics domain.
Common problem: Pages built with a different template or plugin may not inherit the global tracking code. I once audited a site where the entire /shop/ section — the most important part for conversions — was missing the tracking snippet because it used a separate page builder template.
If you set up your site using a guide like how to set up website tracking from scratch, you likely installed the snippet globally. But it is always worth confirming.
2. Are Pageviews Counting Correctly?
- Compare your analytics pageview count to server logs or hosting stats
- Check for sudden spikes or drops that do not match real traffic patterns
- Verify that single-page applications (SPAs) track navigation correctly
- Confirm that 404 error pages are not inflating pageview counts
How to check: Look at your pageview data over the past 30 days. Does the trend make sense? A sudden doubling of pageviews with no corresponding marketing activity often indicates duplicate tracking. A sudden drop might mean the snippet was removed during a site update.
Common problem: WordPress plugin updates can sometimes remove or duplicate the tracking snippet. Always check your analytics after any major site update.
3. Are UTM Parameters Consistent?
- Pull a report of all UTM sources and campaigns from the past 90 days
- Look for duplicates caused by capitalisation differences (e.g.
Facebookvsfacebook) - Check for misspelled campaign names
- Verify that all paid campaigns have UTM tags
- Confirm you use a consistent naming convention
How to check: In your analytics tool, look at the traffic sources or campaigns report. Sort by name and scan for near-duplicates. Consistent UTM parameters are the foundation of useful source attribution — if they are messy, your traffic source data is unreliable.
Common problem: Different team members use different naming conventions. One person tags a campaign as utm_source=Newsletter while another uses utm_source=email. Create a shared UTM naming document and stick to it.
4. Are Conversion Goals Firing?
- List all conversion goals configured in your analytics tool
- Check each goal — has it recorded at least one conversion in the past 30 days?
- Manually trigger each goal (visit the thank-you page, submit the form) and verify it registers
- Confirm goal names and URLs still match your current site structure
How to check: Go to the goals or conversions section of your analytics tool. Look for goals with zero conversions — these are likely broken. Then test each goal manually in an incognito browser window.
Common problem: Site redesigns change URL structures. A goal set to track /thank-you/ breaks if the page moves to /order-confirmation/. I audit sites where critical conversion goals have been broken for months without anyone noticing.
5. Is Referral Spam Filtered?
- Check your referral traffic report for suspicious domains
- Look for referrers with 100% bounce rate and 0 seconds session duration
- Check for referrer domains that are clearly spam or unrelated to your business
- Verify that your analytics tool’s spam filtering is enabled
How to check: Review your top referral sources. Legitimate referrals come from sites that would logically link to yours. If you see domains you do not recognise — especially ones with suspicious names or ones that redirect to unrelated sites when visited — that is referral spam.
Common problem: Referral spam can inflate your unique visitor count by 5-15%. Privacy-first tools like Plausible and Umami are generally better at filtering spam than traditional analytics, but it is still worth checking.
6. Is Bot Traffic Excluded?
- Check if your analytics tool has bot filtering enabled
- Look for traffic patterns that suggest bots (e.g. traffic spikes at 3am with 100% bounce rate)
- Check if known bot user agents are being filtered
- Compare analytics data with server-side logs to spot discrepancies
How to check: Most privacy-first analytics tools filter bots by default. Plausible automatically excludes known bots. Matomo has a “Bot Tracker” setting. However, if you see unusual patterns — like consistent traffic at odd hours with zero engagement — some bots may be getting through.
Common problem: Internal tools and monitoring services (uptime checks, SEO crawlers, security scanners) can generate false traffic. Make sure these are excluded or filtered.
7. Are There Duplicate Tracking Snippets?
- View page source and search for your analytics domain — it should appear exactly once
- Check if both a plugin and a manual snippet are adding the tracking code
- Look for multiple analytics tools tracking simultaneously (unless intentional)
- Check the browser’s Network tab for duplicate tracking requests
How to check: View the source of any page and count how many times your tracking snippet appears. In the browser developer tools, go to the Network tab, reload the page, and filter by your analytics domain. You should see one tracking request per page load, not two or three.
Common problem: Someone installs a WordPress plugin for analytics, forgetting that the tracking snippet was already added manually to the theme. Result: every pageview is counted twice, every session looks shorter than it really is, and your data becomes unreliable.
8. Is the Data Matching Reality?
- Compare analytics conversion count to actual orders or signups in your system
- Cross-reference traffic spikes with known marketing activities
- Check if traffic source percentages make sense for your marketing mix
- Verify that revenue data (if tracked) matches your payment processor
How to check: Pull your conversion data from analytics and compare it against your actual business records. If analytics says you had 100 purchases last month but your e-commerce platform shows 130, something is wrong — either the tracking snippet is missing from some checkout flows, or some transactions are not firing the conversion event.
Common problem: A 10-20% discrepancy between analytics and actual business data is normal (ad blockers, JavaScript errors, and network issues cause some tracking to fail). A discrepancy above 30% indicates a tracking problem that needs fixing.
How Often Should You Audit?
I recommend a full audit at these intervals:
| Trigger | Audit Type | Time Required |
|---|---|---|
| Every 6 months | Full checklist (all 8 items) | 60-90 minutes |
| After any site redesign | Full checklist | 60-90 minutes |
| After changing analytics tools | Full checklist | 60-90 minutes |
| Monthly | Quick check (items 2, 4, and 8 only) | 15-20 minutes |
| After plugin updates | Quick check (items 1 and 7) | 10 minutes |
The monthly quick check is the most important habit to build. Spend 15 minutes checking that pageviews look normal, goals are still firing, and conversions match reality. This catches most problems before they corrupt weeks of data.
Tools for Testing Your Tracking
You do not need paid tools to audit your analytics. Here are the free tools I use with my clients:
- Browser Developer Tools — the Network tab shows every tracking request your page makes. Filter by your analytics domain to see exactly what data is being sent.
- Plausible’s troubleshooting guide — if you use Plausible, their integration troubleshooter walks you through common issues.
- Matomo’s Tag Debugger — built into Matomo Tag Manager, this tool shows which tags fired on each page load.
- Real-time dashboards — open your analytics in one tab, visit your site in another (incognito window), and confirm your visit appears in real-time.
- A spreadsheet — compare analytics data against business records. Export monthly conversions from analytics and your e-commerce platform, then calculate the discrepancy percentage.
Common Problems Found During Audits
Based on the audits I have run over the past 12 years, here are the issues I find most frequently, ranked by how often they appear:
| Problem | Frequency | Impact |
|---|---|---|
| Inconsistent UTM parameters | Very common (70%+ of audits) | Traffic source data is fragmented and misleading |
| Broken conversion goals | Common (50%+ of audits) | Conversions undercounted; ROI calculations are wrong |
| Missing tracking on some pages | Common (40%+ of audits) | Incomplete traffic data; bounce rate inflated |
| Duplicate tracking snippets | Occasional (20%+ of audits) | All metrics doubled; data completely unreliable |
| Unfiltered bot traffic | Occasional (15%+ of audits) | Inflated visitor counts; misleading engagement data |
| Internal traffic not excluded | Common for small teams (30%+) | Team visits inflate metrics, especially for low-traffic sites |
Your Audit Action Plan
Here is the complete process for running your first audit. Block 90 minutes in your calendar and work through it methodically. Review the results alongside your analytics dashboard to connect the findings to your day-to-day reporting.
- Run through all 8 checklist items above, noting any issues found
- Prioritise issues by impact (data accuracy) not effort (ease of fix)
- Fix the highest-impact issue first
- Re-test the fix to confirm it works
- Document your findings and fixes for future reference
- Schedule your next audit (6 months from now)
- Set a monthly reminder for the 15-minute quick check
Frequently Asked Questions
How do I know if my analytics data is accurate?
Compare your analytics conversion data against your actual business records (e-commerce orders, CRM entries, email signups). A discrepancy of 10-20% is normal due to ad blockers and JavaScript failures. Anything above 30% suggests a tracking problem. Also check that traffic trends correlate with known marketing activities — a campaign launch should show a traffic spike.
Can I audit my analytics without technical skills?
Yes. Most of this checklist requires only looking at reports in your analytics dashboard and comparing numbers. The most technical step is viewing page source to check for the tracking snippet, and even that just requires right-clicking and searching for a domain name. You do not need to write code.
What should I do if I find duplicate tracking?
Remove one of the duplicates immediately. Check whether the tracking was added via a plugin, a theme setting, or manually in the code. Keep whichever method is most maintainable for your team. After removing the duplicate, your metrics will drop — this is expected and accurate. Note the date of the fix so you can account for the data discontinuity in future analysis.
Should I use a different tool for auditing than my main analytics?
No, you can audit using your existing tool. The audit checks whether that tool is configured correctly and collecting data accurately. Browser developer tools (free, built into every browser) are the only additional tool you need. For advanced audits, you can temporarily install a second analytics tool to cross-reference data, but this is usually overkill for small businesses.
How much data loss from ad blockers is normal?
Privacy-first analytics tools like Plausible and Umami experience lower ad-blocker rates than traditional analytics — typically 5-10% compared to 25-40% for conventional tools. If you self-host your analytics, ad-blocker impact drops even further because the tracking domain matches your own site.
Bottom Line
An analytics audit checklist is your insurance policy against bad data. Run through the eight checks in this guide every six months, do a quick monthly check on your most critical tracking, and you will catch problems before they corrupt weeks of decision-making data.
The audit itself is straightforward — 60 to 90 minutes of checking that your tracking snippet is present, your goals work, your UTMs are consistent, and your data matches reality. The return on that time investment is enormous: confidence that the numbers in your dashboard actually mean something, and the ability to make marketing decisions based on data you can trust.
