Analytics
Five conversion tracking mistakes that distort marketing decisions
Duplicate events, missing UTMs, the wrong optimization goal, and more. Common tracking errors that quietly mislead campaign decisions, and how to check for each.
6 min read
Campaign decisions are only as good as the conversion data behind them. Tracking problems rarely announce themselves. Reports keep filling with numbers, and nobody notices that the numbers mean something different from what they appear to. These five issues are among the most common, and each can be checked in an afternoon.
1. Counting the same conversion twice
Duplicate conversions happen when a thank-you page fires an event on every reload, when both a browser pixel and a server-side integration report the same event without de-duplication, or when the same goal is configured in two tools that are both imported into the ad platform.
How to check: compare the conversion count in each platform with the number of real records (orders, CRM leads) for the same period. Large, consistent differences in one direction usually point to duplication.
2. Optimizing for the wrong event
If a campaign is told to optimize for page views, button clicks or “add to cart”, it will find people who do those things, which may not be the people who buy. Micro-conversions can help new campaigns gather data, but the primary optimization goal should be as close to real business value as your volume allows.
How to check: list the primary conversion action for every active campaign and confirm each one is the outcome you would actually pay for.
3. Losing the source between the click and the CRM
Inconsistent or missing UTM parameters, redirects that strip query strings, and forms that don't capture campaign data all break the chain from ad to lead. The result is a CRM full of leads labelled “direct” or “unknown”, and no way to judge campaigns by lead quality.
How to check: submit a test enquiry from each live ad and confirm the campaign details arrive intact in the CRM record.
4. Ignoring consent and browser restrictions
Consent requirements, ad blockers and browser privacy features mean that some conversions are never observed by client-side tags. That is expected and, in many regions, legally required. The mistake is treating the observed numbers as complete. Trends may still be useful, but absolute totals and cross-channel comparisons need care.
How to check: understand your consent setup and estimate the share of conversions you can observe, for example by comparing tagged conversions with backend records. Server-side or modelled approaches can help, within the limits of your consent obligations.
5. Mixing attribution windows and definitions
Platforms use different default attribution windows and models, and those defaults change over time. Comparing a 7-day-click figure from one platform with a 30-day-click-plus-view figure from another isn't a fair comparison, and neither matches what your analytics tool reports.
How to check: document the attribution setting behind every number in your reports, align settings where possible, and label any figure that uses a different basis.
Make tracking a maintained system
Tracking isn't a one-time setup. Site changes, new forms, platform updates and new campaigns all introduce risk. A short monthly check, comparing platform conversions with real records and testing a few key journeys end-to-end, catches most problems before they influence a budget decision.