A graphic module that summarizes statistics about the site and its users. Widgets are dipslayed on the Dashboard in Yandex.Metrica

Session (visit)
A sequence of actions (activity) performed on the site by a single user

Yandex.Metrica uses cookies to identify unique users. If cookies are cleared, the browser is reinstalled, or the operating system is reinstalled, the user will be counted as a new user.

(on a single counter). User activity is considered: page views, clicks on outbound links, file downloads, and triggers of the functions reachGoal, hit, params, extLink, file, notBounce.

The session ends when there is no activity for a certain amount of time. By default, this is 30 minutes. You can set a different amount of time using the session timeout option.

For example, the timeout is 30 minutes. A user opens the site and views several pages — the session is registered. Then the user leaves the browser tab open and walks away. Returning 35 minutes later (the timeout period has expired), the user goes to another page on the site. This pageview is considered a new session.

Referrals from advertising systems (such as Yandex.Direct and others) are always considered separate sessions. Even if a user clicked an ad repeatedly (or there were several of them from the same computer) before the session timed out, each of the clicks is a separate session.

External click-through

When a user exits your site by clicking an external link to any other site.

External link
A link on your site that leads to an external site.
Time on site
The time difference between the first and last event in the session (events include pageviews, clicks on external links, downloading files and reaching goals, including reachGoal method calls).
More information about pageviews

Pageviews include:

  • Loading site pages (including page refreshes).
  • Updating AJAX sites, which is detected by the hash parameter changing in the address bar (#fragment).
  • Sending data using the hit method.
Page depth
The number of pageviews on the site during a single session.

Attribute for user actions that are registered by the counter (for example, session, pageview, referral, file download, and so on). Data put in the report is grouped by this attribute.

Goal completion
When the user completes an action set as the goal during the session.
Page loading

The process of displaying webpage contents. There are several stages of loading:

  • Processing DNS requests.
  • Processing redirects.
  • Connecting to the server.
  • Getting the server response.
  • Processing HTML.

Detailed information about page loading is available in the Page load time report.

File download

When the user begins downloading a file from the site.


How a user got to the site: from an ad, search results, social network, or other source.

Conversion rate

The number of conversions as a percentage of the total number of sessions.


A numerical value that is based on an attribute of a session or pageview. This amount can be the total or average. For example, pageviews are calculated as the sum of values, while session depth is the average value.


A session is considered a bounce if it meets all of the following criteria at once:


For calculating session length, user activity is considered: page views, clicks on outbound links, file downloads, and triggers of the functions reachGoal, hit, params, extLink, file, notBounce.

The “non-bounce” internal event is generated in the browser when the set bounce tracking time has passed since the beginning of the session. The registered event time might differ from the actual time due to discrepancies in the time on the server and on the client, or due to latency in sending the event. As a result, a non-bounce session might be registered that is shorter than 15 seconds (or the set duration).


A user who spent a certain amount of time on the site. A user who has a non-duplicated set of characteristics (IP address, browser, OS, cookies, and so on) is considered a unique user. If a user clears cookies, reinstalls the browser, or reinstalls the operating system, this user will be counted as a new user.

Pageview (hit)

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.


Some of the sessions or pageviews, which are selected by a formal attribute (for example, the number of pages viewed).


JavaScript code that the service uses to collect statistical data.

It is also a Yandex.Metrica tracking unit — a container for collecting all information about sessions on your site.


A session in which a goal was completed.

Conversion metric

A numerical value calculated for the goal specified in the report. This amount can be the total or average. For example, conversions are calculated as the total of all values, and conversion per user is calculated as the average value.

Goal-based report

A Yandex.Metrica report that specifies a previously created goal. The report shows conversion metrics that are calculated for the specified goal.


A user action that the site owner is interested in: viewing a specific page, clicking a particular element (such as the “Proceed to Checkout” button), and so on. For more information about types of goals and setting them up, see the section Goals.

If you have questions, contact the support service.