How a tagging conflict happens
Two different mechanisms can describe the same click. An advertising platform with auto-tagging switched on attaches its own click identifier and passes the campaign detail through the linked accounts. Manual tags describe the click in plain text written into the URL. When both are present on one landing page address, each system has to decide which story to believe.
Where the advertising and analytics accounts are linked, the automatic data normally takes precedence inside analytics, while other tools — a CRM, an email platform, a dashboard, a form handler — read whatever plain text they can see. The result is not an error message. It is two sets of records that quietly disagree, and nobody notices until someone compares them.
The usual origin is mundane. Somebody builds an ad by copying a landing page URL that already carried tags from an email campaign, and the old email tags travel into a paid campaign where they no longer make sense.
Why a tagging conflict matters
It corrupts exactly the number people trust most: cost per lead. If paid clicks are recorded under an email or referral label, the spend sits against one channel while the enquiries sit against another, and both channels are judged wrongly. Budget then moves in the wrong direction, confidently.
It also breaks the conversation between systems. When the advertising platform, analytics and the CRM each name a different origin for the same enquiry, arguments about which one is right consume more time than the campaign itself, and the honest answer is that none of them is reliable while the conflict remains.
Common mistakes with tagging conflicts
The first is trying to solve it by tagging harder — adding manual parameters to every ad so that at least the values are consistent. That replaces automatic data that was accurate with typed data that is not, and loses keyword and cost detail in the process.
The second is switching auto-tagging off. It is tempting, and it does end the disagreement, but it also ends the click identifier that connects a click to the spend behind it. That trade is almost never worth making.
The third is treating it as a reporting problem. Filters and renamed rows change how the past looks; they do nothing to what arrives tomorrow. The fourth is assuming a redirect is harmless — a redirect that drops the query string removes the manual tags and keeps the identifier, or the reverse, and produces the same disagreement from a different direction.
How to act on it
Decide one method per channel and enforce it. Leave auto-tagging on for platforms that support it and strip manual parameters out of those landing page URLs entirely. Use manual tagging only where no automatic connection exists.
Then audit the actual URLs rather than the intention. Export the final URLs from each campaign and look for parameters that should not be there, click a live ad and inspect the address that ends up in the browser after every redirect, and check that your redirects preserve the query string. Fixing the link is the only fix; everything downstream is a symptom.