# Яндекс Метрика

Dig into traffic and conversion drops right in the chat

Веб-аналитика — счётчики, цели, отчёты и логи посещений

## How the agent works with Яндекс Метрика

The agent starts from the list of counters your account can reach and then works through the Metrica API: it builds reports on visits, sources, pages and devices, counts goal completions and conversion, and when the aggregates are not enough it drops down to visit logs for the details of an individual session. It always compares a period against the previous one, so a drop shows up as a change rather than as a single number.

The agent keeps two Metrica specifics in mind. First, data ripens: the freshest tail of the day is not fully processed, so «yesterday versus the day before» easily shows a false dip, and for comparisons the agent takes closed periods. Second, conversion exists exactly as far as goals are configured in the counter. If a goal is not set up it will not appear in the report — and the agent says the goal is missing rather than that conversion is zero.

The agent never writes to Metrica: it does not create or rename goals and does not touch filters, segments or counter settings. All the work is reading and analysis: rolling up traffic by channel, finding the sources and pages where visits and goals slipped, spikes and dips in traffic tied to sources and devices, and a short digest of the key numbers instead of opening the cabinet.

The agent builds reports through the reporting API: it picks the metrics and dimensions the question needs rather than pulling the whole set, and splits a long period into windows. When the aggregates are not enough it goes to the visit logs — those do not answer at once but prepare an export, so per-visit detail arrives after the summary. The agent holds the request rate itself, and if there is no data for the period or the counter is unavailable it says so directly instead of showing an empty table.

## Integration scenarios

### Digging into a traffic or conversion drop
The agent compares the period with the previous one, finds the sources and pages where visits and goals slipped and shows what actually broke.

### Report on sources and goals
The agent rolls up traffic by channel, calculates goal conversion and points out which sources bring buyers and which drain the budget.

### Spotting traffic anomalies
The agent tracks spikes and dips on the counter, ties them to sources and devices and warns you about sharp changes.

### Metrics digest without opening the cabinet
The agent pulls the counter's key numbers — visits, bounces, conversions — and sends a short digest straight to chat.

### The path to a conversion
The agent pulls the visit logs and shows which pages the sessions that reached a goal walked through and at which step the rest broke off.

### Every site in one table
The agent goes through all the counters it can reach, rolls visits, bounces and conversion for each site into one table and shows where the returns have slipped.

## How to connect

**Before you connect**

- A Yandex account with rights to the counters you need
- View-only access is enough — Metrica is used read-only
- One-click sign-in: no tokens or keys to copy

### Pick the Yandex ID to sign in with
The agent sees exactly the counters one Yandex account has access to. Sign out of the other accounts in the browser first.

### Check your login on the Access tab
Open metrika.yandex.ru, pick the counter and go to Settings → the Access tab. Your login must be listed there or own the counter, otherwise it stays invisible.

### Ask the owner to click Add user
In Settings → Access the counter owner clicks Add user and enters your Yandex login. The View level is enough for reports on visits, traffic sources and goals.

### For all counters — Add representative
If there are many counters on someone else's account, its owner opens Account settings → Representatives → Add representative: access covers the whole account.

## FAQ

### How do I connect Yandex Metrica?
By signing in to your Yandex account in one click: you confirm access and the agent sees the counters you have rights to. No tokens or keys to copy.

### What data does the agent see?
Counters, goals, reports on visits, sources and devices, and visit logs — for the counters your account has access to.

### Can the agent change anything in Metrica?
No. Metrica is used read-only: the agent only collects and analyzes reports, changing nothing in the counter settings.

### How fresh is the data the agent gets?
The agent requests reports through the Reporting API on demand, so the data matches the counter's current state, allowing for Metrica's usual processing delay.

[Open Яндекс Метрика](https://metrika.yandex.ru)