Start a conversation

Integration with Yandex Metrica

1. Connecting a Yandex account

2. Settings

3. Yandex.Metrica parameters

4. Results of the data analysis

1. Connecting a Yandex account

To add a Yandex account, open the ‘Yandex.Metrica’ tab of the program settings.

Connection to yandex

Once you click on the ‘Add new Yandex account’ button, the new tab will be automatically opened in your browser. Select necessary account and allow Netpeak Spider to view data from Yandex.Metrica.

Once the access is granted, the program will add and remember your account in the settings. If necessary, you can add several accounts and use them simultaneously. The list of saved accounts will be displayed in the corresponding field:

Saved Yandex account

2. Settings

Yandex.Metrica settings are saved in the program and do not change when you open another project in Netpeak Spider. After adding Yandex account(s), all segments and counters available in it will be automatically loaded into the corresponding settings fields.

2.1. Yandex.Metrica settings

All Yandex accounts connected to Netpeak Spider are displayed in the ‘Yandex.Metrica settings’ subsection. For each account you can choose:

  • site
  • segment
  • date range
  • devices.

In ‘Segment‘ drop-down menu you can choose one of the custom segments you need to get data for.

Segments from yandex

In the ‘Date Range‘ drop-down menu, you can specify the period for downloading data from the service. The menu contains the following ranges:

  • Current month
  • Current year
  • Last 7 days
  • Last 30 days
  • Last 90 days
  • Last 365 days
  • Previous week
  • Previous month
  • Custom

metrica data range

The Yandex.Metrica service has a one-day delay in receiving data, which is automatically taken into account by the program.

The ‘Devices’ filter allows you to select a device to view data accordingly. For example, search traffic  to a desktop or mobile version of the site.
 
You can choose a device type in a corresponding drop-down menu:

  • all
  • desktop,
  • tablet,
  • TV,
  • mobile,
  • mobile & tablet.

Yandex.Metrica service API allows to obtain data without sampling only for small number of requests.
To receive data without sampling for large queries, the program splits the period on a monthly basis and summarizes the data. Because of it, the values of some parameters in the Y.M interface may not coincide with the data obtained in Netpeak Spider.

2.2. Proxy settings for accessing Yandex services

In case you need to use a proxy when accessing Yandex services, follow these steps:

  1. Tick the ‘Use proxy for Yandex.Metrica’ checkbox on the ‘Yandex.Metrica’ tab of the program settings.
  2. Tick the ‘Use list of HTTP proxies’ checkbox on the ‘Proxy’ tab of the program settings and configure proxies. 

If several proxies are added, the program will use the first proxy from the list.

To find out how to work with proxies in Netpeak Spider, read the article ‘Proxy settings’.

3. Yandex.Metrica parameters

Netpeak Spider has the following Yandex.Metrica parameters:

Users — total number of website users according to Yandex.Metrica (considering the chosen tag, date range, and segment).

Note that this parameter is defined according to the 'Landing page'. This means it shows the number of unique users for whom the target page was the first visited page.


• Sessions — total number of sessions according to Yandex.Metrica (considering the chosen tag, date range, and segment). A session is the time period when a user is actively engaged with your website.

Note that this parameter is defined according to the 'Landing page'. Which means it shows the number of sessions for which the target page was the first visited page.


Bounce Rate — bounce rate of a URL according to Yandex.Metrica (considering the chosen tag, date range, and segment). Counted as the ratio of [number of sessions, during which only one page view lasting less than 15 seconds took place] to [number of all sessions].


• Time on site — average session duration (in seconds) according to Yandex.Metrica (considering the chosen tag, date range, and segment). Counted by dividing the whole session duration of all users by the number of sessions.

Note that this parameter is defined according to the 'Landing page'. Which means it shows the average session duration of the users for whom the target page was the first visited page.


• All goals — includes parameters from Yandex.Metrica that are set for all goals of the tag. The parameters show the efficiency of specific landing pages in terms of goal completions on a website.


All Goals Reached — total number of completions for all goals according to Yandex.Metrica (considering the chosen tag, date range, and segment).

Note that this parameter is defined according to the 'Landing page'. This means it shows the number of goal completions for sessions for which the target page was the first visited page.


Conversion Rate by Any Goals — the percentage of visits that resulted in a conversion to any of the goals according to Yandex.Metrica (considering the chosen tag, date range, and segment). 

Ecommerce — includes parameters of the 'Ecommerce' group from Yandex.Metrica. Ecommerce reports include data on purchases made on your site.


• Number of purchases — total number of completed purchases on a website according to the 'Ecommerce' reports in Yandex.Metrica (considering the chosen tag, date range, and segment).

Note that this parameter is defined according to the 'Landing page'. This means it shows the total number of completed purchases for sessions for which the target page was the first visited page.


• Revenue — total number of completed purchases on a website according to the 'Ecommerce' reports in Yandex.Metrica (considering the chosen tag, date range, and segment).

Note that this parameter is defined according to the 'Landing page'. This means it shows the total number of completed purchases for sessions for which the target page was the first visited page.

 

Learn more about parameters analyzed by Netpeak Spider in the article ‘What SEO parameters does Netpeak Spider check? ’.

Fetching Yandex.Metrica parameters is performed once the crawling is finished or suspended. It also can be started manually when crawling is finished via the ‘Analysis’ module in case the corresponding parameters were disabled before the crawling started or if it is necessary to analyze them separately from other parameters.

get data from metrica

4. Results of the data analysis

Once the parameters are fetched from Yandex.Metrica, you can view them:

• in the ‘All results’ report

• on the ‘Dashboard’ panel

• in the ‘Overview’ tab in a sidebar

• in the issue reports from the ‘Reports’ tab in a sidebar

• in the ‘Express audit of the optimization quality (PDF)’ report

4.1. On the ‘Dashboard’ panel

Netpeak Spider displays pie-chart based on data from Yandex.Metrica on the ‘Dashboard’ tab in the main table and in the ‘Express audit of the optimization quality’ report:

Get traffic from Yandex in dashboard

4.2. In the ‘Overview’ tab in a sidebar

On the ‘Overview‘ tab of the sidebar, you can quickly filter the pages from the main table that get traffic using the ’YM: Get Traffic’ item.

An item has two filters:

  • TRUE – pages that get traffic,
  • FALSE – pages with zero traffic.

Overview

4.3. In the issue reports from the ‘Reports’ tab in a sidebar

Netpeak Spider generates 3 issue reports based on collected data from Yandex.Metrica:


• YM: Non-Compliant Pages with Traffic — shows addresses of the pages that are not available for indexing by search engines but did drive traffic for the specified period (according to Google Analytics). Note that the issue is only relevant to the segments including organic search traffic.


• YM: Max Bounce Rate —  shows addresses of compliant pages which bounce rate exceeds 70% (by default) according to Yandex.Metrica. Note that you can change the default value on the 'Restrictions' tab of crawling settings.


• YM: Compliant Pages w/o Traffic — shows addresses of pages available for indexing by search engines that didn't drive any traffic for the specified period (according to Google Analytics). Note that the issue is only relevant to the segments including organic search traffic.


4.4. In the ‘Express audit of the optimization quality (PDF)’ report

Learn more about issue reports generated by Netpeak Spider in the article ‘What SEO issues does Netpeak Spider detect?’.

Choose files or drag and drop files
Was this article helpful?
Yes
No

Still Thinking?

Thousands of specialists around the world use Netpeak Spider and Checker. Register to start your 14-day free trial!