Automatic goals
Yandex.Metrica collects data about different actions that users perform on a website. It can create goals automatically based on certain ones:
| Action on the website | What Yandex.Metrica tracks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Click on email | All email addresses. Yandex.Metrica recognizes email addresses by the presence of mailto:<email address> in links. | ||||||||
| Click on phone | All phone numbers. Yandex.Metrica recognizes phone numbers by the presence of tel in links. | ||||||||
| Click on button | Clicks on all buttons or other clickable elements on the website. Yandex.Metrica recognizes clickable website elements by the presence of the following tags: a, button, div, and input. | ||||||||
| Opening a messenger | Transitions to any messenger used for feedback on the website. For example, WhatsApp, Viber, VK Messenger, Facebook Messenger, and others. Yandex.Metrica recognizes messengers by the presence of their URLs in links. | ||||||||
| Form submission | Submission of all feedback forms on the website. A form is identified by the presence of the form element on the website and some form parameters: id, name, or the path to the DOM element. | ||||||||
| File download | Downloads of any files on the website.
File types Supported extensions
| ||||||||
| Site search | How often people use site search. Yandex.Metrica recognizes addresses by the presence of q, text, query, or search. | ||||||||
| Service events | Events transmitted by services integrated with Yandex.Metrica: Jivo, Nethouse, and others. | ||||||||
| Clicks to social networks | Transitions to any social network that is added to the site. For example: Instagram, VK, Facebook, YouTube, and others. Yandex.Metrica recognizes social networks by the presence of their URLs in links. | ||||||||
| Transition back from payment system | How often users return to the site after clicking through to a payment system. Yandex.Metrica recognizes payment systems by the presence of their URLs in the referrer. | ||||||||
| Basket | How often site users open the shopping basket page on an online store's website. | ||||||||
| Purchase | The number of orders placed on an online store's website. | ||||||||
| Entering contact information | Entering contact information in form fields on site pages. If the Use advanced tracking settings option is enabled in the tag settings, the goal is created when contact information is first entered on the site. |
| Action on the website | What Yandex.Metrica tracks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Click on email | All email addresses. Yandex.Metrica recognizes email addresses by the presence of mailto:<email address> in links. | ||||||||
| Click on phone | All phone numbers. Yandex.Metrica recognizes phone numbers by the presence of tel in links. | ||||||||
| Click on button | Clicks on all buttons or other clickable elements on the website. Yandex.Metrica recognizes clickable website elements by the presence of the following tags: a, button, div, and input. | ||||||||
| Opening a messenger | Transitions to any messenger used for feedback on the website. For example, WhatsApp, Viber, VK Messenger, Facebook Messenger, and others. Yandex.Metrica recognizes messengers by the presence of their URLs in links. | ||||||||
| Form submission | Submission of all feedback forms on the website. A form is identified by the presence of the form element on the website and some form parameters: id, name, or the path to the DOM element. | ||||||||
| File download | Downloads of any files on the website.
File types Supported extensions
| ||||||||
| Site search | How often people use site search. Yandex.Metrica recognizes addresses by the presence of q, text, query, or search. | ||||||||
| Service events | Events transmitted by services integrated with Yandex.Metrica: Jivo, Nethouse, and others. | ||||||||
| Clicks to social networks | Transitions to any social network that is added to the site. For example: Instagram, VK, Facebook, YouTube, and others. Yandex.Metrica recognizes social networks by the presence of their URLs in links. | ||||||||
| Transition back from payment system | How often users return to the site after clicking through to a payment system. Yandex.Metrica recognizes payment systems by the presence of their URLs in the referrer. | ||||||||
| Basket | How often site users open the shopping basket page on an online store's website. | ||||||||
| Purchase | The number of orders placed on an online store's website. | ||||||||
| Entering contact information | Entering contact information in form fields on site pages. If the Use advanced tracking settings option is enabled in the tag settings, the goal is created when contact information is first entered on the site. |
For recently created tags, tags without goals, and tags that are rarely used, the automatic goals creation option is enabled by default.
If there is a JavaScript event goal on the tag, automatic goals are not created. For Yandex.Metrica to create goals, enable the Automatic goals option in the tag settings.
Goals begin to be displayed when Yandex.Metrica registers at least one of the above events on the site: on the Goals page with a name such as “Auto-goal: Open messenger”.
To view goal statistics, use the Conversions report and add the goal to other Yandex.Metrica reports.
You can manage automatic goals:
- 1. Edit
-
For automatic goals, you can edit the name, income, and enable or disable the Retargeting option. You can't edit the other fields.
- 2. Delete
-
To delete a goal, click
. You can't restore a goal after you delete it, but you can recreate it manually.
Restrictions
- Automatic goals are not counted in the total number of tag goals.
- This type of goal can't be used in Multi-step goals.
- 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.
