What is app.slack.com in my analytics, and why is Slack traffic so low?
23 September 2026 · by Nordva, who make Nordva Launch
The short answer
It means someone clicked a link to your site in Slack, in a browser. You see it less often than Slack sends you visitors: Slack's web app tells the browser to send no referrer at all, so a click there normally arrives with nothing and counts as direct. When a referrer is there, it names Slack, not the workspace, channel or message.
- Referrer
- app.slack.com
- What sends it
- A link clicked in Slack
- Nordva Launch counts it as
- Referral (another website or app)
- Also shows up as
- slack.com · android-app://com.Slack · com.Slack
Why Slack clicks usually arrive with no referrer
A browser tells the page it opens where the click came from, unless the page the click was on says not to. Slack’s web app says not to: the app at app.slack.com/client is served with the header Referrer-Policy: no-referrer and a meta tag that says the same. MDN describes that policy plainly: the Referer header is left out entirely, whatever the destination.
So a link clicked in Slack in a browser normally reaches you with no referrer, and your analytics files it under direct, next to people who typed your address. Some clicks still arrive with one (that is why you’re reading this), so treat app.slack.com in your reports as the part of your Slack traffic you happen to see, not all of it.
Two other forms can turn up:
android-app://com.Slack(or justcom.Slack): the Slack app on Android passing its package name on. The Gmail app referrer page explains where that form comes from.slack.com: a page on Slack’s own site rather than the app.
What it hides
Even when the referrer is there, it’s only the host. A post in a large public community and a message to one colleague look the same, and so do every workspace and channel. A spike of direct visits right after you posted in a Slack group is often that post, but your analytics can’t tell you so.
How to see which Slack post it was
Tag the link before you paste it. The tags are part of the address, so they arrive whatever the browser does with the referrer:
https://example.com/?utm_source=slack&utm_medium=community&utm_campaign=indie-foundersUse one utm_campaign per workspace or channel you post in. Links people copy from your site and share on their own won’t carry tags; those stay direct, and nothing on your side can recover them.
With Nordva Launch
Launch counts app.slack.com and slack.com as a referral, the channel for another website or app, not social. Slack visits with no referrer or tags count as direct, as in any tool. Tags arrive even when Slack sent no referrer: the link above counts as a referral with slack as its source and your campaign attached. A UTM tag that names a channel (a medium such as email or social, or a known source) wins over the referrer, so add utm_medium=social if you’d rather see Slack under social.
When Launch is the wrong tool
If you only share links in one or two Slack groups and can ask the people there, a tagged link and a count of visits is enough. Launch is for when you want to know which community brought the people who signed up and paid.
- Why doesn't Slack show up as a referrer?
- What is com.Slack in my referrers?
- How do I track clicks from a Slack community?
- Slack web app (app.slack.com/client): the response carries the header Referrer-Policy: no-referrer and a matching meta tag (read 23 September 2026)
- MDN: Referrer-Policy, what no-referrer does (read 23 September 2026)
- Google Play: Slack (package com.Slack) (read 23 September 2026)