Tumblr referrer traffic
Tumblr is a microblogging and reblogging network where shared links can drive visits. In analytics these arrive as referrals from tumblr.com or the t.umblr.com redirect host, but mobile-app taps and link-shimming often strip the original post URL, so tagging campaign links is the reliable way to attribute Tumblr traffic.
What this means
Tumblr is a reblog-centric microblogging platform. When someone posts a link or reblogs a post containing your URL, clicks can appear in your analytics as referrals. Because reblogs propagate across many blogs, a single post can surface from many different Tumblr pages.
The referrer typically resolves to tumblr.com or the t.umblr.com outbound redirect host. That tells you the platform but rarely which blog or post sent the click, so platform-level grouping is the most you can rely on from the header alone.
Why the referrer can be missing
Tumblr passes outbound links through a redirect, and taps inside the Tumblr mobile app frequently arrive with no Referer header at all — those land in direct or unknown traffic. Browser referrer-policy downgrades and in-app webviews further reduce what reaches you.
To keep Tumblr attributable, add UTM parameters to the links you share, for example utm_source=tumblr and utm_medium=social. The query string survives the redirect even when the Referer header does not, so tagged links remain countable as Tumblr regardless of policy or app behaviour.
- Host you may see: tumblr.com or t.umblr.com (redirect)
- Recommended tags: utm_source=tumblr, utm_medium=social
- In-app taps often arrive as direct/unknown — UTM recovers them
How it appears in analytics and logs
A referrer on tumblr.com or t.umblr.com means a visitor followed a link from a Tumblr post or dashboard. The path is frequently absent because Tumblr routes outbound clicks through a redirect host, so you usually learn the platform but not the originating blog or post.
Diagnostic use case
Confirm whether a referral came from Tumblr, separate web reblog clicks from in-app taps, and attribute a post that went around Tumblr even when the referrer collapses to the bare host.
What WebmasterID can help detect
WebmasterID groups Tumblr referrals as a social channel and reconciles them with the UTM tags on your shared links, so reblog-driven visits stay distinct from direct traffic even when the post path is stripped.
Common mistakes
- Assuming t.umblr.com is spam — it is Tumblr's own outbound redirect host.
- Expecting the originating blog or post URL in the referrer when only the platform host survives.
- Leaving Tumblr links untagged, so in-app clicks fall into direct traffic.
Privacy and accuracy notes
Referrer attribution uses only the HTTP Referer header and any UTM parameters you add. No Tumblr account, blog identity, or individual user is identified. WebmasterID records the channel, not the person behind the click.
Related pages
- Dark social traffic explained
Dark social describes sharing that happens through private channels — messaging apps, email, copied links — where no referrer reaches your site. These visits are real but unattributed, so they inflate the direct bucket. UTM tagging on your own links is the practical way to expose some of it.
- UTM vs referrer: which wins
When a visit carries both a referrer and UTM campaign parameters, most analytics treat the explicit UTM source as authoritative over the inferred referrer. That is usually correct: UTM tags describe intent you set deliberately, while a referrer is whatever the browser happened to send. Understanding the precedence prevents double-counting and mis-attribution.
- Campaign links
Tag Tumblr links so reblog clicks stay attributable past the redirect.
Sources and verification notes
- Tumblr — About / helpPlatform description; redirect-host behaviour observed, not version-specific.
- 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.