Traffic source tracking
Know where every
visitor really came from.
Multi-signal source detection that catches what cookies cannot. Organic search, paid clicks, social referrals, newsletters — all classified accurately, all without consent banners.
7-day free trial. 2-minute setup.
Why traffic source tracking is broken in most tools
Cookie consent, app-to-web jumps, and HTTPS referrer policies have quietly broken source attribution everywhere. Most analytics tools just silently bucket the loss into "direct".
Cookie-based tools
- 30–60% of visits land in "direct"
- Consent banner drops a chunk before tracking starts
- One signal breaks → source lost
- Paid click IDs require manual setup
Attrifast multi-signal
- Direct shrinks dramatically
- No banner, GDPR by architecture
- Multiple signals, fallbacks built in
- gclid / fbclid / ttclid auto-detected
How Attrifast detects a traffic source
Five independent signals, combined into one accurate source per visit.
SignalWhat it capturesLimits without fallback
document.referrerReferring URL when one is sentStripped on most app-to-web jumps and HTTPS→HTTP
utm_* parametersExplicit campaign taggingOnly as good as your tagging discipline
Click ID parametersgclid, fbclid, ttclid, msclkidNeed normalisation across ad platforms
Search engine matchGoogle, Bing, DuckDuckGo, etc.Search engines hide most query strings
Session continuityReturning visitor stitchingCookieless requires daily-rotating IDs
Every category of traffic source, classified
Organic search
Google, Bing, DuckDuckGo, Yandex, Baidu, Brave, Ecosia.
Paid search & ads
Google Ads, Microsoft Ads, Meta, TikTok, LinkedIn — via click IDs.
Social
X, Reddit, LinkedIn, YouTube, TikTok, Hacker News, Mastodon.
Newsletters, transactional sends, drip campaigns via utm.
Referral
Product Hunt, GitHub, blogs, partner sites, communities.
Direct & internal
Bookmarks, typed URLs, in-app links, email clients.
Traffic source tracking: common questions
What is traffic source tracking?
Traffic source tracking is the process of identifying where each visit on your site came from — direct, organic search, paid ads, social, email, referrals — and reporting that breakdown over time. It is the foundation of any honest marketing report.
How does Attrifast detect traffic sources?
Attrifast inspects the document referrer, parses utm parameters, normalises ad-platform click IDs (gclid, fbclid, ttclid), matches known search and social domains, and stitches sessions with cookieless daily IDs. The result is a clean source for every visit even when one signal is missing.
Why does GA4 misclassify so many sources as "direct"?
GA4 relies heavily on cookies and the referrer header. When users decline consent, switch from app to browser, or arrive via HTTPS-blocked referrers, GA4 falls back to "direct / none". Attrifast uses multiple signals and works without cookies, so direct is much smaller and more accurate.
Can I track paid traffic sources alongside organic?
Yes. Click IDs from Google, Meta, TikTok, and Microsoft Ads are auto-detected and grouped with the matching utm_source. You get a single dashboard that compares paid vs organic vs social vs email by visitors and revenue.
Is traffic source tracking GDPR compliant?
Attrifast is built cookie-free with no personal identifiers, so traffic source tracking happens without consent banners and is GDPR compliant by design.
See which AI engines actually send you paying customers
Attrifast splits ChatGPT, Perplexity, Claude and Gemini into their own revenue lines — joined to real Stripe payments, not estimates.
- One script tag and a Stripe key — live in minutes
- First-party measurement without third-party cookies
- Recognized AI referrals joined to Stripe payments
7-day free trial · $0 due today · then $9.99/mo · cancel anytime
