Products Solutions Templates Pricing Resources

Verification: Confirming Your Tracking Code Is Working

Home / Everything About / Everything About Analytics / Verification: Confirming Your Tracking Code Is Working

You installed the tracking code. Did it work? Are you measuring what you think you're measuring? Most site owners install tracking and never verify. They trust that it works. Three months later, they discover tracking was broken the whole time. They've collected useless data. They've made decisions based on bad numbers. Verification takes thirty minutes. Not verifying costs days of wasted analysis. Verify first. Trust later.

This article walks through verification methods that confirm your tracking is working before you rely on the data for decisions.

Use Real-Time Data Verification

Most analytics platforms show real-time data. Visit your website yourself. Refresh a few pages. Check your real-time dashboard. Does your visit appear? If you see yourself in real-time data within seconds, tracking is working.

Check different pages. Check the homepage. Check a blog post. Check a product page. Your visits should appear on all of them. If your visit appears on the homepage but not on blog posts, something is wrong with blog post tracking.

Do this with different devices. Visit from mobile. Check if mobile visits appear in real-time. Visit from desktop. Check if desktop visits appear. Tracking should work everywhere.

Test Conversions

If you set up conversion tracking, test the conversions before going live with real traffic. Go through your conversion process. Complete a purchase. Submit a form. Sign up for email. Check your real-time dashboard. Did the conversion appear?

Conversions should appear within seconds of completing the action. If you don't see a conversion in real-time, it's not firing. Find out why. Check that the conversion tag is on the right page. Check that the tag is installed correctly. Debug before going live.

Test conversions from different devices and browsers. A conversion might work on Chrome but not Safari. Test everywhere.

Use Browser Developer Tools Verification

Open your browser's developer tools. Go to the Network tab. Refresh your website. Look for requests going to your analytics platform's servers. You should see one or more requests to your analytics domain.

These requests show that tracking code is firing. If you don't see any requests to your analytics domain, the tracking code isn't working. Check your page source. Search for the tracking code. If the code isn't there, it's not installed. If the code is there but no network requests are firing, the code might be broken.

This technical verification confirms what real-time data shows. It's a second confirmation that tracking is working.

Test With Different Traffic Sources

Visit your website from different sources. Click a link from an email. Search for yourself on Google and click your result. Click an ad if you have ads running. Each traffic source should appear in your analytics with the correct source.

Check that traffic source is correctly attributed. Email clicks should show "email" as the source. Search results should show "google" as the source. Ad clicks should show the ad platform as the source. If sources are incorrectly labeled, your traffic analysis is wrong.

Compare Analytics Data to Server Logs

If you have access to your server logs, compare them to your analytics. Your server logs show every page request. Your analytics shows pageviews. They should roughly match. If your server logs show 100 requests and your analytics show 10 pageviews, something is wrong.

They won't match exactly. Bots create server requests but shouldn't be counted as visitors. Cached pages might not hit the server every time. But they should be in the same ballpark. If they're off by 10x, something is seriously wrong.

Set Up Test Data and Validation Alerts

Create a test visitor or test user. Tag it with a special value so you know it's test data. Then monitor that test data. Every day, someone should visit as a test user. If test data stops appearing, tracking probably broke.

Set up an alert. If your analytics receive no data for an hour, alert someone. This catches broken tracking immediately instead of waiting days to notice.

Don't rely on alerts alone. Verify weekly that tracking is working. Check real-time data. Check conversions. Check traffic sources. Make verification part of your routine.

Document and Continue Verification

Document your verification process. What did you check? What did you find? When did you verify? Keep records. If something breaks later, you'll know what working tracking looks like.

Verify at least monthly. Schedule a task. Check real-time data. Check a few conversions. Verify that traffic sources are correctly labeled. Small verification takes minutes. It prevents days of bad analysis.