Traffic Sources

Traffic sources answer the most important question in distribution: where did these clicks actually come from?

---

Definition

Traffic sources in link analytics identify the channel or origin from which each click on a short link arrived. They are derived primarily from the HTTP Referer header — the field in an HTTP request that identifies the URL of the page from which the visitor navigated.

Traffic source data answers the distribution question: if the same short link is shared across email, social media, SMS and a website, which channel drove each click? Without traffic source data, total click volume is visible but attribution to channels is not.

Main Traffic Source Categories

• Direct. Clicks with no referrer header. Includes: typed URLs, saved bookmarks, links opened from apps that strip referrers, email clients that do not pass referrer headers, and messaging apps. Direct is often the largest category and is frequently misunderstood as meaning "people typed the URL directly."
• Social. Clicks from social media platforms — identified from known social platform domains in the referrer. Platforms are broken out individually: Facebook, Instagram, X/Twitter, LinkedIn, Pinterest, TikTok and others.
• Email. Clicks from email platforms that do pass referrer data — typically webmail interfaces (Gmail web, Outlook web) when the referrer is not stripped.
• Search. Clicks from search engine result pages — Google, Bing, DuckDuckGo and others.
• Referral. Clicks from specific web pages — partner sites, articles, directories or any webpage that contains the link and passes referrer data.

Why Direct Traffic Is Often Overrepresented

Direct traffic in link analytics is frequently higher than the actual percentage of visitors who typed or bookmarked the URL. Several common scenarios produce direct traffic because they generate clicks without a referrer header:

• Email clients. Most native email apps (Gmail app, Outlook app, Apple Mail) and many desktop clients strip or do not pass referrer headers. A link in an email campaign appears as direct traffic in link analytics unless UTM parameters carry the attribution.
• Messaging apps. WhatsApp, Telegram, iMessage, Facebook Messenger and similar apps do not pass referrer headers when links are clicked from within the app.
• HTTPS-to-HTTP transitions. When a user navigates from an HTTPS page to an HTTP destination, browsers strip the referrer header for security. Short links always use HTTPS, but destination pages on HTTP lose the referrer.
• Privacy tools. Browser extensions, VPNs and privacy-focused browsers may strip or modify referrer headers.

The solution is UTM parameters: adding utm_source and utm_medium to destination URLs carries channel attribution data independently of the HTTP referrer — solving the email and messaging app attribution gap at the destination analytics level.

Using Traffic Source Data

• Channel contribution comparison. Which channel drives the most link clicks for this campaign? Which drives the least? This informs channel investment decisions for future campaigns.
• Audience behaviour by channel. Combining traffic source data with device data: are social visitors primarily mobile? Are email visitors primarily desktop? This informs content format and landing page design decisions per channel.
• Unexpected source discovery. Traffic source data sometimes reveals that a significant percentage of clicks are coming from an unexpected source — a partner site, a forum, a press mention. This surfaces organic distribution that was not part of the planned campaign.

Related Terms

• Referrers
• Link Analytics
• UTM Parameters
• Click Tracking