Direct traffic decoder: what “direct” really is
Long inner addresses are rarely typed.
What your direct visits look like: where they land, what device they use and how they compare with other channels.
Why quietstats: you get this without cookies, a consent banner or storing IP addresses, in every plan including Free.
In every plan, including Free. Sources and campaigns.
📘 Step-by-step guide, with screenshots and diagrams →
Start free, no cardSee live demo
- No cookies or consent banner
- No IP addresses stored
- Groups under 5 visitors hidden
- 845-byte script
- Free plan, no card


What it is
quietstats splits direct visits (no referrer, no tag) into those landing on the home page and those landing on inner pages, compares both with other channels, and lists where direct visits land with the likely reason.
Why it matters
Long inner addresses are rarely typed. Those visits usually come from chat apps, email apps or documents, which you can tag to see properly.
How it works
- Open your dashboard, go to Deep dives (or Reports on a phone) and open Analysis lab.
- Under Sources and campaigns, tap Direct traffic decoder. You can also search for it on the All reports screen.
- Pick a date range (and any options at the top), read the “How to read this” notes, and download any table as CSV.
Privacy: what is and isn’t collected
Collected
- Nothing new: it reads the pageviews, events, goals or daily totals you already have
Never collected
- Anything about a single visitor
- Links between days: visitor ids still reset at midnight
- Cookies, localStorage or anything else stored on the visitor’s device
- IP addresses or user agents (used in memory, then discarded)
- Anything that links a visitor across days (the visitor ID resets daily)
Rows and limits
- Landing pages with fewer than 5 direct visits are left out
- Up to 92 days and 200,000 pageviews per screen
- Read from the database only when you open it, then kept for 10 minutes
“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →
Questions
Can quietstats tell me where direct visits came from?
Not exactly; the browser did not say. This screen gives the likely reasons and tells you how to tag the links.
Does it store anything new?
No. It is worked out from the pageviews and events you already have when you open the screen, and only the totals are kept for 10 minutes.
Related features
Sources and campaignsTagged links count as the right source
Sources and campaignsUTM campaigns
Sources and campaignsEmail sources: newsletters and mail services
Sources and campaignsCampaign content and terms: compare ads, buttons and keywords
Sources and campaignsReferrer tidy-up: one source, several names
Sources and campaignsSocial networks compared: which network sends real readers
Sources and campaignsWhat changed, linked to traffic
See your traffic
All sources and campaigns features → · All features → · Docs: Direct traffic decoder guide → · Compare features with other tools →
Guides on this topic
Set it up
Nothing to set up: it works with the standard one-line script.
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>Try it on your own site
Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.