Skip to contentSkip to navigationSkip to topbar
Twilio Segment Docs
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Yandex.Metrica Destination

Destination Info
  • Accepts Page, Alias, Group, Identify and Track calls.
  • Refer to it as Yandex Metrica in the Integrations object
Components
Connection Modes
Device-modeCloud-mode
✅ Web❌ Web
❌ Mobile❌ Mobile
❌ Server❌ Server

Yandex.Metrica(link takes you to an external page) 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.

Our Yandex.Metrica destination code is open sourced on GitHub. Feel free to check it out here for JavaScript(link takes you to an external page).

Getting Started

getting-started page anchor
  1. From the Segment web app, click Catalog.
  2. Search for "Yandex.Metrica" in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. Enter your Counter ID that you can find in your Yandex.Metrica UI navigating to Settings > Tag.

Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Yandex.Metrica's snippet on your page and sending data.

Once you've followed these steps you should be good to go! No additional code is required for your Yandex.Metrica Destination to start tracking activity on your page.

Settings

settings page anchor

Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription
Enable Accurate Bounce Trackingboolean

Optional

Enables the accurate bounce rate, with a non-bounce event registered after 15000 ms (15 s).

Default: false
Enable Clickmap Trackingboolean

Optional

Enables heat mapping reports.

Default: false
Counter IDstring
required

Your Counter ID

Enable Hash Trackingboolean

Optional

Enables hash tracking, allowing correct calculation of the number of pageviews on pages that are updated without being refreshed.

Default: false
Enable External Link Trackingboolean

Optional

Enables external link tracking.

Default: false
Enable WebVisorboolean

Optional

Lets you see playback of a customer's actions including mouse movement, scrolling and clicks.

Default: false