Analytics Audit Checklist: 15 Things to Check Right Now
When was the last time you actually audited your analytics setup? If you’re like most marketers I know, the answer is “never” or “when we first set it up.” That’s a problem — analytics configurations drift, tracking breaks silently, and bad data accumulates without anyone noticing.
I run a full analytics audit on my sites every quarter. Here are the 15 things I check every time — and the issues I find more often than you’d expect.
Data Collection (Items 1-5)
1. Verify Your Tracking Code Fires on Every Page
This sounds basic, but I find tracking gaps on roughly 1 in 3 sites I audit. Common culprits:
- New landing pages added without the analytics snippet
- Subdomain or staging environments accidentally excluded
- JavaScript errors preventing the tracking code from executing
- Tag manager configurations that exclude specific page templates
How to check: Use your browser’s developer tools (Network tab) and verify the analytics request fires on at least 10 different page types — homepage, blog post, product page, category page, thank-you page, 404 page, search results.
2. Check for Duplicate Tracking
The opposite problem: your tracking code fires twice on some pages. This inflates pageviews, deflates bounce rates, and corrupts session data. It happens when tracking is added both in the theme code and through a tag manager, or when a plugin also injects analytics.
How to check: Look at your real-time report. If sessions consistently show 2 pageviews for obvious single-page visits, you likely have duplicate tracking.
3. Validate Your Event Tracking
Events are the backbone of meaningful analytics. Check that your custom events are:
- Actually firing. Trigger each event manually and verify it appears in your real-time event feed.
- Correctly named. Inconsistent naming (e.g.,
button_clickvsButtonClickvsbtn_click) fragments your data. - Sending the right parameters. Check that event values, categories, and labels contain accurate data — not null, undefined, or placeholder text.
4. Review Your Filters and Exclusions
Are you filtering out internal traffic? Is the filter still accurate? Common problems:
| Filter Issue | Impact | How to Fix |
|---|---|---|
| Office IP changed, filter not updated | Internal visits inflate traffic | Update IP filter quarterly |
| Staging/dev environment not excluded | Test traffic pollutes data | Add hostname filter |
| Bot traffic not filtered | Inflated sessions, skewed metrics | Enable bot filtering + review user-agents |
| Referral spam | Fake traffic sources in reports | Add referral exclusion list |
5. Check Cross-Domain Tracking
If your user journey spans multiple domains (main site → checkout → thank-you page), verify that cross-domain tracking is working. The test is simple: complete a conversion yourself and check if it shows as a single session with the correct source — not a new session attributed to your own domain as referrer.
Data Quality (Items 6-10)
6. Audit Your Conversion Goals
Goals and conversions are the metrics that matter most — and they’re also the most likely to break silently. Check:
- Are all conversions still relevant? Remove goals for features you’ve deprecated.
- Are conversion values accurate? If you assign monetary values, verify they match current pricing.
- Is e-commerce tracking reporting correctly? Compare analytics revenue against your actual sales data for the same period. A 5%+ discrepancy indicates a tracking issue.
7. Review Referral Sources
Open your referral report and look for:
- Self-referrals. Your own domain appearing as a referral source means tracking breaks during navigation (usually a cross-domain or subdomain issue).
- Payment processor referrals. Stripe, PayPal, or similar showing as referral sources means you need to add them to your referral exclusion list.
- Unrecognized AI sources. New AI referral traffic sources may be appearing that you’re not categorizing properly.
8. Check UTM Parameter Consistency
Pull your source/medium report and look for inconsistencies. Common problems:
facebookvsFacebookvsfb(case and naming inconsistency)emailvsEmailvsnewsletter(same channel, different labels)- Missing UTMs on active campaigns (dark traffic issue)
Create a UTM naming convention document and share it with everyone who creates links.
9. Validate Funnel Configuration
If you have funnel reports configured, verify each step still matches reality. Common issues:
- URL patterns changed during site updates
- New steps added to checkout that aren’t tracked
- Steps in wrong order
- Checkout funnel not reflecting current payment flow
10. Check Page Load Impact
Your analytics shouldn’t slow down your site. Use web.dev’s Lighthouse to check your performance score with and without analytics scripts. If there’s a significant difference:
- Ensure scripts load asynchronously or with
defer - Reduce the number of tracking pixels
- Consider server-side tracking for heavy event volumes
Compliance and Configuration (Items 11-15)
11. Verify Consent Management
Test your consent banner from a fresh browser (incognito mode):
- Does analytics tracking actually stop when consent is denied?
- Does it resume when consent is granted?
- Can visitors change their preference after initial choice?
- Does it work on mobile?
12. Review Data Retention Settings
Check how long your analytics tool retains individual-level data. For GDPR compliance, you should have explicit retention periods configured — not “forever” by default. Most teams find that 14-26 months of retention is sufficient for trend analysis.
13. Audit User Access and Permissions
Who has access to your analytics? Review the user list and remove:
- Former employees and contractors
- Agencies you no longer work with
- Test accounts created during setup
14. Check Schema and Structured Data
If you use structured data for rich results, verify it’s still valid. Schema errors can silently accumulate as your content evolves. Run Google’s Rich Results Test on 5-10 pages.
15. Document Everything
The most overlooked step: document what you found, what you fixed, and what your current configuration looks like. Next quarter’s audit will be twice as fast with a baseline to compare against.
Your documentation should include:
- Tracking code locations and version
- Active events and their naming convention
- Conversion goals and their definitions
- Filter and exclusion settings
- Third-party integrations and data flows
Making Audits a Habit
A quarterly audit takes about 2-3 hours once you have the process down. Schedule it. The regulatory landscape is shifting fast enough that waiting longer than quarterly risks compliance gaps.
The investment pays for itself the first time you catch a broken conversion goal that’s been silently underreporting for weeks — and trust me, that happens far more often than anyone admits.
Start with item #1 right now. Open your analytics, check your tracking code, and work through the list. Your data quality — and every decision based on it — depends on it.