Yandex.Metrica

Yandex.Metrica is a web analytics platform that lets you get an in-depth understanding of your audience’s behavior and use the insights to drive business growth.

Find the open source code for this destination in the GitHub repository.

Connection compatibility

Destination info
Status: Generally Available Supported sources: Web Refer to it as YANDEX_METRICA in the Integrations object.

Connection modes
Source	Cloud mode	Device mode	Hybrid mode
Web

Supported message types
Source	Identify	Page	Track	Screen	Group	Alias
Device mode
Web

Get started

Once you have confirmed that the source platform supports sending events to Yandex.Metrica, follow these steps:

1. From your RudderStack dashboard, add the source. Then, from the list of destinations, select Yandex.Metrica.
2. Assign a name to your destination and click Continue.

Connection settings

To successfully set up Yandex.Metrica as a destination, you need to configure the following settings:

• Tag ID: Enter your Yandex.Metrica tag ID.
• Enable Clickmap: Enable this setting to collect data for click mapping.
• Enable Tracklinks: Enable this setting to track user clicks on the outbound links.
• Enable Accurate Track Bounce: This setting enables the accurate bounce rate with a non-bounce event that is registered after 15 seconds (15000 ms). For more information on this setting, refer to the Yandex.Metrica documentation.
• Enable WebVisor: Enable this setting to use Yandex.Metrica’s sesssion replay feature.
• Container name: Enter the name of your Yandex.Metrica ecommerce data container that you set while creating a new counter. If not specified, RudderStack sets it to dataLayer by default.
• Map your event name with supported Yandex.Metrica event name: Use this setting to map the RudderStack event to the Yandex.Metrica event selected from the dropdown.
• Goal ID: Enter your Yandex.Metrica goal ID.
• Client-side Events Filtering: This setting lets you specify which events should be blocked or allowed to flow through to Yandex.Metrica. For more information on this setting, refer to the Client-side Events Filtering guide.
• Use device mode to send events: As this is a web device mode-only destination, this setting is enabled by default and cannot be disabled.
• Consent management settings: Configure the consent management settings for the specified source by choosing the Consent management provider from the dropdown and entering the relevant consent category IDs. See Consent Management in RudderStack for more information on this feature.

Refer to the FAQ section for more information on obtaining the Yandex.Metrica tag ID, container name, and goal ID.

Identify

You can use the identify call to identify a user in Yandex.Metrica. If a contact already exists, RudderStack updates the contact details.

A sample identify call is shown below:

rudderanalytics.identify('1hKOmRA4el9Z', {
      firstName: 'Alex',
      lastName: 'Keener',
      email: "alex@example.com"
    }

RudderStack uses Yandex.Metrica’s setUserID method to associate the userId with the user’s client ID during a particular session. To update the information of a user with a specfic userId, RudderStack uses the userParams method.

Supported mappings

The following table lists the mappings between the RudderStack attributes and the Yandex.Metrica properties:

Track

You can use the track call to send your ecommerce events to Yandex.Metrica.

A sample track call is shown below:

rudderanalytics.track("Order Completed", {
  order_id: "34897497",
  coupon: "BB20",
  currency: "INR",
  products: [{
      product_id: "43521",
      currency: "INR",
      name: "Rudder Bag",
      price: 3700.99,
      brand: "Nice",
      category: "Bags",
      quantity: 3,
    },
    {
      product_id: "37333",
      currency: "INR",
      name: "RudderStack T-shirt",
      price: 1651.55,
      brand: "Adidas",
      category: "Bags",
      quantity: 3,
    },
  ],
});

Event mapping

This destination does not strictly adhere to the RudderStack Ecommerce Event Spec.

The following table lists the default mappings between the RudderStack events and the Yandex.Metrica events:

You can also map any other event to the above Yandex.Metrica events via the dashboard settings.

Supported property mappings

The following table lists the properties mapping for Yandex.Metrica’s detail, add, and remove events:

The following mappings are applicable only for the purchase event:

Page

You can use the page call to send all page view data to Yandex.Metrica.

A sample page call is shown below:

rudderanalytics.page(
  "Cart",
  "Cart Viewed", {
    referrer: "https://www.mysite.com/search?q=bestseller",
    title: "The best seller items",
    url: "https://www.mysite.com/bestseller/1"
  });

RudderStack uses Yandex.Metrica’s hit method to send all page view data.

Supported mappings

The following table lists the mappings between the RudderStack attributes and the Yandex.Metrica properties:

FAQ

What is the Yandex.Metrica container name? Where can I find it?

You can set your Yandex.Metrica data container name while setting up your counter for your website:

Where can I find my Yandex.Metrica tag ID?

To obtain your Yandex.Metrica tag ID, follow these steps:

1. Log into your Yandex.Metrica dashboard.
2. From the left sidebar, click Visitors. You can see the tag ID listed in the dashboard as well as in the URL:

Where can I find my Yandex.Metrica goal ID?

To obtain your Yandex.Metrica tag ID, follow these steps:

1. Log into your Yandex.Metrica dashboard.
2. From the left sidebar, click Goals. You can see the goal ID listed in the dashboard against your created targets/goals:

Questions? Contact us by email or on Slack