What direct traffic means
Analytics tools assign each visit a source from two signals: tags in the URL, such as UTM parameters or click IDs, and the referrer the browser sends. When both are empty, the visit is Direct. Direct is not a channel you can invest in. It is the bucket for "unknown".
The name suggests people typing your address, and some do. Returning customers who know your domain, bookmarks and browser autocomplete are real direct visits. But much of the bucket is traffic whose source was lost on the way.
What ends up in Direct
| Cause | Example |
|---|---|
| Typed URLs, bookmarks, autocomplete | A customer opens your app's login page every morning |
| Links in apps that send no referrer | WhatsApp, Slack, Discord, many mobile apps |
| Email and documents | Newsletters without tags, PDFs, slide decks |
Pages with a no-referrer policy | Some sites strip the referrer from every outbound link |
| Redirects that drop tags | A link shortener or tracking redirect that loses the query string |
| HTTPS to HTTP | A secure site linking to a non-secure page sends no referrer |
Shares in private messages are often called dark social. They are a large part of Direct for most sites.
How to measure and shrink direct traffic
- Tag every link you control: newsletters, social bios, partner links, QR codes and links in your own app.
- Check redirects and shorteners keep the query string.
- Look at the landing pages of Direct visits. Deep pages with long URLs were almost never typed, so they point to a share or an untagged link.
- Compare Direct over time with your launches and mentions. A spike that matches a newsletter or a podcast tells you where the untagged link was.
Common mistakes
- Reading Direct as brand strength. It is mostly lost attribution, not loyalty.
- Crediting sales to Direct in a last-touch report. A customer who first came from search and later typed your URL to buy gives Direct the sale under last-touch attribution.
- Ignoring bot traffic. Scrapers that run a real browser usually arrive with no referrer and inflate Direct.
How MetricRaven handles direct traffic
In MetricRaven, Direct is the last channel rule: a visit with no referrer, no utm_source, no ref, via or source link tag, no ad click ID and no utm_medium that names a channel. A visit with a click ID but no referrer goes to Paid, and one with a UTM source but no referrer goes to Campaign. Set utm_source on every tagged link: a link with only utm_campaign still counts as Direct.
- Revenue is credited to each customer's first tracked visit (first-touch attribution). A buyer who found you through search and came back directly to pay is credited to search, not Direct.
- Payments that can't be linked to any visit show as Unattributed, separate from Direct.
- Cloud and hosting networks are excluded by default, so headless scrapers, which often look like Direct visits, don't inflate the bucket (bot traffic settings).
See Campaign & referral links for the full channel rules.
Questions
- Why is my direct traffic so high?
- Usually because links are shared in places that send no referrer, like messaging apps, email and mobile apps, and because untagged links or redirects drop the source. Scrapers running real browsers add to it too.
- Is direct traffic good or bad?
- Neither. Part of it is loyal customers typing your URL. The rest is traffic whose source you lost. Tag your own links so less of it ends up there.
- Does direct traffic include bots?
- It can. Bots that run a browser and send no referrer look like direct visits. Analytics that filter bot user agents and data-center networks keep most of them out.