Automatic goals
Yandex Metrica collects data about various activities on a website. It can create goals automatically based on certain actions:
| 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 number | All phone numbers. Yandex Metrica recognizes phone numbers by the presence of tel in links. | ||||||||
| Button click (including Auto-goal: Request and others) | 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. For websites added to Yandex Business, you can create this goal for different buttons (for example, Auto-goal: Request). We don't recommend deleting these goals, because they help improve the quality and effectiveness of your ads. | ||||||||
| Opening a messenger | Clicks 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. To ensure that your forms work correctly, set up data validation. | ||||||||
| 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 | Clicks 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. | ||||||||
| Ecommerce: Add to cart | Adding an item to the cart. The goal is triggered by the add E-commerce event. | ||||||||
| Ecommerce: purchase | Purchase on the site. The goal is triggered by the purchase E-commerce event. | ||||||||
| Entering contact information | Entering contact information in form fields on site pages. Starting December 2023, the goal is counted whenever the user submits their contact data. If the Use advanced tracking settings option is enabled in the tag settings, the goal is created when contact data is first entered on the site, and this data is transmitted to Yandex Metrica in hashed form. If this option is disabled, Yandex Metrica records the entered data but does not process it. | ||||||||
Logging in with Yandex ID (Auto-goal: User logged in with Yandex ID) | The user signed in with their Yandex ID account. There are two ways to count the auto-goal:
In other cases, the auto-goal won't be counted. |
| 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 number | All phone numbers. Yandex Metrica recognizes phone numbers by the presence of tel in links. | ||||||||
| Button click (including Auto-goal: Request and others) | 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. For websites added to Yandex Business, you can create this goal for different buttons (for example, Auto-goal: Request). We don't recommend deleting these goals, because they help improve the quality and effectiveness of your ads. | ||||||||
| Opening a messenger | Clicks 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. To ensure that your forms work correctly, set up data validation. | ||||||||
| 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 | Clicks 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. | ||||||||
| Ecommerce: Add to cart | Adding an item to the cart. The goal is triggered by the add E-commerce event. | ||||||||
| Ecommerce: purchase | Purchase on the site. The goal is triggered by the purchase E-commerce event. | ||||||||
| Entering contact information | Entering contact information in form fields on site pages. Starting December 2023, the goal is counted whenever the user submits their contact data. If the Use advanced tracking settings option is enabled in the tag settings, the goal is created when contact data is first entered on the site, and this data is transmitted to Yandex Metrica in hashed form. If this option is disabled, Yandex Metrica records the entered data but does not process it. | ||||||||
Logging in with Yandex ID (Auto-goal: User logged in with Yandex ID) | The user signed in with their Yandex ID account. There are two ways to count the auto-goal:
In other cases, the auto-goal won't be counted. |
You can also use the list of recommended goals for various industries and support sending events with the specified identifiers on the website. In this case, goals for tracking the sent events will be created automatically. On top of that, if you use Google Analytics and Facebook Pixel on your website, Yandex Metrica can recognize the markup of the recommended goals of these systems and automatically create goals for events.
Yandex Metrica suggests recommended goals based on your business area:
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Enter contact information | A user provided their contact information |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Request form opened | A user opened a request form |
| Submit an application form | A user filled out and submitted a request form |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Adding to favorites | A user added a service to favorites |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Enter contact information | A user provided their contact information |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Request form opened | A user opened a request form |
| Submit an application form | A user filled out and submitted a request form |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Adding to favorites | A user added a service to favorites |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Meeting confirmation | A user confirmed a meeting |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Meeting confirmation | A user confirmed a meeting |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Adding to favorites | A user added a product to favorites |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Add to basket | A user added a product to the basket |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Adding to favorites | A user added a product to favorites |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Add to basket | A user added a product to the basket |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Enter contact information | A user submitted their contact information |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Course started | A user started a course |
| Creating CV | A user created a resume |
| CV sent | A user sent a resume |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Enter contact information | A user submitted their contact information |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Course started | A user started a course |
| Creating CV | A user created a resume |
| CV sent | A user sent a resume |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Viewing seller/performer contacts | Viewing the contact information of a seller or contractor |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Ad placement confirmed | A user confirmed the placement of an ad |
| Ad response | A user responded to an ad |
| Contacting seller/performer | A user contacted a seller or a contractor |
| Successful contact | Successful contact |
| Meeting confirmation | Meeting confirmation |
| Performer completed order | A contractor provided a service |
| Adding to favorites | Adding to favorites |
| Goal name in Yandex Metrica | Event |
|---|---|
| Registration on the site | A user registered on the website |
| Contact details confirmed | A user confirmed their contact information |
| Login to site | A user logged in to the website |
| Subscription to mailing list | A user subscribed to the newsletter |
| Chat opened | A user opened the chat |
| Chat message sent | A user sent a message in the chat |
| Viewing seller/performer contacts | Viewing the contact information of a seller or contractor |
| Request form opened | A user opened a request form |
| Submit an application form | A user submitted a request form |
| Start to check out | A user started placing an order |
| Select a payment method | A user selected a payment method |
| Successful order | Payment completed |
| Ad placement confirmed | A user confirmed the placement of an ad |
| Ad response | A user responded to an ad |
| Contacting seller/performer | A user contacted a seller or a contractor |
| Successful contact | Successful contact |
| Meeting confirmation | Meeting confirmation |
| Performer completed order | A contractor provided a service |
| Adding to favorites | Adding to favorites |
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.
How to enable and manage automatic goals
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 at least one JavaScript event goal on the tag, automatic goals are not created by default.
For Yandex Metrica to create goals, enable the Automatic goals option in the tag settings.
You can manage goals:
— edit-
For automatic goals, you can edit the name, income, and enable or disable the Retargeting option. You can't edit the other fields.
To learn how to edit the “Click on phone number” auto-goal, see the Track clicks on phone numbers page.
— delete-
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.
- No automatic goal will be created if the tag already has a goal with exactly the same condition.
- 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.
