Direct traffic
Updated 2026-11-02
Definition
Direct traffic is any visit with no referrer and no campaign tags. Analytics can't tell where it came from, so it gets the label Direct.
The name suggests someone typed your URL or used a bookmark, and some of it is exactly that. In practice, direct is a catch-all for visits whose source wasn't passed along.
Example
This example uses made-up numbers. Your report shows 3,000 direct visits this month. Look closer:
- 1,000 land on your homepage, which fits people who know your name.
- 300 land on
/login, which is existing users. - 1,200 land on a single blog post, on the day someone shared it in a private group.
- 500 land on
/pricingfrom links in a mobile app.
Only about a third of those visits are the classic picture of direct traffic. The blog spike is probably dark social.
What ends up in direct
- Links in email clients and mobile apps
- Links shared in private messages
- Untagged links in documents and PDFs
- Typed URLs and bookmarks
- People who heard about you offline
How to shrink it
Tag every link you control with UTM parameters, especially in emails. Then exclude your own team and internal pages. Ask people how they found you, since many direct visitors can name a real source.
How Headstream measures it
Headstream labels a session Direct when it has no click ID, no UTM tags and no outside referrer. It classifies each session by its first pageview.
Because direct is so often wrong, Headstream compares it with what people tell you. If someone answers "podcast" and tracking saw Direct, they count toward the "hidden from tracking" stat in self-reported attribution. You can exclude internal paths and IP addresses in your project settings. See the methodology page.