Yandex.Metrica enables customizable report analytics so marketers can toggle between attribution models, segment and compare audiences based on custom details like OS, number of visits, and ad blocker usage. It also supports session replay, heat maps, form analytics so marketers can review user movements such as mouseclicks, form fill ins, and keystrokes. Finally, it supports custom events tracking and purchase funnels, and automates eCommerce reports to calculate metrics like cost per order and total costs.
This document was last updated on January 18, 2019. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, please let us know!
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “Yandex.Metrica” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Enter your Counter ID that you can find in your Yandex.Metrica UI navigating to Settings > Tag.
- In about 45 minutes the CDN will be updated and Yandex.Metrica’s snippet will be initialized onto your page.
Once you’ve followed these steps you should be good to go! No additional code will be required for your Yandex.Metrica Destination to start tracking activity on your page.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
Enable Accurate Bounce Tracking
Enables the accurate bounce rate, with a non-bounce event registered after 15000 ms (15 s).
Enable Clickmap Tracking
Enables heat mapping reports.
Your Counter ID
Enable Hash Tracking
Enables hash tracking, allowing correct calculation of the number of pageviews on pages that are updated without being refreshed.
Enable External Link Tracking
Enables external link tracking.
Lets you see playback of a customer’s actions including mouse movement, scrolling and clicks.
Adding Yandex Metrica to the integrations objectTo add Yandex Metrica to the
integrationsJSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration: