---
metadata:
  - name: generator
    content: Diplodoc Platform v5.48.2
alternate:
  - https://www.yandex.com/dev/metrika/en/management/chats.md
  - https://www.yandex.com/dev/metrika/ru/management/chats.md
---
> **Documentation Index:** Fetch the complete configuration index at https://www.yandex.com/dev/metrika/en/llms.txt

# Tracking chats

With Yandex Metrica, you can import chats in [messengers](*mes) as [offline data](https://www.yandex.com/dev/metrika/en/data-import/index.md) and attribute them to site sessions.

After you upload chats, the automatic goal **Chat** will appear in the tag. You can use this goal in all reports and for ad optimization. 

Data appears in reports after [the uploaded file is processed](*obr).

## How to add chats {#how-to}

There are two ways to add chats:

- Using chat tracking services: your provider gives you a [code](*code) that is embedded in your site, collects the necessary Yandex Metrica IDs, and generates events for importing. 

- Using custom integration: if you choose this option, collect the [IDs](*ids) and prepare a CSV file for importing. 

## What data you can transmit {#what-data}

You can transmit the following data:

- [Event time](*time).

- [Chat platform](*mes). 

- At least one [chat partner ID](*id).

Additionally, you can transmit this data:

- [Whether the chat was responded to](*bool).

- Tags.

- Cost and currency.

- Site page URL. 

- Link to the conversation in a tracking system. 

To learn more about the format, see [Passing chat data](https://www.yandex.com/dev/metrika/en/management/chats-transfer-data.md).

[*mes]: WhatsApp, Telegram, Viber

[*obr]: Processing can take up to 2 hours.

[*code]: Widget or script

[*ids]: ClientID, UserID, Yclid, and, if necessary, PurchaseID 

[*time]: Unix, UTC

[*id]: Nickname, ID, or phone number

[*bool]: 0/1