---
metadata:
  - name: generator
    content: Diplodoc Platform v5.50.6
alternate:
  - https://yandex.ru/support/metrica/en/data/offline-conversion-data.md
  - https://yandex.ru/support/metrica/es/data/offline-conversion-data.md
  - https://yandex.ru/support/metrica/pt/data/offline-conversion-data.md
  - https://yandex.ru/support/metrica/ru/data/offline-conversion-data.md
  - https://yandex.ru/support/metrica/tr/data/offline-conversion-data.md
  - https://yandex.ru/support/metrica/zh/data/offline-conversion-data.md
title: Transmitting and processing data
description: "How to configure the transmission of offline conversions in the Yandex\_Metrica web interface."
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/support/metrica/en/llms.txt


# Transmitting and processing data

You can transmit information using:
- The Yandex Metrica web interface.
- The Yandex Metrica API. [Data import guide](https://yandex.ru/dev/metrika/doc/api2/practice/offline-conv-docpage/)
- Albato automation service. [Setup instructions](https://albato.ru/yandex-offline-conversion)

To configure the transfer of offline conversions in the Yandex Metrica web interface:

1. Prepare [special identifiers](https://yandex.ru/support/metrica/en/data/offline-params.md#ids).
1. On the **Goals** page, create a [JavaScript event goal](https://yandex.ru/support/metrica/en/general/goal-js-event.md) in the left menu. For the goal ID, specify the event you want to track (for example, order confirmation — "order_confirmed"). You will need this ID when creating a CSV file.
    
   If you want to analyze offline conversions separately from conversions on the website, enter a more specific description in **Name** (for instance, “Purchase in office”, “Offline goal”, or “Cash payment”). This will make it easier to find the goal in the list.
    
1. [Create a CSV file](#make-file) with conversion data, following the recommendations.
1. [Upload the file](#upload-file) to Yandex Metrica.


{% note info %}

The data will appear in Yandex Metrica reports within 2 hours of uploading.

{% endnote %}

## Preparing the CSV file {#make-file}

[Specification for the CSV format](http://www.rfc-editor.org/rfc/rfc4180.txt)

[CSV format description](https://ru.wikipedia.org/wiki/CSV)

#|
||
**Field name**
|
**Required**
|
**Description**
|
**Example**
||
||
[ClientID](https://yandex.ru/support/metrica/en/data/offline-params.md) \| [UserID](https://yandex.ru/support/metrica/en/data/offline-params.md) \| [yclid](https://yandex.ru/support/metrica/en/data/offline-params.md) \| [PurchaseId](https://yandex.ru/support/metrica/en/data/offline-params.md)
|
Yes[*](**)
|
ID of a site visitor or Yandex Direct campaign.
|
12345
||
||
`Target`
|
Yes
|
Goal ID specified during goal creation
|
order_confirmed
||
||
`DateTime`
|
Yes
|
Conversion time in [Unix Time Stamp](http://www.unixtimestamp.com/index.php) seconds. When converting event date and time to this format, make sure to account for the tag’s time zone.
|
1481718166
||
||
`Price`
|
No
|
[Revenue by goal](https://yandex.ru/support/metrica/en/general/price-goal.md)
|
1000
||
||
`Currency`
|
No
|
<!-- source: en/_includes/ecommerce/data/id-about/currency-iso4217.md -->
Three-letter [ISO 4217 currency code](https://www.six-group.com/en/products-services/financial-information/data-standards.html#scrollTo=currency-codes).
<!-- endsource: en/_includes/ecommerce/data/id-about/currency-iso4217.md -->


<!-- source: en/_includes/ecommerce/data/id-about/currency-note.md -->
If a different currency is passed, null values are sent instead of currencies and amounts.
<!-- endsource: en/_includes/ecommerce/data/id-about/currency-note.md -->
|
RUB
||
|#

<sup >*</sup> At least one identifier is required.

## Uploading the file {#upload-file}

To upload the prepared file with the data, go to the **Settings**  page (the **Upload data** tab). In the **Upload offline conversions**, follow these steps:

1. Click **Upload data**.
1. In the window that opens, select the linking type depending on the type of the ID you want to upload.
1. Select the file on your computer and add comments to the upload, if necessary.
1. Click **Upload data**.

[Sample CSV file for uploading data](https://download.cdn.yandex.net/from/yandex.ru/support/ru/metrica/files/offline-conversions.csv)

{% note info %}

Your uploaded CSV file should be no larger than 1 GB and use UTF-8 encoding.

{% endnote %}

## File upload errors {#error}

Sometimes Yandex Metrica can't match offline conversions to their respective sessions. The most common causes of matching errors are described below:


#|
||
**Reason for error**
|
**Solution**
||
||
The goal identifiers specified in the file were not found in Yandex Metrica
|
Make sure that the file contains the same goal identifiers as shown in Yandex Metrica. To check the goal ID, open the **Goals** tab from the left menu.
||
||
The user IDs specified in the file aren't found in Yandex Metrica
|
[Make sure](https://yandex.ru/support/metrica/en/data/offline-params.md#ids) the way to transmit the IDs is set up correctly.

If you are using UserID and the data transfer is configured correctly, try uploading the file later. Most likely, some of the customers with a UserID specified in the file haven't visited the website yet, so the system hasn't had a chance to link their UserID from your database to their internal СlientID in Yandex Metrica.
||
||
Session dates do not fall within the period of adding offline data to sessions. This means that more than 21 days have passed between the date of the user’s last session on the site and the start of file processing.
|
In this case, you won't be able to add offline conversions to Yandex Metrica. 
 			 
[Period of adding offline data to sessions](https://yandex.ru/support/metrica/en/data/offline-params.md)
||
|#

<!-- source: en/_includes/buttons/chat-button.md -->
[Chat with us](https://yandex.ru/chat/#/user/036e6a02-3620-9cdc-4c5e-a34667a7379e?utm_source=spravka){.button}

<!-- source: en/_includes/styles/href-to-button.md -->

<!-- endsource: en/_includes/styles/href-to-button.md -->
<!-- endsource: en/_includes/buttons/chat-button.md -->

<!-- source: en/_includes/sources/support-button.md -->
<div class="cut-button">

{% cut "Write an email" %}


<!-- source: en/_includes/popup/id-popup/wrong-sup.md -->
Please note: Our support team will never initiate a call to you. Do not follow any instructions of people who call you and introduce themselves as the Yandex Metrica support team.
<!-- endsource: en/_includes/popup/id-popup/wrong-sup.md -->


<div style="padding: 15px;
     margin: 10px 0;
     background: #FFFFFF;
     border-radius: 10px;
     border: 1px solid var(--g-color-line-generic);">
  <iframe style="background: #FFFFFF;"
        height="700"
        width="100%"
        frameborder="0"
        src="https://forms.yandex.ru/surveys/10019201.1cb990cef225b369d8f28f4d76817c247f25992d/?&iframe=1&lang=en">
  </iframe>
</div>

{% endcut %}

</div>

<!-- source: en/_includes/styles/cut-button.md -->

<!-- endsource: en/_includes/styles/cut-button.md -->
<!-- endsource: en/_includes/sources/support-button.md -->

<!-- source: en/_includes/footer-links.md -->
- - -

<div class="borderless-table">

#|
||
Useful links

- [Demo tag](https://metrika.yandex.com/r/dashboard?)
- [Add a tag](https://metrika.yandex.com/add/)
- [Free tag setup](https://yandex.com/promo/freeservice/metrica?utm_source=help_metrica_ru&utm_medium=cpc&utm_campaign=1)
- [Yandex Metrica API](https://tech.yandex.com/metrika/)
- [Suggest your idea](https://yandex.com/support/metrica/troubleshooting/idea.html)
- [Discuss in Telegram](https://t.me/yandexmetrika)
|
Online training

- [Get a Yandex Metrica certificate](https://yandex.ru/adv/expert/exam/metrika/?utm_source=metrika_help&utm_medium=web&utm_campaign=static&utm_content=useful_links)


- [Take a training course](https://yandex.ru/adv/edu/online/metrika?utm_source=metrika_help&utm_medium=web&utm_campaign=static&utm_content=useful_links)

||
|#

</div>

<!-- source: en/_includes/styles/table-style.md -->

<!-- endsource: en/_includes/styles/table-style.md -->
<!-- endsource: en/_includes/footer-links.md -->

[**]: <sup >*</sup> At least one identifier is required.