VK referrer traffic
VK (VKontakte) is a social network widely used in Russian-speaking regions. Shared links can drive visits that appear as referrals from vk.com, often via its away.php outbound redirect. App taps and link wrapping can hide the originating post, so UTM tags are the dependable way to attribute VK traffic.
What this means
VK (VKontakte) is a social network with profiles, communities, and a news feed, used heavily across Russian-speaking audiences. Links shared in posts, communities, or messages can send clicks to your site that show up as VK referrals.
The referrer usually resolves to vk.com, frequently through its away.php outbound redirect. This identifies the platform but rarely the originating wall or community, so platform-level grouping is the practical ceiling from the header alone.
Why the referrer can be missing
VK routes outbound links through away.php, and taps inside the VK mobile app often arrive with no Referer header, landing in direct or unknown traffic. Referrer-policy downgrades reduce detail further.
Tag your VK links with utm_source=vk and utm_medium=social so the query string survives the redirect. Tagged links remain attributable to VK even when the Referer header is stripped or collapsed to the bare host.
- Host you may see: vk.com or vk.com/away.php
- Recommended tags: utm_source=vk, utm_medium=social
- App taps often arrive direct/unknown — UTM recovers them
How it appears in analytics and logs
A referrer on vk.com (or vk.com/away.php) means a visitor followed a link from a VK post, profile, or community. The away.php redirect commonly replaces the original post URL, so you learn the platform but usually not the specific wall or group.
Diagnostic use case
Confirm a referral came from VK, separate feed and community clicks from in-app taps, and attribute a VK post even when the away.php redirect hides the source wall or group.
What WebmasterID can help detect
WebmasterID groups VK referrals as a social channel and reconciles them with your UTM tags, so community-driven clicks stay separate from direct traffic even when away.php strips the post path.
Common mistakes
- Treating vk.com/away.php as spam — it is VK's own outbound redirect.
- Expecting the originating community or wall when only vk.com survives.
- Leaving VK links untagged, losing in-app clicks to direct traffic.
Privacy and accuracy notes
Attribution uses only the Referer header and any UTM parameters. No VK profile, community membership, or individual is identified. WebmasterID records the channel, not the person.
Related pages
- 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.
- 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.
- Attribution analytics
Keep VK community clicks attributable past the away.php redirect.
Sources and verification notes
- VK — AboutPlatform description; away.php redirect behaviour observed.
- 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.