“Session duration” goal

This goal type allows you to track sessions that exceed a specific duration.

Session duration is the time difference between the first and last event a user triggers on the site. The first event is always the loading of the tag on the page. The last event can be a pageview, an external link click, a file download, a conversion, a non-bounce event, or a parameter submission.

  1. How to create a “Session duration” goal
  2. Restrictions

How to create a “Session duration” goal

  1. In the Yandex Metrica interface, click on Goals in the left menu.
  2. Click Add goal.
  3. In the Name field, enter a name for the goal to create.
  4. Select the Session duration goal type.
  5. Use the Hours, Minutes, and Seconds fields to set the session duration that marks goal completion.
  6. Click Add goal. The created goal appears in the list of goals. Yandex Metrica will start collecting statistics on it within a few minutes.
  7. Check if the goal is working correctly.


Restrictions

  • A maximum of 200 goals can be set for each tag.
  • The service registers a user that completes the same goal on the same tag no more than once per second.
  • During a single user session, the service can register up to 400 completions of all the goals created for a tag.
  • If you edit a tag or goal, previously collected information doesn't change.
  • If you delete a goal, information collected for it is no longer available in reports.

Select a question to find a solution.

Goals in Yandex Metrica work the same way for any source. Perhaps there aren't any users who have completed the goal from this source yet.


This might happen for the following reasons:
  • The goal condition in Yandex Metrica doesn't cover all the possibilities. For example, the goal is set as going to the order confirmation page, but the site also allows instant checkout without visiting this page.
  • The site user has a browser plugin that blocks the Yandex Metrica tag, so this user isn't counted.
  • The user has an antivirus system with strict privacy settings.
  • The user has a slow internet connection, so the Yandex Metrica tag didn't load on the target page.