We've inherited more broken analytics setups than we can comfortably count over the years. Duplicate tracking codes firing twice, goals that were never configured correctly in the first place, Google Analytics still counting internal staff visits as genuine customer traffic — these aren't rare edge cases, they're closer to the norm when a business has been managing its own tracking or inherited a setup from a previous agency who never properly checked their own work. Before we report a single figure to a client, we audit the plumbing behind it, because a beautifully designed report built on faulty data is genuinely worse than no report at all in our experience. This isn't a box-ticking exercise we rush through quickly before getting to the more interesting strategic work. Genuinely broken tracking has, in our experience, led business owners to defund campaigns that were actually working well while pouring budget instead into channels that only looked successful because of a misconfigured goal somewhere in the account, which is a genuinely expensive mistake to make without ever realising it.
Checking for Duplicate and Conflicting Tags
The first thing we look for is duplicate tracking, usually from a Google Analytics tag being installed twice, once directly in the site's code and again through Google Tag Manager layered clumsily on top without anyone realising what had happened. This inflates session counts and skews every downstream metric, from bounce rate to conversion rate, without anyone noticing unless they go looking specifically for it with the right diagnostic approach in hand. We've seen businesses genuinely believe traffic had doubled overnight when the real explanation was a duplicated tag counting every single visitor as two separate sessions in the reporting dashboard they trusted completely. This kind of duplication is particularly common straight after a website rebuild, when a developer adds fresh tracking code without first checking what a previous agency or in-house team had already installed months earlier. We always ask for admin access during onboarding specifically so we can check this ourselves rather than relying on someone's memory of what was supposedly set up correctly the first time round.
Filtering Out Internal and Bot Traffic
Staff checking the website from the office, developers testing changes on a staging environment, and automated bot traffic can all quietly contaminate a dataset if filters aren't set up correctly from the very start of a build. We configure IP exclusions and bot filtering as standard practice, then check the numbers before and after to see how much of a genuine difference it actually makes to the underlying trend line. In more than one case, filtering internal traffic revealed that a seemingly "steady" traffic trend was actually masking a genuine decline in real customer visits that had gone unnoticed for several months running. We also review referral exclusion lists at the same time, because payment gateways and booking widgets can otherwise appear as separate referring websites and quietly break the continuity of a single customer's journey through the site. Getting this right up front means a client's conversion path looks the way it actually happened, not the way a poorly configured default setting decided to record it instead.
Verifying That Conversions Actually Mean Something
A conversion goal is only useful if it's tracking something the business actually cares about in commercial terms that matter. We've seen "conversions" configured to fire on a simple page view of the contact page rather than an actual form submission, which massively overstates genuine enquiries and gives everyone a false sense of momentum. We test every goal manually — submitting real forms, making test calls where call tracking is in place — to confirm the numbers genuinely reflect real business outcomes rather than a convenient proxy that happened to be easier to set up in the first place. This diligence is part of what we build into every SEO and analytics engagement from the very start of the relationship.
Making Sure Cross-Device and Cross-Domain Tracking Works
Plenty of Colchester businesses send traffic across multiple domains or subdomains — a booking system hosted on a separate platform, for instance, or a checkout hosted elsewhere entirely from the main site. If cross-domain tracking isn't configured properly, a single customer journey gets split into two disconnected sessions, and attribution data becomes close to useless for making any real decisions with confidence. We check this specifically as part of every onboarding audit rather than simply assuming a previous setup got it right first time, because that assumption has been proven wrong far too often for us to keep making it without checking. Getting this piece right matters just as much for smaller local businesses as it does for larger multi-site operations, because even a single missed connection between a booking platform and the main website can quietly understate genuine demand for months on end. It's a detail we build into every stage of the SEO reporting we build for Colchester clients from the very first audit onward.
Reconciling Analytics Against Other Business Data
Numbers in isolation can look entirely convincing and still be wrong in ways that only become obvious once compared properly against something else entirely. We cross-check analytics-reported enquiries against actual CRM entries, phone records, or booking diaries wherever a client can provide them, as a proper reality check on the whole system. When the figures line up, we know the tracking is trustworthy and can move forward with confidence. When they don't, that gap tells us exactly where the setup needs fixing before we build a single report around it and trust numbers that aren't actually reliable. This reconciliation step takes real time, sometimes an extra day or two during onboarding, but it's time well spent compared with the alternative of building months of strategy on top of a number that was quietly wrong from the very start. We'd rather find that out in week one than have a client discover it themselves eight months into the relationship.
Documenting What We Find and What We Fix
Every audit produces a written record, not just a private internal fix that the client never sees or fully understands. We share this documentation openly rather than filing it away somewhere internal, because a client deserves to know exactly why their historical numbers might look different once tracking has been properly corrected at the source.
- A written summary of every tracking issue identified during onboarding, in plain language
- Before-and-after figures showing the genuine impact of each fix on reported data
- A clean baseline date from which all future comparisons are measured fairly and honestly
It's usually no more than a page or two, but it saves a great deal of confusion months down the line when someone inevitably asks why last year's figures don't quite match what a newer, cleaner dashboard now shows them.
The Bottom Line
Trustworthy reporting starts with trustworthy tracking, and trustworthy tracking is never something you can simply assume is already in place before you begin. We audit every setup we inherit because we'd rather spend a few focused days fixing the plumbing than spend months delivering reports built on numbers that were never accurate in the first place and never will be. It's unglamorous, essential work, and it's exactly the kind of thing that quietly separates reporting you can genuinely act on with confidence from reporting that simply looks tidy on the page and falls apart under scrutiny. Every client deserves to know their numbers are real before they ever start making decisions based on them.
Looking for Best SEO Company in Colchester?
Let's talk about what your business actually needs
Digital Impact Ventures provides SEO, AI visibility and digital marketing support for businesses across Colchester and Essex. Get in touch and we will talk through where your business is now and where it needs to go.