5 signs your tracking is broken
Nicklas Segatz Mortensen · Growth Hacker · Fractional CMO · Meta Ads Nerd · 8 July 2026 · 5 min.
01The five warning signs
Tracking problems rarely show up as an error message — they just drain performance quietly, because the algorithm optimizes on patchy data. Here are five signs that your data foundation is leaking:
- 1.A big discrepancy between conversions in the ad account and actual orders in the store — the platform sees only a fraction of the sales.
- 2.Low Event Match Quality (under ~6) in Meta, a sign that too few matched parameters are being sent for users to be recognized.
- 3.No server-side tracking (CAPI/sGTM), so a growing share of events is lost to ad blockers, ITP and iOS.
- 4.Conversions counted twice, because pixel and server-side aren't deduplicated on a shared event_id.
- 5.Lots of traffic in "direct / unknown" in your analytics, a sign of missing UTM tagging and an unclear source for the sales.
Sådan virker det
Browser-tracking taber hændelser til adblockere, cookie-spærring og iOS. Server-side sender konverteringen fra din egen server direkte til Metas CAPI og Google — uden for blokeringernes rækkevidde. Bedre data = bedre optimering.
02Why it costs more than you think
Bad tracking isn't just a reporting problem — it's a performance problem. When the algorithm sees fewer or wrong conversions, it optimizes worse, bids wrong and scales slower. A lift in data quality (server-side, high EMQ, dedup) often raises performance without touching budget or creatives.
That's why an audit almost always starts in the tracking layer. If the foundation is leaky, everything else is built on sand — and the lost conversions you can't see are exactly the ones that cost the most.
Frequently asked questions
How do I know if my tracking is broken?+
Look for a discrepancy between the ad account's conversions and actual orders, low Event Match Quality, missing server-side tracking, double-counting, and lots of 'direct/unknown' traffic. One or more of these signs points to a leaking data foundation.
Why is bad tracking a performance problem, not just reporting?+
Because the algorithm optimizes on the data it sees. Fewer or wrong conversion signals mean worse bidding, slower scaling and higher CPA. Better data quality lifts performance without changing budget or creatives.
Related terms
Glossary
What is server-side tracking?
Server-side tracking sends conversion events from your own server (e.g. via a server-side Google Tag Manager container and Meta's Conversions API) instead of from the user's browser — so data isn't lost to ad blockers, cookie restrictions and iOS limitations.
Read the entry →Glossary
What is Event Match Quality (EMQ)?
Event Match Quality (EMQ) is a score from 0 to 10 that measures how well Meta can match a conversion event to a user, based on the customer parameters you send (hashed email, phone, name, external ID and more).
Read the entry →Glossary
What is deduplication?
Deduplication is the process that prevents the same conversion from being counted multiple times when it's sent from both the browser (pixel) and the server (CAPI) — typically by both sources sharing the same event_id.
Read the entry →Glossary
What are UTM parameters?
UTM parameters are small tags you add to the end of a link (source, medium, campaign and more), so analytics tools can record which source, channel and campaign a visitor came from.
Read the entry →We build the tracking foundation from the ground up as part of Profit Forge.
See Profit Forge →
Nicklas Segatz Mortensen
Growth Hacker · Fractional CMO · Meta Ads Nerd at Oaksmond
Growth hacker and fractional CMO with 10+ years' experience and hundreds of millions in managed ad spend behind him. Background from larger Danish and international scale-ups, and from the agency world.
Meet the team →