Why are goals set in Yandex Metrica. Guide to setting goals in Metrica: let's figure it out together. Accounting and tracking conversions using Google Tag Manager

Goals in Yandex Metrica help to analyze great amount information coming to the site. Often they are set precisely in order to find out the exact number of people who ordered a product or service from you. In rare cases, they are indispensable in finding the reasons why users leave the resource. For clarity, we can give a simple example of the benefits of using goals. Let's say you have a store on the Internet, which is visited by more than 1000 people a day. Even in the worst case You will receive up to 30 applications per day. It will be extremely difficult to track the exact number of applications in order to process them. It will be even more difficult to find out the most popular forms from which these applications were left. And properly set goals will help you understand all these nuances and make decisions that at least do no harm.

Main types of goals Metrics and rules for their selection

Currently, Yandex Metrica offers to configure up to 4 types of goals:

  1. Number of views. Allows you to analyze the quantity unique visitors, which made an integer number of views specified during setup. Allows you to analyze the nature of traffic after changes on the site and work on reducing bounces.
  2. Page visits. It makes it possible to track exactly the number of visitors who opened a particular page on the site or their sequence. As a setting for this goal, it is supposed to use several options for conditions (up to 10):
    • URL matches. You must specify the exact address of the page you need.
    • URL contains. If the target needs to be configured for pages with a common key in the address. For example, the use of the category name or the word from the address of the product basket page.
    • URL starts with. If the object of analysis is a whole subsection of the site, it is necessary to track all addresses starting with the specified key.
    • URL regular expression. Here you set your own sequence, according to an arbitrary type. Be very careful here.
  3. JavaScript event. If the object under which the target is configured is a JS code. Often these are various forms and buttons from sites like: “Submit”. To fix the execution, an identifier is used (the ReachGoal method). For Ecommerce, goal completion is signaled using the goal_id.
  4. Composite target. Allows you to track those users who have made a certain number of steps (more than 5) at the specified page addresses. In this case, the system also takes into account those sequences that were performed out of order.

Depending on the type of site and the tasks assigned to it, an infinite number of variations of using this tool can be used. The most important thing in this case is not to get confused with the data that you set up the statistics for.

Correct setting of goals in the metric

To obtain accurate data on goals, it is also necessary to know the correctness of their settings. It should be noted that in most cases all errors occur due to inattention, in extremely rare moments the site itself is responsible for issuing biased data.

Goal setting: number of views in Yandex Metrica

To configure, follow these steps:

  1. Log in to the Ya.Metrika interface. To avoid errors, it is best to do this from the login to which the analytics is registered.
  2. Select the setting item. it is on the left.
  3. Then we move on to Goals.
  4. Click add and select our goal.
  5. Specify an integer number of pages and click add.
  6. After that, within 30 minutes we look at the metric for the correctness of the settings and the incoming data.
  • when work is being done on the site to improve behavioral factors. In this case, it is convenient to view the share of views per visitor before work and after it is completed.
  • in the case of analyzing the visual accessibility of other articles. If you have blocks with related posts, the convenience of their location should be analyzed.
  • whether the materials on the site meet the needs of the user. If you don't have useful information, then the reader is likely to close the page. If the material is interesting, there is a chance of viewing the rest of the material.

Key points for setting up a given Metrica goal:

  • Specify an integer number of pages.
  • The correctness of receiving data and their reliability can be checked by creating a target with 1 in the settings.
  • When working to reduce site bounces, try setting up multiple goals with different settings. So the data will reflect the whole picture as fully as possible.

Goal setting: visiting pages in Yandex Metrica


Setting the target is done as follows:

  1. Login to Yandex.Metrica using your login.
  2. Choose settings.
  3. Go to the goals tab and select ours.
  4. Specify the name. Get something you won't forget later. It’s just that when there are already more than 2-3 dozen goals on the site, it will be possible to get confused which one is responsible for what.
  5. Choose the condition you need. Their explanations are given above.
  6. Enter the value according to the conditions and click add.

Why do I need to set up a goal for visiting pages?

  1. To identify a chain of events before the main action. Just recently, we analyzed an online store to reduce bounces. During the analysis of the goal, it was found that the bulk of people leave after visiting a certain section of the site. As it turned out, this section was crooked and gave out hieroglyphs instead of prices.
  2. To complete the picture of user behavior. If you need to make sure that a new element, block, or even the entire design is correct, it is important to trace the chain of events, pages that lead to the final action.
  3. If necessary, analytics of entire sections of the site. especially relevant for online stores. If there are problems in a certain section of the site.

Goal setting: Java Script event in Yandex Metrica


Popular ways to use this goal:

  1. Implementation of achieving the goal of adding a product to the cart. This is especially true for stores with a large assortment.
  2. Form Analytics feedback and filling. Especially relevant for finding out the most popular elements of the site. In this case, you can analyze and leave only those forms that are most popular.
  3. Comprehensive analytics of goals by buttons on the site. Almost all buttons work through JS. so setting up a target will help track any click.
  4. Opening/closing forms under Hide. If you have a forum or a portal with the provision of some information only for the elite. You can make the goal so that it will analyze the popularity of the message hidden under hide.
  5. Setting up for virtual fitting rooms. If you set this goal to click the selection button in virtual fitting rooms, you can identify the most popular product model and make various promotions for it, thereby attracting more customers.

How to set target JS event in Yandex.Metrica?

  1. Select the statistics counter and go to the settings.
  2. Open the target tab and select the JS event.
  3. Indicates a target name that you will not forget later.
  4. Specify the target ID, any arbitrary name in English. Take for example - kaktus.
  5. Click add.

The goal is created, but that's not all. Yandex Metrica does not yet know which form will be considered as the goal. She needs to indicate this by digging into the site code. Don't worry, there's quite a bit.
To do this, we first need to decide where we will set up this goal.
If the result of the goal is clicking a button or link, the code will be as follows:

Onclick="yaCounterXXXXXX.reachGoal("kaktus"); return true;"

If you need to set a goal for a form, then the code will be like this:

Onsubmit="yaCounterXXXXXX.reachGoal("kaktus", function () ( alert("Data submitted successfully");

If it is necessary to make a goal with the input of user parameters, then the code will already change:

Onclick="yaCounterXXXXXX.reachGoal("kaktus", goalParams, goalCallback); return true;"

In this case, instead of XXXXXX, we indicate the number of the counter to which data on the achievement of the goal will be received. As the identifier-kaktus, you must choose any value you like. You can even leave it.

Step-by-step Setting up a target JS event in Yandex Metrica

Let's show on real example how we set up this goal, because it is the most complex and raises the maximum number of questions.

  1. Select the element of the site that we will configure. We took the submit button on the template landing page.
  2. We are watching source in the browser (select the button-right-click-explore element).
  3. We leave the browser open at the place of viewing the code of the button that we will configure.
  4. We copy a piece of code with an identifier and a counter number and paste it at the beginning of the code, right after INPUT.
  5. We save the result and check.

Uploading the code home page from the server
Insert the target code at the beginning of INPUT
We save the result and check the code for the appearance of the configured target.

Setting up a compound goal in Yandex Metrica


To set up this target, do the following:

  1. Go to the settings of the Metrica counter.
  2. Specify the name of the goal and the name of the steps.
  3. Select transition conditions and value.
  4. Click add.

A caveat should be made here:

  1. A multi-target allows you to customize steps with both page URLs and a JS ID.
  2. You must specify at least 5 steps.

For what tasks is a compound goal configured in Yandex.Metrica?

This type of goal can be very effective in several cases:

  • When you should track those pages that cause the user to refuse further actions on the site. For example, in the case of filling out an order form for goods.
  • In case of need in the analysis of forms of surveys or assessments. This option is more applicable to marketers and allows you to evaluate failures at different steps in filling out a questionnaire or test.
  • When improving website conversion rates, it is important to know what moments in the design, download, etc. are especially annoying target audience and forced to close the page.

How to check if the goals are set correctly?

There are two effective ways to do this:

  • Direct fulfillment of the goal. In this case, you must wait 10-20 minutes after execution. The metric does not immediately produce results.
  • Yandex suggests checking in a different way. To do this, you need to add /?_ym_debug=1 to the main page of the site. In this case, you will see data indicating the achievement of goals.

Important points about setting goals:

  1. Yandex has a limit of 200 goals for one counter.
  2. For the user to complete the same goal, at least 1 second must elapse.
  3. When you delete a target, all data in the reports for that target is erased.
Setting up Metrics Goals on Contact Form 7 in WordPress


As a bonus for those who have read to the end, we will talk about how to set metric goals for Contact form 7 plugin forms. WordPress fans probably know it and we won’t talk about the benefits of this plugin. So. Let's say we need to set up a goal that would be executed on clicking the submit button in the form. To do this, we do the following:

  1. Go to the settings of the counter Metrica
  2. Open targets and select JS event
  3. Specify a name and select an arbitrary identifier
  4. Click add and go to the settings of the form on which our goal should work
  5. To do this, open the plugin settings and select the Forms column
  6. Click edit on the selected form and go to advanced settings
  7. We insert the following code there: on_sent_ok: "yaCounterXXXXXX.reachGoal("kaktus ");"

Here, instead of XXXXXX, the number of your Metrica counter is indicated, and kaktus is the identifier we have chosen.

We have released a new book, "Social Media Content Marketing: How to get into the head of subscribers and make them fall in love with your brand."

What are the goals in and their tremendous benefits have already been outlined in this , so we will not focus on this, but let's talk about how to set up .

Immediately after you have decided on the goals of your site and before launching an advertising campaign, you need to set up the appropriate counters in Yandex.Metrica.

Goal options in Yandex Metrica

In general, there are not very many options for goals in Metrica, but their use can be very flexible. There are 4 main ways to set goals:

  1. Quantity . This refers to the browsing depth, that is, the number of pages visited by the user within one session.
  2. Page visits. Here we can specify the goal of the user entering the pages of interest to us.
  3. JavaScript event. Thanks to small pieces of JS code, we will be able to customize the user's interaction with the functionality of the site.
  4. Composite goal. It is a visitor's chain of actions, which can include all previous goals.

Now let's take a look at how to set up goals in Yandex.Metrica and how to use them.

At the time of this writing, there is a limit on the number of targets for one counter - 200 pieces

Goal in Metrica: number of views

The first, and the simplest. There are few use cases, but the output can be very useful:

  • Is the site easy to navigate and how clear is the structure.
  • Have we implemented the linking correctly and is it convenient to use it.
  • Does the site provide high-quality content, does a person want to delve into your structure and learn more about the service / product / information provided.

Scope of use:

  1. Great for information resources, where a large number of information and it is important to understand whether visitors go to related articles.
  2. For educational portals, where all courses are built from consecutive articles and you need to evaluate the quality of the material and ease of navigation between lessons.
  3. Commercial sites that maintain their blog to attract thematic traffic.

How to set up a goal in Yandex.Metrica: number of views

We go to Yandex Metrica of our site, click:

  1. Settings
  2. Goals
  3. Add target
  4. Come up with a meaningful name
  5. In the view field, put the number of pages of interest
  6. Click "Add"

If everything is in order, we will see our first target in the list. Don't forget to click the yellow "Save" button. In a few minutes everything will work!

Goals in Metrica: page visits

One of the most important goals (as it is often part of a compound goal, but more on that later). Here we can specify the URL of the page, the transitions to which will be the achievement of the goal. Most often, we are talking about the order / delivery / download page and any other transaction. The conclusion suggests itself:

  • Whether the link to the desired page is visible/attractive.
  • Linking correctness.
  • Whether users reach the conversion page.

Scope of use:

  1. Internet shops. Thanks to this goal, they can know for sure whether users go to the cart. Are those sections of the product viewed and where they go more often, are they interested in delivery, etc.
  2. Service Sites. Depending on the nature of the services, you can evaluate whether users go to conversion pages, whether they are looking for your address when they go to the contact page. Which of your services on the site is more in demand.
  3. For both service sites and online stores, you can set the goal to visit the “Thank you for your purchase / order / contact” page, which is shown only after any transaction.

Setting a goal in Yandex.Metrica: visiting pages

The initial steps will be the same everywhere, but I will duplicate them just in case, you never know.
Go to the Metrics of your site and:

  1. Settings
  2. Goals
  3. Add target
  4. We come up with a clear name, for example: “View Contacts Page”
  5. We select the condition based on the need. (more on this below)
  6. In the value column, we enter the URL or part of the URL, also from the needs.
  7. Click "Add Target"

About conditions:

  • url: contains - An analogue of a fuzzy match. They are used if you are interested in visiting a group of pages, for example, a filter in the catalog of an online store. In this case, the part common to all URLs is specified.
  • url: matches - Similar to an exact match. Used to track a specific page. You need to insert the entire address into the hole, along with the http / https protocol.
  • url: starts with - Used to track a group of pages with the same URL start. For example, a subsection of goods of an online store. Insert the address of the previous directory with a slash into the hole, for example, site.ru/podrazdel/
  • url: - Used to set very "flexible" parameters. Unfortunately, there are so many of them that it is enough for a separate article.

Goal in Metrica: JavaScript event

A super-thing that will help track the interaction of the visitor with any elements. We will draw a conclusion after the scope of use.

Where to apply:

From life:

Once we increased the conversion rate for an online store in this way, having discovered that the green “order” button did not attract the attention of users at all. Simply by changing the color of the button to yellow (it went well with the overall design of the site and was brighter than other elements), we increased the number of orders by 13% from the current one. And all thanks to the goals in Metrica.

How to set up a goal in Yandex.Metrica: JavaScript event

Setting this goal raises the most questions. For it, in addition to Metrica, you will need access to editing html code but the site. In general, ideally, you need to know at least a little html for comfortable work with this tool. However, I will try to be as detailed as possible:

  1. Settings
  2. Goals
  3. Add target
  4. Selecting a JavaScript event
  5. We come up with an identifier, for example: "buttonZakazat".

    Please note that you cannot specify identifiers that match the content of the URL, either partially or completely. And you do not need to enter all the characters that are on the keyboard into the identifier, be content with Latin letters, numbers and a lower space.

  6. Click OK

The target has been created. The second step is to add an identifier to the html code of the page. To do this, you need to determine what to add to the button code, find out how the button is written in the code, find it and convert it.

First, let's look at which code is used where:

Code for buttons and links:

Onclick="yaCounter12345678.reachGoal("Nazvanie_Identifikatora"); return true;"

Code for various forms where the user submits data to us:

Onsubmit="yaCounter12345678.reachGoal ("Nazvanie_Identifikatora", function () (alert ("Data sent"))); return true;"

Onclick="yaCounter12345678.reachGoal("Nazvanie_Identifikatora", goalParams, goalCallback); return true;"


Instead of numbers after yaCounter - specify the code of the Metrica counter
Instead of'Name_Identifier' - specify the name of our identifier, which was created by the step above.

  1. Choose a piece of code that fits
  2. We go to our site and look for an experimental button
  3. Click on her right click mouse "view code"
  4. In the console that opens, copy the highlighted line
  5. Go to ftp in the root folder of the site and open the file containing the . For example index. html

    If you're going into code without much confidence, it's best to save the index. html in its original form, somewhere in a secluded place. If you accidentally break something, you can fix it painlessly by returning it. original file to ftp.

  1. With the help of a single keystroke ctrl + f, a search opens, where we paste the copied line from the page code and click search
  2. Having found the line, add to it the code fragment selected in step 1 before the closing tag
  3. in the fragment, replace the numbers after yaCounter with our own, and replace Nazvanie_Identifikatora with our own.
  4. Save file to ftp

Button code example:

An example of the callback form code:

Since we were in the code with inexperienced hands, we check the site for operability and after a couple of minutes you can try to click on the marked button and see in Yandex.Metrica whether the statistics are considered.

Make sure the counter counts your own visits. To do this, go to "Settings" - "Filters" and see that there is no checkmark next to "Do not include my visits."

Setting Goals in Metrica: Composite Goal

Compound goals are useful when tracking is important, building a chain of landing pages that a user should visit. Later, we will be able to identify the stage at which users leave the site without buying / ordering anything and work through them. Also, if you blog to attract thematic traffic (and you should already), you can track the conversion of the transition from the information pages to the service / product pages and from there to the checkout.

  • If we have built some kind of chain of pages on the site that the client must visit in order to convert into a deal.
  • Sales funnel for online stores. The most popular and flexible, since funnels can be very different and sophisticated.

How to set up a compound goal in Yandex.Metrica

There is nothing difficult if you have learned how to set up all the previous goals.

Well, straight to the point:

  1. Settings
  2. Goals
  3. Add target
  4. We come up with a name, for example: “Order button”
  5. Choose a compound goal
  6. Step name
  7. Select the desired condition (one of the previous goals)
  8. Specify the required value
  9. Adding a Target

In the screenshot, a composite goal from "one" step, so as not to confuse anyone. In order to add the next step, you need to click on the appropriate button and repeat the steps from step 6.

There are a couple of nuances:

  • There can be any number of actions between steps (but the steps must be performed sequentially). Therefore, if a composite goal is visiting two pages and clicking a button, then the user can be busy with anything between these actions, but after going through all the steps, the goal will be counted.
  • If the user takes the first action from a multi-goal, and then leaves the computer for more than 30 minutes (session time), the goal will be considered failed
  • A compound goal can contain a maximum of 5 steps

Checking Metrics Goals

Unfortunately, I did not find a better way to check goals in Yandex.Metrica than manually. After 10-15 minutes after setting the goals, go through them yourself and see if it works. Don't forget to uncheck "Ignore my visits" in the filter section!

If you have read to the end

For those who mastered this giant layer of text and pictures, I have prepared a small surprise. I asked our Metrica gurus what “unusual” goals that you won’t find on the Internet, but which they used in their practice, and that these goals were really useful. Perhaps some of them are just what you need?

Setting up not quite standard goals will require us to be able to create and connect to the site. Let's briefly analyze how to do this exclusively for our example.

How to create a script: Create on desktop Text Document, come up with a name for it and change the extension to get a file like imya_scripta.js - this file will contain our script. Now paste the required code into it and copy it to ftp to the folder with scripts. (where files with the same .js extension are located)

How to connect a script: In index. html between tags … write a design.
For example, all my scripts are in the scripts/targets folder.

We write: and, of course, we replace the numbers with our counter and write the goal identifier with the reachGoal value.

  • Transferring data from the site search (when the words entered by the user into the search box on the site are transferred to Yandex.Metrica) var myParams = ( x: query /*search query value*/ ) var yaCounter12345678 = new Ya.Metrika((id:12345678, params: myParams));
  • Script to count bounces for the Landing page (since there is only one page, all hits can be "bounces"). Already according to the usual scheme, we create a js file with the code below:
  • The visitor moved the mouse over a certain area. It helps when you need to track the degree of attractiveness of any element on the site. The data is fuzzy, but still gives food for thought. So we experimented with the colors of an element containing small text and tracked which color background attracts more people. document.body.onmouseover = handler; function handler(event) ( if (event.type == "mouseover") if (event.target.className == "element") (reacGoal456123("identifikator"); return true; ) )

    Then we connect the code as usual. Now, we need to link the code to the element of interest. We have already discussed how to find the site element code above. When found, you need to add to the opening tag

    , which comes before the element code, class. I highlighted them in red.


    Tracked item ID


    Now, every time the user moves the mouse over the selected element of the site, the goal will be considered achieved.

  • The visitor copied some information from your site (for example, if your text is stolen from the main one, you can quickly check its uniqueness for theft)

    Script:
  • ;

    We connect to html.

    Now in the index. html select the first one

    after and assign to it onCopy="funCopy ();" id="id1"

    Just in case, one more time. Everywhere in the reachGoal (‘something’) construction, in brackets and quotation marks, the event modifier that we create in Yandex.Metrica

    If there is JivoSite or similar online chats, you can track the visitor's requests, whether they answered him or not, and so on. To do this, go to the metrics in creating goals, create (we already know how to do) a JavaScript event and use the one that suits your needs as an identifier:

    1. Jivo_Chat_requested - Chat requested by the client.
    2. Jivo_Chat_established - A client-agent dialogue has been established. Items 1 and 2 are usually two steps of a compound goal. It turns out a chain: the client writes to the online chat -> the consultant answers the client.
    3. Jivo_Proactive_invitation_accepted - An invitation was displayed to the client.
    4. Jivo_Proactive_invitation_rejected - Client closedcross stitch invitation.
    5. Jivo_Proactive_invitation_shown - Client acceptedinvitation by writing a message in response.
    6. Jivo_Offline_form_shown - A form is displayed to the client to send a message to e-mail when there are no operators online
    7. Jivo_Offline_message_sent - Client sent offline message

    Hope it was helpful!

    If you have had experience setting extraordinary goals in Metrica, please tell us about them in the comments.

    To about n e c

    in internet marketing, the purpose or target action is understood as the visitor's actions in which the site owner is interested, for example:

    • visiting specific pages;
    • clicking on the subscribe button;
    • clicking on the button to add goods to the basket;
    • following certain links;
    • registration and payment of the order.

    Wherein:

    • site visits by users during which goals were achieved are called targeted visits;
    • during one targeted visit, several achievements of the same or different goals may occur;
    • a the ratio of the number of targeted visits to the total number of visits is called!

    Goals are usually divided into simple and compound.

    Simple Goals- are set by one condition, for example: the number of page views, a visit to a certain page, a given JavaScript event.

    Composite Goals- are set by a certain sequence of steps (conditions) performed by the user on the way to the target action, and each step is described using a simple goal.

    Analysis of statistics on the steps of compound goals helps to understand at which stage of the movement towards the goal site visitors experience difficulties.

    Conversion is the ratio of two indicators to each other; for example, the number of those who went to , to the number of those who were on the main page of the site at all. If 1 person out of 100 page visitors went to the directory, the conversion would be 1%, if 10 people went, the conversion would be 10%, and so on.

    Conversion rates are important data in determining the effectiveness of a website. Does our site sell? We can get the answer to this question by analyzing the indicators of different conversions.

    What goals or conversions to track

    It depends on the optimization tools and capture forms (they are also data collection forms). It is most convenient to create a plan for tracked conversions in the following table:

    To begin with, you can name the fields exactly as shown in the example - as we work, we will figure out what it is and what it is for. After that, you can optimize the plate for your needs. Now, together, step by step, we will identify the conversions we need.

    Step 1. Identify conversion elements

    First, for convenience, let's make a list of all our conversion elements - that is, those that: order a call back, open a catalog, put a product in a basket, go to a social network, and even just watch a video.

    Here is a rough list of elements that are likely to be on your site and should be included in the list.

    • Buttons:
      • with a call to action;
      • adding goods to the cart;
      • placing an order;
      • newsletter subscriptions;
      • registration;
      • transition to social networks;
      • links to other pages.
    • Pictures that serve as links to pages/sections.
    • Forms:
      • placing an order in the shopping cart;
      • registration;
      • subscriptions;
      • feedback;
      • registration of applications;
      • inquiries/requests/questions, etc.
    • Video viewable.

    Attention! It is worth thinking carefully about which elements are worth working out and which are not: not all of them will directly affect sales; Tracking a thousand unnecessary conversions does not make sense.

    Now the necessary elements need to be correctly entered into the table: how to do this, let's look at the example of a button on the main page of the site. There she is:

    The button we are interested in is called “More” and it leads to the training catalog page. Recording about it is entered into the plan.

    Just a few words about the name. There can be several tens or even hundreds of conversions, but by the name you should immediately clearly understand what it is about. You should not use names like: "Conversion 1" or names in the form of incomprehensible abbreviations. It is convenient to use the following format:

    "Site page _ conversion type _ page section".

    For our button, a good, correct entry would look like this:

    Recording the conversion in the planning table: it is immediately clear that we are talking about the main CTA on the first screen of the main page of the site

    We carry out a similar analysis of each page and find all the elements by which we will track conversions.

    Step 2. Identify conversion pages

    Now we track the path that the visitor takes from the moment of the first hit (the entry page) to the final moment of purchase. This path is called the visitor's conversion trajectory.

    Why do we need it? After the analysis, we will get a list of not only buttons, but also pages where the conversion occurs; their visits are monitored. Here are some examples of typical trajectories with indication of such pages.

    • Main page - Catalog - Product card - Filling out the order form
    • Main page - Catalog - Product card - Filling out the order form - Payment page - Thank you page (about it below)
    • Main page - Catalog - Service page (landing) - Call from the site for ordering
    • Main page – Service page (landing page) – Filling in the order form.
    • Blog article – Service/product page – Filling out the order form

    If we find a lot of such pages, the list should be shortened, leaving only the so-called "nodal" pages: those visited by users following different trajectories. For example, in the first two examples there is a node page "Filling out the order form" - we will leave it.

    Looking ahead a little (so as not to get the feeling that we forgot to say something): the trajectories of visitors are tracked using the settings of the Goals tool in Yandex.Metrica and Google Analytics- we will talk about this in detail below.

    The pages we need (all or only the nodal ones) are entered into the plate in the same way as the buttons. As a result of the analysis, we have a planning table in our hands, which contains full list elements and pages, the conversion of which we will track.

    The conversion of elements or pages can be tracked using special goal settings in " Yandex.Metrica» (no more than 200 targets per site).

    The service uses 4 formats - or condition types - of goals.

    • The number of views. A format for tracking users who viewed two or more pages in one session. This feature is often referred to as "View Depth".
    • Page visits. A goal that measures the number of visits to specific pages on a site.
    • JavaScript event. This type embeds an identifier in the site code that tracks the number of actions performed by visitors: clicking on a button, filling out registration forms, etc.
    • Composite goal. Tracks how visitors complete up to 5 specific steps, such as placing pages, clicking a button, and going to new page etc.

    4 main conditions for setting goals in Yandex.Metrica

    The table below shows the types of conversions and goal formats that you need to use.

    Note: if two or three options are indicated, it is not necessary to use all - choose one suitable and use it.

    It is worth dwelling separately on such a method as the "Page of Gratitude". Add a special thank you page after each targeted customer action. Then the visitor will get to it every time they reach the goal, and we can easily measure the conversion by tracking how many such visitors were in the end.

    Setting goals in Yandex.Metrica step by step

    1. Open the "Counters" page of "Yandex.Metrics". Select the one you want and click on the gear icon:

    2. On the page that opens, select the "Goals" tab:

    3. Click "Add Target" and select the "Page Visits" tab.

    4. From the drop-down list, select "url: contains" and write the address of the page, the transition to which is tracked. In our example: how many visitors from the main page will go to the page with the catalog of services.

    5. Add a name from the planning table and click the "Add goal" button:

    Setting up conversions (goals) via JavaScript events

    Now let's set up the conversion of used buttons, registration forms and subscriptions.

    Attention! Setting up this type of goal requires making changes to the site code. If you do not have the necessary level of knowledge, it is better to leave this task to specialists.

    The setup involves two steps:

    1. Target setting.

    2. Making changes to the site code.

    First, let's set up a goal in Yandex.Metrica:

    1. We enter the name of the goal from the planning table:

    2. Select the type of conversion - JavaScript event.

    3. Specify the name of the target identifier.

    Attention! The identifier must be specified only in Latin letters and numbers without spaces. It is impossible for the name of the identifier to coincide with the url-address of the site, even partially.

    4. Click "Add target".

    Now we make changes to the site code. You need to find the button or form code and add the goal data.

    onclick="yaCounterХХХХХХ.reachGoal("Identifikator"); return true;"

    where instead of XXXXX we add the Yandex.Metrics counter code, which we take on the counter settings page:

    Instead of Identifikator, we add the name of the target identifier, which we set in the step above.

    In our example, the final code will look like this:

    onclick="yaCounter40703159.reachGoal("btnZakaz1"); return true;

    2. Open the code of the site page on which the button is installed.

    3. Find the code for this button on your site.

    4. Add a piece of code - as shown in the figure and save. Target set.

    Setting up conversion through the "trajectory of the visitor"

    1. Enter the name of the goal.

    2. Select the type - "Composite goal".

    3. Enter the name of the step.

    4. Enter the condition of the first step - the address of the page from which we begin to track the client's path. Then click "Add Step".

    5. Similarly, the data for the next step is entered (attention: there can be no more than five). The cycle is repeated as many times as the number of pages the client has to go through.

    6. Click "Add target".

    You can use not only the format of visiting a specific page, but also individual events. For example: "click on a button". In this case, at the step selection stage, we specify the condition "Event: Target ID". The setting is carried out in the same way as the button conversion setting.

    Additional options for analyzing registration/contact/order forms

    "Yandex.Metrica" ​​allows you to analyze the completion of registration forms through a tool such as "Form Analytics":

    To measure the conversion of a specific page, do the following:

    1. Open Form Analytics.

    2. Select the "Interaction with the site" tab, select the page address in the drop-down window and set the required dates:

    3. We receive data in the form for the selected period:

    Google Analytics Conversion Tracking

    Let's take a look at setting up conversion tracking through Google Analytics. For this, the “Goals” tool is used (no more than 20 goals per view - that is, per level that gives access to reports).

    Google Analytics uses the following 4 goal formats:

    1. landing page. Allows you to track visits to specific pages or visitor trajectory.
    2. duration. Allows you to track the number of visitors who stayed on the site for a certain amount of time.
    3. Pages/screens per session. This format tracks people who visit a certain number of pages in a single session.
    4. Event. The format tracks the completion of targeted actions, such as clicking on buttons or registering in forms.

    The table below shows the types of conversions and goal formats for them:

    List of conversions and their corresponding condition types in Google Analytics

    Customizing the Landing Page Format

    1. We go into our office. Select the "Administrator" tab, select the site in the drop-down list and click "Goals":

    2. In the tab that opens, click on the "+ Goal" button:

    3. At the very bottom of the page, select "Own":

    4. Enter the name of the goal, select the type - "Landing page" and click "Continue":

    5. We prescribe the address of the page, the transition to which is tracked. In our example, we need a transition to a page with a catalog of services, which means that we prescribe the address of the latter. And click "Save":

    6. Check the result:

    Setting the goal of the "Events" format

    As in Metrica, here we do two things.

    1. Set up goals in Google service.

    2. We make changes to the site code.

    Set up the target:

    1. We go into the service, click on "+ Target" and select "Own" in the window that opens.

    2. We drive in the name, select the type - "Event" and click "Continue":

    3. In the window that opens, we must fill in at least two sections: "Category" and "Action".

    You can fill in the names only in Latin and numbers. It is desirable that the names reflect the essence. In our case, this is the “Orders” category (we write “zakaz”) and the “Click” action (we write “click”), since we are talking about a mouse click on the button to place an order.

    Now you need to add the necessary changes to the site code.

    1. To track the conversion of the button, add the following code:

    ga("send", "event", , );

    ga("send", "event", unchangeable part

    - name of category. Instead of this phrase, we enter the word that was specified when setting up the goal: “zakaz”.

    - the name of the action. The word that was specified when setting the target is entered here: “click”.

    The final code for our example:

    ga("send", "event","zakaz", "click");

    Setting up a visitor path conversion

    1. Click "Add Target" and select "Own" at the very bottom of the page.

    2. Specify the name of the goal and select the type "Landing page". Click "Continue":

    In the "Transfer" tab, we indicate the address of the last page that the client gets to in the chain. Next, set the "Sequence" button to "ON":

    4. Now we write down sequentially all the stages that the client must go through from the first to the penultimate page (the last one is already indicated). Set the Required button to YES. We save.

    Accounting and analysis of data on conversions

    Setting goals in Yandex and Google only gives you access to statistical data. But without the creation of an accounting system and regular analysis of the results, all this will be useless. Conversion analysis should be carried out in dynamics, that is, constantly comparing data for one period with data for another.

    Example. The fact that in March 2017 the callback conversion rate is 1.2% does not tell us anything about the effectiveness of the element. Is it a lot or a little? Unclear. But if we compare this indicator with the result of the previous month, when the conversion was 1.9%, then we can conclude that the conversion has worsened.

    To correctly interpret the results, you need to create and maintain a record of all conversion data. The easiest way is to use Excel spreadsheet to regularly record item conversion data.

    • For online stores, it is recommended to take into account the data on a daily basis.
    • For other sites, it is enough to analyze the data on a weekly/monthly basis.

    Then, based on this data, you can create a graph for a good visual presentation with a few mouse clicks.

    Viewing conversion results in Yandex.Metrica

    1. To view the results of tracked conversions, open the "Reports" tab, then "Standard Reports" and "Conversions".

    2. Choose the goal we need:

    3. On the page that opens, we see detailed information in graphical and tabular form. We can choose the reporting period we need.

    1. To view the results on the left tab, select "Conversions" - "Goals" - "Overview".

    2. In the window that opens, we select the reporting period and in the "Goals" drop-down menu - a specific type of conversion.

    Yandex.Metrica and Google Analytics are very different services, but together they solve almost any task, so you should not neglect any of them. Having done all the work of setting goals and tracking conversions consistently in both systems, you will track the effectiveness of each significant element of the site. It is imperative to start with planning to cut off dozens of unnecessary conversions that do not matter to the business.

    Accounting and tracking conversions using Google Tag Manager

    You can use the tool Google Tag Manager (GTM).

    In the last article, I talked about . Today it's time to figure out how to make sure that conversions go to Yandex Metrica. This can also be done quickly and easily. And you don't need to be a programmer.

    Therefore, right now (with the console and debug turned on), I am doing a test conversion - sending an application through the form on the site. And… what do we see!


    As you can see, the debug reports that a goal with id = send was successfully sent to Yandex.Metrica. And indeed, in Yandex.Metrica, I have an event configured with the following ID:

    As you can see, to check the work of goals in Metrica, you do not need to have knowledge of a programmer. Just follow three simple steps:

    • enable the code debugger in the browser;
    • enable the goal debugger in Yandex.Metrica (add a tail to the page url);
    • submit a test conversion.

    That's all for me guys. Like if this article was helpful and ask questions in the comments if something is not clear!

    Lesson Materials Activity

    What are goals in web analytics systems such as Yandex Metrica and Google Analytics and how to set them up?

    Let's look into this issue.

    If you do not have time or do not want to dive into all the features of setting up such a goal, you can entrust this work to me, I will do everything for you.

    In the Yandex Metrica system, goals can be found in the Settings - Goals menu.

    In Google Analytics, goals are at the presentation level, there is a menu item called Goals.

    What kind of tool is this "goal" and what is it for?

    When visitors go to your site, they begin to take a variety of actions. They can start moving from one page to another, start filling out any forms on the site, click on some elements (for example, buttons, slider, images, etc.) and can follow various links, etc. d.

    Depending on the purpose of your site, what you created it for, some actions that visitors take may be somehow more valuable to you than others. You can highlight them before the rest.

    Depending on what kind of site you have and what you created it for, these types of actions may differ and you yourself can determine which of these actions will be more valuable actions for you.

    For example, for an online store, such valuable actions can be:

    Buying a product

    Click on the button "Add to cart"

    Click on the buy button

    These actions for an online store directly affect its sales. For the main purpose for which this online store was created, but it was created to sell goods. Therefore, all actions that users take in terms of moving towards the purchase of a product will be targeted for this site.

    For a news site, the tasks may be somewhat different. For example, a news site may have the goal of reaching out as quickly as possible to as many people as possible. For this, it is important that people get involved in this site, that it is interesting for them and that they want to return there.

    Therefore, for a news site, such valuable actions can be the depth of browsing by visitors to the pages of the site, how deeply they browse the pages of the site and how much time they spend on it.

    Web analytics systems allow you to highlight these valuable actions of visitors on the site in separate group, which is called the target.

    The fact is that in analytics reports, by default, we see such analytics indicators as Visits, Visitors, Bounces, Viewing Depth, Time on the site, but we do not see any specific actions that the user takes on the page.

    In web analytics systems, by default, we cannot see clicks on some links, clicks on some areas on the page, filling out forms, etc.

    All these events, which are additionally performed by the user on the page, need to be configured separately in web analytics systems and this can be done using goals so that these events can be detected and seen.

    Goals is a tool that allows you to record the actions of your visitors that are important to you.

    If you set them up, then the web analytics system begins to "see" these actions.

    What will the customized goals on your site give you?

    1) You will understand about the sources that bring people to your site who buy from you or perform some other actions. You will know where visitors come from who are targeted for your site.

    By knowing the sources that work for you, you can invest more money and attention there and get more results.

    2) You will be able to build visual reports that show you not only data on how many people came to your site, but also data on how many people performed this or that target action that would be important to you. Goal achievement and conversion columns appear.

    3) You can build funnels for multi-stage processes.

    With the help of these funnels, you can see how many and at what stage of the multi-step process visitors are weeded out. You will see a weak link and can conclude that at some stage there may be something wrong and you need to pay more attention to it.

    4) By setting goals, you can filter only targeted visits in reports.

    5) It is possible for people who have completed the target action on the site to advertise in systems such as Yandex Direct, Google Adwords. With the help of goals, you know that a certain group of visitors are loyal to you and they are interested in your product or service, and you can advertise only to this interested segment of people, pay less money for advertising and get more results.

    Goals are a tool that shows where the money is.

    Adds clarity to the process of analyzing your website statistics

    I hope that I managed to convince you that goals are important for your site, especially if this site is about sales.

    If you want to learn more about the goals, how it's all set up and where, go to the following videos.

    With the choice of goals for the site, there can be a lot of features, controversial and rhetorical questions.

    Let's try together with you to learn how to determine the events on the site for which you should, and for which you should NOT set goals.

    2) Write for what events you will set goals on this site? Why did you choose these events? Why is it important?

    Write, we will understand, discuss and learn together.