How Yandex Metrica detects the traffic source
Sources of traffic to the site are determined by the referrer (HTTP Referer header) and tags. If you need to replace the referrer with your own, use the utm_referrer parameter.
Yandex Metrica uses a tag to detect traffic sources if the tag is included in the data for the first pageview during a user session. If there isn’t a tag in the first pageview, the traffic source is detected from the referrer.
For example, a user has accessed the site from a browser bookmark (first pageview). Then they have left the site and returned within 30 minutes by clicking a link with a tag from an email newsletter (second pageview in the session). This session would be considered direct traffic to the site.
Source |
How it is detected |
Description |
Default report |
Direct traffic |
Referrer |
Yandex.Metrica attributes traffic to this source in the following cases:
|
|
Link traffic |
Referrer and UTM tags |
Users visited your site by clicking a link on another site. The page URL hosting the link is saved as the referrer. |
|
Search engine traffic |
Users clicked a link to your site in search results. Yandex Metrica can detect the majority of search engines. Yandex Metrica stores the name of the search engine used, usually along with the search query. |
||
Traffic from social networks |
Users followed a link posted on a social network. Most social networks identify the user who posted a link or the community it was posted by. |
||
Yandex Direct traffic |
Conditions for linking a tag to a Yandex.Direct campaign |
Traffic generated by Yandex services (Yandex Direct, Yandex Market), media platforms, and tagged links (such as UTM, Openstat, or Google Ads). To learn more, see the Ad systems report. |
|
Traffic from other ad systems |
Referrer and tags. Complete data is collected only if you create UTM and Openstat tags correctly. |
||
Other advertising: identified by tags |
UTM tags. Conditions that determine the data source. |
||
Messenger traffic |
Referrer and UTM tags. Complete data is only collected if you create UTM tags correctly. |
Clicks on links posted in messengers are identified by the referrer and UTM tags. Learn moreYandex.Metrica collects data on the following messengers:
Use these UTM tags to identify your source of traffic:
|
|
Recommendation system traffic |
Referrer and UTM tags |
Clicks on links in news feeds, personalized recommendation lists, and similar sources. Does not include data from traffic exchange networks and news aggregators (News, Rambler News, and Google News). Learn moreYandex.Metrica recognizes the following recommendation systems:
|
|
Cached page traffic |
Referrer |
Yandex.Metrica attributes traffic to this source in the following cases:
|
|
Internal traffic |
If the user stopped doing anything on the site and the session timeout expired but the browser was still open, when the user later resumes activity Yandex.Metrica registers a new session with “internal traffic” as the source. Note For accurate detection of internal traffic, make sure that the correct website address is shown in the tag settings (in the Tag section). |
||
Mailing traffic |
UTM, Openstat, From tags. Learn more about proper tag creation. |
The user clicked a link in an email. Defined by UTM, Openstat, and from tags. For more information, see How to correctly create a tag |
|
Click-throughs via QR codes |
Traffic to the site via QR codes is detected using UTM tags. For more information, see How to correctly create a tag |
||
Undefined |
— |
Undefined means that some of the session characteristics couldn’t be identified, although the session itself was registered in the system. For instance, Yandex Direct traffic may have Yandex Direct: Undefined listed as the source. That means that Yandex Metrica recognized the ad platform, but couldn't identify details such as the campaign, keyword, and so on. Why sessions aren’t recognizedThere are many reasons why sessions might be “undetected” in Yandex Metrica. For example, if the source of Yandex Direct traffic appears as Yandex Direct: Undefined, this could mean that there was a delay between generating the yclid tag in Yandex Direct and registering the session in Yandex Metrica. This can happen in the following situations:
|
Learn more
Useful links |
Online training |
Loading one of a site’s pages when a user navigates to it. Pageviews also include page refreshes, AJAX site updates, and sending data using the hit method.
A URL parameter processed by Yandex Metrica using a special algorithm. It’s not displayed in the “URL parameters” report. Instead, it’s included in special reports. This lets you create more intuitive and thorough analytic segments.
The sequence of actions (activity) performed by a single user on the site (on a single tag). What is considered as user activity: pageviews, clicks on outbound links, file downloads, and triggers of the functions reachGoal, hit, params, extLink, file, notBounce.