Tistory referrer traffic
Tistory is a popular Korean blogging platform operated by Kakao, where each blog lives on a subdomain of tistory.com. Links in blog posts can appear as tistory.com referrals, but referrer-policy downgrades and subdomain handling can blur which blog or post sent the click, so UTM tags keep blog referrals attributable.
What this means
Tistory is a widely used Korean blogging service run by Kakao. Each blog occupies its own subdomain such as example.tistory.com, and bloggers frequently link out to products, tutorials, and news. A click from a post can arrive as a tistory.com referral.
Because blogs are subdomains, the host portion can tell you which blog sent the visitor, but the specific post path depends on the referrer policy in effect.
Keeping blog referrals attributable
A strict referrer policy on a Tistory blog can reduce the Referer to the bare host, and aggregated views or reader apps may drop it entirely into direct traffic. Custom-domain blogs may surface under their own host rather than tistory.com.
Tag links you place in Tistory posts with utm_source=tistory and utm_medium=referral so the query string survives trimming and custom-domain mapping. Tagged links keep a post-driven spike attributable to Tistory even when only the host or nothing survives in the Referer.
- Host you may see: a subdomain of tistory.com
- Recommended tags: utm_source=tistory, utm_medium=referral
- Custom-domain blogs may show their own host instead
How it appears in analytics and logs
A referrer on a tistory.com subdomain means a visitor followed a link from a Tistory blog post. You learn the platform and often the blog subdomain, but the exact post may not survive a policy downgrade.
Diagnostic use case
Confirm a referral came from Tistory, distinguish one blog subdomain from another, and attribute a post-driven spike even when the post path is stripped.
What WebmasterID can help detect
WebmasterID groups Tistory referrals as a referral channel and reconciles them with your UTM tags, so Korean blog clicks stay distinct from direct traffic even when the post path is trimmed.
Common mistakes
- Treating each tistory.com subdomain as a separate unknown source instead of one platform.
- Leaving post links untagged, losing custom-domain blogs to direct traffic.
- Expecting the post path when only the blog subdomain survives.
Privacy and accuracy notes
Attribution uses only the Referer header and any UTM parameters. No Tistory account or visitor is identified. WebmasterID records the channel, not the person.
Related pages
- Naver Cafe referrer traffic
Naver Cafe is the community-forum service inside South Korea's Naver portal, where members run topic-based groups. Links shared in cafes can carry a cafe.naver.com referrer, but app usage and member-only contexts often strip it. This page explains what a Naver Cafe referrer means and how UTM tags keep Korean community traffic measurable.
- KakaoTalk referrer traffic
KakaoTalk is the leading messaging app in South Korea. Links shared in chats or KakaoTalk channels open in its in-app browser, which usually sends no Referer header, so the traffic looks direct. UTM tags are the reliable way to attribute KakaoTalk-driven visits.
- Referrer grouping into channels
Analytics platforms do not report every raw referrer separately — they map hosts into channel groups such as organic search, paid, social, referral, email, and direct. Understanding the default rules explains why a click ends up in one bucket versus another, and why a custom source can be misfiled until you adjust the grouping.
- Attribution analytics
Keep Tistory blog clicks attributable across subdomains and custom domains.
Sources and verification notes
- Tistory — ServiceKorean blogging platform; subdomain and referrer behaviour observed, not a documented metric.
- 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.