The attribution gap
Your tracking depends on data surviving advertising platforms, apps, browsers, consent, cookies and third-party systems. Information gets lost along the way, leaving you with incomplete analytics and only part of the picture.
See where tracking failsThe Blind Spot
This figure is the average we’ve seen across new agency-managed accounts since early 2020s. Missing visits don’t all vanish from the dashboard, they often get reassigned to “Direct”.
The default answer
Despite the name, Direct is rarely people who typed-in your address. It’s often where analytics puts visits it couldn’t identify. The size of the number is not brand awareness, it’s what the tracking is losing. High ad spend and a large Direct numbers travel together, as paid traffic is most vulnerable to having its source stripped.
Where tracking breaks
Attribution does not usually break in one dramatic moment. It erodes across the path from campaign click to business outcome.
The source never reaches your analytics intact.
Campaign parameters may be stripped, shortened links may hide the referring page, and privacy-focused browsers can reduce referrer detail. Analytics receives the visit but not the reliable context behind it.
The page loads, but tracking does not behave as expected.
Scripts can be blocked, delayed or prevented from firing. Consent settings and tag configuration can also produce gaps. The customer arrived; the analytics record may be partial or absent.
One visit becomes several disconnected records.
Moving between domains, payment platforms or booking tools can restart sessions and overwrite attribution. Instead of one coherent path, the report shows fragments that are difficult to reconnect.
The result is recorded without the marketing context.
A quote request, booking or purchase may still appear, but its original source has been replaced or removed. Revenue exists; confidence about what produced it does not.
Uneven exposure
Paid social, email, affiliates, QR codes and links opened inside apps are more exposed to source loss than a straightforward browser search. The reporting bias is not evenly distributed, so channel comparisons can become misleading.
The consequence
Dashboards can calculate perfectly from incomplete inputs. That precision creates false confidence: teams move budget, judge campaigns and forecast growth using categories that may describe a tracking failure rather than customer behaviour.
Source loss removes credit from the campaigns that generated the visit.
Unknown arrivals are absorbed into a category that appears intentional.
Fragmented sessions hide the actions that happened before the outcome.
Clean-looking reports reward whichever channels retained the most evidence.
Why the gap persists
Better tags, models and dashboards can help, but they can’t recreate source details that were never recorded.
| Typical fix | What it helps with | What it cannot restore |
|---|---|---|
| Add more UTMs | Creates clearer labels when parameters survive. | A parameter removed before capture. |
| Change attribution models | Redistributes credit across the data available. | Missing evidence or disconnected sessions. |
| Build another dashboard | Makes existing information easier to inspect. | The source that never entered the dataset. |
| Move tags server-side | Can improve control over event delivery. | Origin information already lost on arrival. |
A more reliable approach
Dáva captures where each visit came from before the source can be stripped or misclassified. It then connects that source to every page visited, event recorded and outcome reached within the same session.
See how Dáva works
The layer most companies skip
Many companies don’t have one agreed system for naming campaigns, classifying sources or defining meaningful outcomes. Dáva’s governance layer solves this by creating a shared tracking language while preserving the original evidence.
Explore tracking governanceSee how Dáva can show you what’s working, what isn’t and where your money should go next.
Book a Demo 30 minutes | Live data walk-through