---
metadata:
  - name: generator
    content: Diplodoc Platform v5.63.1
alternate:
  - https://www.yandex.com/support/metrica/en/general/goal-page-visit.md
  - https://www.yandex.com/support/metrica/es/general/goal-page-visit.md
  - https://www.yandex.com/support/metrica/pt/general/goal-page-visit.md
  - https://www.yandex.com/support/metrica/ru/general/goal-page-visit.md
  - https://www.yandex.com/support/metrica/tr/general/goal-page-visit.md
  - href: https://www.yandex.com/support/metrica/en/general/goal-page-visit.md
    type: text/markdown
    title: Markdown version
  - href: https://www.yandex.com/support/metrica/en/llms.txt?revision=r21566194
    rel: describedby
title: Page view goal
description: This goal type enables you to track traffic to a specific page or multiple pages, outbound clicks, and file downloads.
---
> **Documentation Index:** Fetch the complete configuration index at https://www.yandex.com/support/metrica/en/llms.txt?revision=r21566194


# "Page view" goal

This type of goal lets you track:
- Traffic to a specific page or multiple pages.
- Outbound clicks.
- File downloads.


{% note tip %}

Some users might complete the goal somewhere other than on the site, such as by making a phone call. To count these users, [set up sending call tracker data to Yandex Metrica](https://www.yandex.com/support/metrica/en/data/calls.md). Then you can add calls to Yandex Metrica reports and also [use a special group of reports](https://www.yandex.com/support/metrica/en/reports/calls.md).

{% endnote %}


- [How to create a “Page view” goal](#create-goal)
- [Restrictions](#general)
- [Examples](#example)

## How to create a "Page view" goal {#create-goal}

1. In Yandex Metrica, select **Goals** from the left menu.
1. Click **Add goal**.
1. Select the **Page view** goal type.
1. In the **Name** field, enter a name for the goal to create.
1. Specify [the desired condition](#rule). You can add up to 10 conditions.
1. Click **Add goal**. The created goal will appear in the list of goals. Yandex Metrica will start collecting statistics on it within a few minutes.
1. [Check](https://www.yandex.com/support/metrica/en/general/check-goal.md) whether the goal is working correctly.

![](../_assets/goal-page-visit.png){.border-yes}

### Conditions for tracking a goal {#rule}

There are several types of conditions available when creating a goal. Conditions are combined with the OR operator, so the goal is considered completed if at least one of the set conditions is met.

<!-- source: en/_includes/general/goal-page-visit/id-create-goal/table_ewv_qzj_5cb.md -->
#|
||
**Criterion**
|
**Description**
||
||
**url: matches**
|
If you select the full address in the settings, the tag will track sessions where the page address is identical, including the protocol (`http://` or `https://`), domain, and all parameters after the `?` sign (if any) excluding the UTM tags.

If you select the path to the page in the settings, the tag will track sessions with matches between the domain name of the tag and the domain name on which the specified page is located. Note that the page's path that comes after the slash `/` must exactly match the path specified in the tag settings.


{% cut "Example" %}

URL matches: `/metrika`, the `example.com` and `mysite.com` domains are specified in the addresses.
The goal will trigger for the following URLs (because the path matches and the domains are specified in the settings):

- `http://example.com/metrika`.
- `http://mysite.com/metrika`.
- `https://example.com/metrika`.
- `https://mysite.com/metrika`.
- `https://example.com/metrika/?utm_source=123`.

The goal will not trigger for the URL:

- `http://test.ru/metrika` (the path matches, but the address is not specified in the tag settings).
- `http://example.com/metrika/test` (the path does not match).
- `https://example.com/?test=123` (the URL contains parameters).
- `http://example.com` (the path does not match).


{% endcut %}


In both cases, if a user lands on a page where the tag is installed, and the page URL completely matches the one specified in the settings, the tag will count this session.
||
||
**url: contains**
|
Specify part of a URL. Use this option if there are multiple target pages and they can be combined with a single condition. Specify as much of the URL as possible so the goal is only completed on the desired pages.

{% cut "Example" %}

If the condition is `/abc`, the goal will be completed on the pages `example.com/abc-1`, `example.com/abc/2`, and `example.com/abcd`.

{% endcut %}
||
||
**url: begins with...**
|
Only the first part of the URL is specified. Use this condition if you want to track views in subdirectories.

{% cut "Example" %}

If the condition is `https://example.com/abc/`, the goal will be completed on the pages `https://example.com/abc/1`, `https://example.com/abc/2`, and `https://example.com/abc/1/2/3`.

{#ex}

{% endcut %}
||
||
**url: regular expression**
|
Used for tracking URLs that match a [custom pattern](https://www.yandex.com/support/metrica/en/general/regexp.md)
||
|#
<!-- endsource: en/_includes/general/goal-page-visit/id-create-goal/table_ewv_qzj_5cb.md -->

When handling the condition, such symbols as `?`, `#`, `&`, and the dot (`.`) are removed from the end of the URL. For example, the URLs `http://example.com/?`, `http://example.com/#`, and `http://example.com/?var=1&` will be compared to `http://example.com/`, `http://example.com/`, and `http://example.com/?var=1`, respectively. To add these symbols, except the dot, to the URL, use the **url: regular expression** condition.

To avoid accidental goal triggers due to overlaps with similar URLs on the site, don't use conditions that are too short. For example, if the goal condition specifies a URL containing `cart` and the site's domain name is `bestcartoons.ru`, the goal is achieved when a user views any page of the site.

To trigger the goal for pageviews on pages with a `+` symbol in their URL, specify `%2B` in the template instead of `+`.

{% cut "Example" %}

![](../_assets/goal-plus.png){.border-yes}

{% endcut %}


## Restrictions {#general}

- A maximum of 200 goals can be set for each tag.
- The service registers a user reaching the same goal on the same counter no more than once per second.
- During a single user session, the service can register up to 1000 offline conversions and 400 online conversions created for the tag.
- If you edit the tag or a goal, all the previously collected information does not change.
- If you delete a goal, information collected for it is no longer available in reports.


## Examples {#example}

> {% cut "Tracking outbound clicks" %} {#ex-external-link}
> 
> 
> The tag owner's site has the page `http://example.com/page1/` with a link to the external resource `http://external-example.com/`.
> 
> 1. Set the type of condition to "url: contains".
> 1. Specify the condition as `https://external-example.com`.
> 
> 
> {% endcut %}
> 
> {% cut "Tracking file downloads" %} {#ex-file}
> 
> 
> 1. Set the type of condition to "url: contains".
> 1. Enter the full or partial path to the file (or its name) on your site as the condition. For example, `https://example.com/files/name.pdf` or `name.pdf`. If you specify a name as the condition, make sure it doesn’t overlap with other file or page names on the website.
> 
> 
> {% endcut %}

### Learn more

- [Track clicks on an email address](https://www.yandex.com/support/metrica/en/simple-goal/email.md)
- [Track click on phone number](https://www.yandex.com/support/metrica/en/simple-goal/tel.md)
- [How to create a report for a goal](https://www.yandex.com/support/metrica/en/reports/goals.md)
- [Revenue by goal](https://www.yandex.com/support/metrica/en/general/price-goal.md)

<!-- source: en/_includes/buttons/chat-button.md -->
[Chat with us](https://yandex.com/chat/#/user/036e6a02-3620-9cdc-4c5e-a34667a7379e?utm_source=spravka){.button}

<!-- source: en/_includes/styles/href-to-button.md -->

<!-- endsource: en/_includes/styles/href-to-button.md -->
<!-- endsource: en/_includes/buttons/chat-button.md -->

<!-- source: en/_includes/reports/texing-button.md -->
<div class="cut-button">

{% cut "Write an email" %}

{% list tabs radio %}

- No data for a particular source

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

  {% cut "The recommendations did not help" %}

  <!-- source: en/_includes/popup/id-popup/wrong-sup.md -->
  Please note: Our support team will never initiate a call to you. Do not follow any instructions of people who call you and introduce themselves as the Yandex Metrica support team.
  <!-- endsource: en/_includes/popup/id-popup/wrong-sup.md -->

  <div style="padding: 15px;
       margin: 10px 0;
       background: #FFFFFF;
       border-radius: 10px;
       border: 1px solid var(--g-color-line-generic);">
    <iframe style="background: #FFFFFF;"
          height="700"
          width="100%"
          frameborder="0"
          src="https://forms.yandex.com/surveys/1706/?&theme=Net dannyh po opredelennomu istochniku&iframe=1&lang=en">
    </iframe>
  </div> 

  {% endcut %}

- Data for a goal doesn’t match real data

  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.

  {% cut "The recommendations did not help" %}

  <!-- source: en/_includes/popup/id-popup/wrong-sup.md -->
  Please note: Our support team will never initiate a call to you. Do not follow any instructions of people who call you and introduce themselves as the Yandex Metrica support team.
  <!-- endsource: en/_includes/popup/id-popup/wrong-sup.md -->

  <div style="padding: 15px;
       margin: 10px 0;
       background: #FFFFFF;
       border-radius: 10px;
       border: 1px solid var(--g-color-line-generic);">
    <iframe style="background: #FFFFFF;"
          height="700"
          width="100%"
          frameborder="0"
          src="https://forms.yandex.com/surveys/1706/?&theme=Dannye po celi otlichayutsya ot realnyh dannyh&iframe=1&lang=en">
    </iframe>
  </div> 

  {% endcut %}

- Goal doesn’t work
  
  <div style="padding: 15px;
       margin: 10px 0;
       background: #FFFFFF;
       border-radius: 10px;
       border: 1px solid var(--g-color-line-generic);">
    <iframe style="background: #FFFFFF;"
          height="700"
          width="100%"
          frameborder="0"
          src="https://forms.yandex.com/surveys/10018080.618d9fdb2524ebc4674fd9e2a54cd71036f465a9/?&theme=Cel ne rabotaet&iframe=1&lang=en">
    </iframe>
  </div> 

{% endlist %}  

{% endcut %}

</div>

<!-- source: en/_includes/styles/cut-button.md -->

<!-- endsource: en/_includes/styles/cut-button.md -->
<!-- endsource: en/_includes/reports/texing-button.md -->


<!-- source: en/_includes/footer-links.md -->
- - -

<div class="borderless-table">

#|
||
Useful links

- [Demo tag](https://metrica.yandex.com/r/dashboard?)
- [Add a tag](https://metrica.yandex.com/add/)
- [Free tag setup](https://yandex.com/promo/freeservice/metrica?utm_source=help_metrica_en&utm_medium=cpc&utm_campaign=1)
- [Yandex Metrica API](https://tech.yandex.com/metrika/)
- [Suggest your idea](https://yandex.com/support/metrica/troubleshooting/idea.html)
- [Discuss in Telegram](https://t.me/yandexmetrika)
|
Online training

- [Get a Yandex Metrica certificate](https://yandex.ru/adv/expert/exam/metrika/?utm_source=metrika_help&utm_medium=web&utm_campaign=static&utm_content=useful_links)


- [Take a training course](https://yandex.com/adv/edu/online/metrika?utm_source=metrika_help&utm_medium=web&utm_campaign=static&utm_content=useful_links)

||
|#

</div>

<!-- source: en/_includes/styles/table-style.md -->

<!-- endsource: en/_includes/styles/table-style.md -->
<!-- endsource: en/_includes/footer-links.md -->

<!-- source: en/_includes/styles/href-to-button.md -->

<!-- endsource: en/_includes/styles/href-to-button.md -->

<!-- source: en/_includes/styles/cut-button.md -->

<!-- endsource: en/_includes/styles/cut-button.md -->