Bluesky referrer traffic
Bluesky is a growing social network whose primary web client lives at bsky.app. Links clicked from the web commonly pass a bsky.app referrer, so Bluesky traffic is often identifiable. As with any platform, app and client contexts can reduce the referrer, so UTM tags keep attribution consistent.
Where Bluesky traffic comes from
Bluesky's main web client is hosted at bsky.app, and links clicked there commonly pass a bsky.app referrer. That makes it more measurable in referrer reports than platforms dominated by in-app browsers.
Because Bluesky is comparatively new and still growing, treat its referrer volume as evolving rather than stable, and avoid over-reading short-term swings as durable trends.
- Primary web client is bsky.app
- Web reads commonly send a bsky.app referrer
- A growing network — referrer volume is still evolving
Tagging Bluesky links
For links you post, add utm_source=bluesky and a utm_medium such as social, so attribution holds even when an app context reduces the referrer. MDN documents the Referer header and Referrer-Policy behaviour involved.
How it appears in analytics and logs
A bsky.app referrer means the visit came from a link on Bluesky's web client. Because Bluesky is web-accessible, the referrer is present more often than on app-first platforms, though app contexts can still strip it.
Diagnostic use case
Interpret bsky.app referrers from a growing network and tag links you post so attribution holds across web and app contexts.
What WebmasterID can help detect
WebmasterID records the referrer when sent and normalises bsky.app when it appears. For app contexts that reduce it, UTM-tagged links keep Bluesky attribution accurate as the network grows.
Common mistakes
- Over-reading short-term swings on a still-growing network.
- Assuming every Bluesky click carries a bsky.app referrer.
- Putting personal data in UTM parameters.
Privacy and accuracy notes
The referrer is browser-controlled; its absence is normal, not a failure. WebmasterID reads the referrer when present and never re-identifies a visitor when it is missing.
Related pages
- Fediverse referrer traffic (decentralised social)
The fediverse microblogging network is decentralised: there is no single canonical host, but thousands of independent instances, each on its own domain. Web reads commonly pass that instance's domain as the referrer, so this traffic is often identifiable yet spread across many hosts. Recognising the federation pattern is key to attributing it.
- Threads referrer traffic
Threads is an app-first social platform where most engagement happens in the mobile app. Links tapped there typically open in an in-app browser that does not pass a web referrer, so Threads-driven visits frequently land in direct. UTM tags are the dependable way to attribute Threads traffic.
- Campaign links
Tag Bluesky links so visits are attributed across web and app.
Sources and verification notes
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.