Slack referrer traffic
Slack is a common B2B sharing channel. When a link is posted, Slack's unfurl service fetches it to build a preview — a bot request, not a human visit — while a human click may open in the Slack desktop or mobile app and pass little or no referrer. Distinguishing the unfurl from the human click matters, and UTM tags keep human Slack traffic measurable.
Unfurl bot vs human click
When someone pastes a link into Slack, Slack's unfurl service fetches the URL to build the rich preview card. That fetch is a bot request — it should not be counted as a human visit. Mistaking unfurl fetches for visitors inflates traffic for any link shared internally.
The human click is separate. Depending on whether it opens in the Slack desktop app, mobile app, or a browser, your site may receive a slack.com referrer or none at all.
- Posting a link triggers a Slackbot unfurl fetch (a bot)
- The human click is a separate event
- Human clicks may send slack.com or no referrer
Tag B2B links shared in Slack
For links you share in a workspace, add utm_source=slack and a utm_medium such as referral or social, so human visits are attributed even when the referrer is stripped. Because Slack is heavily B2B, this undercount can distort which channels look effective. MDN documents the referrer behaviour involved.
How it appears in analytics and logs
Posting a link in Slack triggers a Slackbot unfurl fetch to generate a preview; that is a bot request, not a visitor. A human click that follows may arrive with a slack.com referrer or none, depending on how it opens.
Diagnostic use case
Separate Slackbot link-unfurl fetches from human Slack clicks, and tag links shared in workspaces so B2B Slack traffic is measurable.
What WebmasterID can help detect
WebmasterID separates the Slackbot unfurl fetch from human Slack visits server-side, so a preview fetch is not counted as audience, and normalises slack.com when a human referrer is present.
Common mistakes
- Counting Slackbot unfurl fetches as human visits.
- Assuming every human Slack click carries a slack.com referrer.
- Putting personal or workspace data into UTM parameters.
Privacy and accuracy notes
The unfurl fetch is automated and carries no human identity; human clicks omitting a referrer is normal in-app behaviour. WebmasterID classifies the unfurl as a bot event and never re-identifies the human who clicked.
Related pages
- Messaging app referrer (WhatsApp, Telegram, etc.)
Links shared in messaging apps such as WhatsApp, Telegram, and similar tools almost always reach your site with no web referrer. These private shares are a core form of dark social: real, often high-intent traffic that referrer reports cannot attribute. UTM tags are the only reliable measure.
- Direct traffic: what it really means
Direct traffic is the bucket analytics uses when no referrer is available. It includes genuine type-ins and bookmarks, but also a large share of visits whose referrer was stripped — app opens, HTTPS-to-HTTP transitions, shorteners, and privacy settings. Treating 'direct' as a single intent is the classic analytics mistake.
- Bot vs human
Separate automated link-unfurl fetches from real human Slack clicks.
Sources and verification notes
- Slack — link unfurling documentationDescribes the unfurl fetch Slack performs to build link previews.
- MDN — Referer header
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.