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 (on a single tag). 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.

Outbound link click

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

Outbound link
A link on your site that leads to an external site.
A click from one page on your website that leads to another page on your site. The website in question is located at the URL specified in your tag settings.
Time on site
The time difference between the first and last event in the session (events include pageviews, clicks on outbound links, file downloads and goal completion, including reachGoal method calls).
More information about pageviews

Pageviews are registered when:

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

Attribute that represents user actions registered by the tag (for example, session, pageview, referral, file download, etc.). Data sent in a report is grouped by attribute.

Meeting the criteria set in the goal parameters within a single user 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.

Uploading the file

A file download from the site.


The means by which a user arrived at 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. In the Cross device report, conversion rate is calculated based on the number of users.


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.

Tag ID
A unique number that identifies the data store associated with the tag. It is assigned by the system automatically when the tag is created, and can't be changed. It is specified during initialization of the tag on a page.

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

More information

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” service 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 whatever time you set).


An internet user who visited your site during a particular time interval.

In all Metrica reports other than Cross device, users are registered based on anonymous browser IDs that are saved as cookies. A user who returns to your site after they delete their cookies will be considered new. In the “Cross device” report, data from different browsers used by the same individual are joined together using Crypta technology.

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.

When a user gets to the site by entering a URL in the browser address bar, clicking a saved link, and so on.

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 conversions 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.

Target user
A user who meets the condition set in the goal parameters.

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 how to configure them, see Goals.

A randomly-generated site user ID assigned by Yandex.Metrica. It represents an anonymous instance of a device or browser. It is used for transmitting user parameters and for tracking offline conversions.
The site user ID assigned by the site owner. It is used for transmitting user parameters and for tracking offline conversions.