Conversion center

Uploading conversion data

You can export your conversion data from the CRM database to a CSV file and add it to the Conversion center using alternative upload methods: from an FTP or SFTP server, by an HTTP or HTTPS link, or using Google Sheets. From the Conversion center, the data will be sent to Yandex Metrica where it'll be used for generating conversions and goals.

Statistics and goal optimization will be available to all Yandex Direct usernames that have access to the Metrica tag to which the data is uploaded.

The upload process consists of three steps:

• 1. Create a file with data in the standard format.
• 2. Upload the file to the source.
• 3. Add a link to the source.

Stage 1. Preparing the file

Create a CSV file. Use a semicolon to separate columns in a CSV file. For example:

id;create_date_time;client_uniq_id;client_ids;emails;phones;order_status;revenue

Name and description of fields:

Name	Description	Note
Conversion date and time. Required field
create_date_time	The date and time when the order was created in the tag's time zone. This value can't be changed.	Specify the date and time. If you don't store the conversion time in your CRM, send only the conversion date. We will add the time of 23:59:59 to each of your conversions. This way we can attribute all conversions that occurred on that day before 23:59:59 to individual sessions. Learn more about the date and time format.
User IDs. At least one of the fields is required
client_ids	ClientID list. For more information, see Transmitting itemized data.	For transmitting online orders, set up the data collection and transmit the ClientID. This enables you to attribute all your online conversions.
emails	A list of the client's email addresses. A Latin string that includes the @ character and the domain name. Avoid uppercase letters. Example: mail@yandex.ru. To transmit multiple values, enclose them in double quotes and separate them by a comma without a space. For example,"mail@example.com,mail2@example.com"	If you use an invalid format for email addresses, we won't be able to attribute conversions to sessions.
phones	A list of the customer's phone numbers. A numeric string containing a mobile phone number with the country code. Avoid any extra characters and spaces. Example: 79995551111. To transmit multiple values, enclose them in double quotes and separate them by a comma without a space. For example,"79876543210,79991234567"	If you use an invalid format for phone numbers, we won't be able to attribute conversions to sessions.
emails_md5	A list of the client's MD5-hashed email addresses. Before the hashing, email addresses must be in the above-specified format.	If you apply the hash to ill-formatted email addresses, we won't be able to attribute conversions to sessions.
phones_md5	A list of the client's MD5-hashed phone numbers. Before the hashing, phone numbers must be in the above-specified format.	If you hash phone numbers in an invalid format, we won't be able to attribute conversions to sessions.
Optional fields
id	The ID of the order in your CRM. Arbitrary value.	Transmitting the id allows you to: Update order status from IN_PROGRESS to PAID. For example, you send an order with the IN_PROGRESS status. A month later, the order is paid, and you want to send the PAID status. Learn more If no id values were transmitted in both uploads, the orders are attributed to the sessions that occurred closest to the conversion date. If id values were transmitted in both uploads, then the order with the IN_PROGRESS status is attributed to the session that occurred closest to the conversion date, and the order with the PAID status is attributed to the same session. Reassign the order from one client to another. For example, you transmit a customer order with a phone number specified. The next day, you transmit the same order in a file, but with an email address. Learn more If neither id nor client_uniq_id were transmitted in both uploads, the system will include two distinct clients and two orders. If client_uniq_id was transmitted in both uploads, there will be one order and one client in the system. If you only transmit the id in both cases, you'll have two different customers in the system, but a single order that will be re-linked to the latest customer.
client_uniq_id	The ID of your customer in the CRM that is linked to the order.	If you add or change the ID of your customer, then you can use client_uniq_id to merge the customer's future orders with their past orders. Otherwise, you'll have two different customers.
order_status	Type of the order status. You can change the status. Possible values: PAID: Paid (default). IN_PROGRESS: Order created but not paid. CANCELLED: Canceled. SPAM: Spam.	Conversions with the IN_PROGRESS status will be added to the “CRM: Order created” goal. Conversions with the PAID status are added to the goal “CRM: Order paid”. If you send orders only with the PAID status, such conversions will be added to both goals: “CRM: Order created” and “CRM: Order paid”. If the conversion status is not specified, then all conversions will be assigned the PAID status, and such conversions will be added to both goals: “CRM: Order created” and “CRM: Order paid”. If you transmit orders with the SPAM and CANCELLED statuses, you can create segments for users who have made such orders. You can collect Lal (Look-alike — a segment of similar users) and use the segment in adjustments in the campaign. To make sure that the order status is updated successfully, send the order ID from CRM in the upload.
revenue	Revenue. The final price of the order. A decimal value. Use a dot to separate whole and fractional parts. For example: 1508.50.	Transmit the revenue from your order. This value will be used in end-to-end analytics reports to show how much money you earned on orders from your ad channels. The value will be shown in the “Revenue” metric.
cost	The cost of the order. A decimal value.	Transmit the cost of your orders to see profits in your end-to-end analytics reports. The profit will be calculated by the Revenue - Cost formula.

Name	Description	Note
Conversion date and time. Required field
create_date_time	The date and time when the order was created in the tag's time zone. This value can't be changed.	Specify the date and time. If you don't store the conversion time in your CRM, send only the conversion date. We will add the time of 23:59:59 to each of your conversions. This way we can attribute all conversions that occurred on that day before 23:59:59 to individual sessions. Learn more about the date and time format.
User IDs. At least one of the fields is required
client_ids	ClientID list. For more information, see Transmitting itemized data.	For transmitting online orders, set up the data collection and transmit the ClientID. This enables you to attribute all your online conversions.
emails	A list of the client's email addresses. A Latin string that includes the @ character and the domain name. Avoid uppercase letters. Example: mail@yandex.ru. To transmit multiple values, enclose them in double quotes and separate them by a comma without a space. For example,"mail@example.com,mail2@example.com"	If you use an invalid format for email addresses, we won't be able to attribute conversions to sessions.
phones	A list of the customer's phone numbers. A numeric string containing a mobile phone number with the country code. Avoid any extra characters and spaces. Example: 79995551111. To transmit multiple values, enclose them in double quotes and separate them by a comma without a space. For example,"79876543210,79991234567"	If you use an invalid format for phone numbers, we won't be able to attribute conversions to sessions.
emails_md5	A list of the client's MD5-hashed email addresses. Before the hashing, email addresses must be in the above-specified format.	If you apply the hash to ill-formatted email addresses, we won't be able to attribute conversions to sessions.
phones_md5	A list of the client's MD5-hashed phone numbers. Before the hashing, phone numbers must be in the above-specified format.	If you hash phone numbers in an invalid format, we won't be able to attribute conversions to sessions.
Optional fields
id	The ID of the order in your CRM. Arbitrary value.	Transmitting the id allows you to: Update order status from IN_PROGRESS to PAID. For example, you send an order with the IN_PROGRESS status. A month later, the order is paid, and you want to send the PAID status. Learn more If no id values were transmitted in both uploads, the orders are attributed to the sessions that occurred closest to the conversion date. If id values were transmitted in both uploads, then the order with the IN_PROGRESS status is attributed to the session that occurred closest to the conversion date, and the order with the PAID status is attributed to the same session. Reassign the order from one client to another. For example, you transmit a customer order with a phone number specified. The next day, you transmit the same order in a file, but with an email address. Learn more If neither id nor client_uniq_id were transmitted in both uploads, the system will include two distinct clients and two orders. If client_uniq_id was transmitted in both uploads, there will be one order and one client in the system. If you only transmit the id in both cases, you'll have two different customers in the system, but a single order that will be re-linked to the latest customer.
client_uniq_id	The ID of your customer in the CRM that is linked to the order.	If you add or change the ID of your customer, then you can use client_uniq_id to merge the customer's future orders with their past orders. Otherwise, you'll have two different customers.
order_status	Type of the order status. You can change the status. Possible values: PAID: Paid (default). IN_PROGRESS: Order created but not paid. CANCELLED: Canceled. SPAM: Spam.	Conversions with the IN_PROGRESS status will be added to the “CRM: Order created” goal. Conversions with the PAID status are added to the goal “CRM: Order paid”. If you send orders only with the PAID status, such conversions will be added to both goals: “CRM: Order created” and “CRM: Order paid”. If the conversion status is not specified, then all conversions will be assigned the PAID status, and such conversions will be added to both goals: “CRM: Order created” and “CRM: Order paid”. If you transmit orders with the SPAM and CANCELLED statuses, you can create segments for users who have made such orders. You can collect Lal (Look-alike — a segment of similar users) and use the segment in adjustments in the campaign. To make sure that the order status is updated successfully, send the order ID from CRM in the upload.
revenue	Revenue. The final price of the order. A decimal value. Use a dot to separate whole and fractional parts. For example: 1508.50.	Transmit the revenue from your order. This value will be used in end-to-end analytics reports to show how much money you earned on orders from your ad channels. The value will be shown in the “Revenue” metric.
cost	The cost of the order. A decimal value.	Transmit the cost of your orders to see profits in your end-to-end analytics reports. The profit will be calculated by the Revenue - Cost formula.

CSV file example

Google Sheets example

Stage 2. Uploading a file to the source

Configure the data upload to any of the suitable sources:

• FTP server.
• SFTP server.
• HTTP/HTTPS link.
• Google Sheets.

When optimizing your ads based on conversions from a file, please follow two rules: