“From tags” report

This report includes statistics on from tags if you use them in links to your site.

To view the report: Reports → Standard reports → Sources → From tags.

Ways to use this report

Tags help you track traffic sources to your site more accurately. For example, if you placed multiple links to your site on another resource, you can tell them apart by the from tag values:
https://source-example.com/partner/offer/
#section with the first link
https://example.com/?from=source-example-offer
#first link to your site

https://source-example.com/partner/about/
#section with the second link
https://example.com/?from=source-example-about
#second link to your site

Report structure and settings

The information provided in the report is grouped based on the value of the from tag. The report supports all settings available in Yandex Metrica.

Select a question to find a solution.

No data or not enough ad data
Data differs from statistics in another system
Internal traffic increased
No traffic from a particular site
Problem getting data on UTM labels

Yandex Metrica receives information about different advertising systems from labels, which are parameters in the ad's link. If an ad system doesn't add a special label to your link, you can manually form the link using the UTM or Openstat label. For the complete list of values, see the "Advertising systems" report section.

There could be several reasons for this.

Imagine the path from the user clicking the link to the Yandex Metrica report:
  1. Creating the label for the link.
  2. Clicking the link and through to the site.
  3. Loading the code snippet for the tag on the site.
  4. Collecting data for the label and analyzing reports.
As a result, there are many steps between the first and last stage where data could be lost.
Imagine the path from the user clicking the link to the Yandex Metrica report:
  1. Creating the label for the link.
  2. Clicking the link and through to the site.
  3. Loading the code snippet for the tag on the site.
  4. Collecting data for the label and analyzing reports.
As a result, there are many steps between the first and last stage where data could be lost.
Reasons at the label creation stage
  • Labels aren't formed correctly: required values are missing, parameter names are incorrect, there are superfluous question mark symbols or spaces, and so on.
  • When copying ads from one ad system to another, the labels weren't changed, so the traffic is linked to another ad system.
Reasons at the click stage
  • The user stopped the page from loading and closed the page before it opened. This could be an accidental click on a mobile phone or tablet.
  • The page didn't load due to problems with site accessibility or it loaded incorrectly in a certain browser.
  • The ad specifies a URL that redirects to a page that doesn't have the Yandex Metrica tag installed.
  • The ad specifies a URL that redirects to another page, and the UTM labels are lost.
  • When the user goes to the site, other scripts that are loading block the tag from working.
  • The ad specifies an invalid URL that doesn't open a page.
Reasons at the code snippet loading stage
  • The Yandex Metrica tag isn't installed on landing pages or it's installed incorrectly.
  • The tag didn't load on the site because the user's browser (or the corporate proxy server) has a plugin that prohibits downloading tracking tags.
  • The user's antivirus system blocks the tag from loading.
Reasons at the report analysis stage

If you are comparing reports for Yandex Metrica and another system or ad management account, data might differ. This is due to the fact that services have different ways of registering a user's interaction with a site.

For example, in the ad manager, a click might be registered for going to the site as well as for opening details about an ad or going to a social media page. Yandex Metrica only counts the users who go to the site.

You might also have different attribution models chosen in ad managers.

See the additional information and tutorial video in the section About the Labels report group.



Yandex Metrica and other web analytics systems and ad managers have different ways of registering a user's interaction with a site and calculating statistics. For example, in the ad manager, a click might be registered for going to the site as well as for opening details about an ad or going to a social media page. Yandex Metrica only counts the users who go to the site.

Also check that:

  • You are comparing correct data for the same time period in Yandex Metrica and the other system.
  • Last click attribution is used by default in Yandex Metrica reports. If necessary, change the attribution settings in Yandex Metrica to make them match the attribution settings in your system.
This might happen for the following reasons:
  • Excessively narrow filters are set in Yandex Metrica in Settings → Filters. As a result, not all of the data is collected.
  • Yandex Metrica filters robots out of statistics. It's possible that the other system included robot traffic in their statistics. You can check for robot traffic on the site in Standard reports → Monitoring → Robots.
  • The tag didn't load on the site because the user's browser (or a corporate proxy server) has a plugin that prohibits downloading tracking tags. Antivirus systems with high security might also prevent tags from loading.

Also make sure that the Yandex Metrica tag is installed on all the domains and subdomains that the other system is collecting statistics for. To see data for domains that have the Yandex Metrica tag installed, go to Standard reports → Content → Popular.


This might happen for the following reasons:

  • Robot filtering is turned off in Yandex Metrica in Settings → Filters. As a result, the reports show data for all the robot traffic on the site.
  • The other system has overly strict filters defined.
  • The other system's tag isn't installed on all the domains, including mobile versions of the site.


This might happen for the following reasons:

  • One of the site's landing pages doesn't have the code snippet embedded on it.
  • The site might have JavaScript code that runs before the snippet and performs an internal redirect on the site. For example, this could be code for A/B testing. You can detect this code by a redirect on the site (this is usually a redirect to the same page on the site with extra parameters added to the URL). To solve this issue, contact your webmaster.
  • Your hosting provider might have enabled protection from DDoS attacks. This could add redirects before going to the site. Contact your hosting provider and ask them to disable this protection.

Choose the protocol your site uses:

In this case, you won't see the traffic source if this source uses a secured HTTPS connection.

  • You can switch your site to a secure HTTPS connection. You can get an encryption certificate for free through the Let's Encrypt project, which is a non-profit certification center supported by many prominent representatives of the internet industry.
  • If you can edit links on the source website, add the utm_referrer label to them and specify the source site as the value. For more information, see About the Labels report group.

The source site might be encrypting the referrer. In this case, you won't be able to solve the problem within your site or Yandex Metrica.

Add the utm_referrer tag to the website's links and specify the source site as the tag's value.


Imagine the path from the user clicking the link to the Yandex Metrica report:
  1. Creating the label for the link.
  2. Clicking the link and through to the site.
  3. Loading the code snippet for the tag on the site.
  4. Collecting data for the label and analyzing reports.
As a result, there are many steps between the first and last stage where data could be lost.
Reasons at the label creation stage
  • Labels aren't formed correctly: required values are missing, parameter names are incorrect, there are superfluous question mark symbols or spaces, and so on.
  • When copying ads from one ad system to another, the labels weren't changed, so the traffic is linked to another ad system.
Reasons at the click stage
  • The user stopped the page from loading and closed the page before it opened. This could be an accidental click on a mobile phone or tablet.
  • The page didn't load due to problems with site accessibility or it loaded incorrectly in a certain browser.
  • The ad specifies a URL that redirects to a page that doesn't have the Yandex Metrica tag installed.
  • The ad specifies a URL that redirects to another page, and the UTM labels are lost.
  • When the user goes to the site, other scripts that are loading block the tag from working.
  • The ad specifies an invalid URL that doesn't open a page.
Reasons at the code snippet loading stage
  • The Yandex Metrica tag isn't installed on landing pages or it's installed incorrectly.
  • The tag didn't load on the site because the user's browser (or the corporate proxy server) has a plugin that prohibits downloading tracking tags.
  • The user's antivirus system blocks the tag from loading.
Reasons at the report analysis stage

If you are comparing reports for Yandex Metrica and another system or ad management account, data might differ. This is due to the fact that services have different ways of registering a user's interaction with a site.

For example, in the ad manager, a click might be registered for going to the site as well as for opening details about an ad or going to a social media page. Yandex Metrica only counts the users who go to the site.

You might also have different attribution models chosen in ad managers.

See the additional information and tutorial video in the section About the Labels report group.