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 md5 hashes of the customer's email addresses.The email addresses that are subject to hashing must have the format specified above.	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 md5 hashes of the customer's phone numbers.The phone numbers that are subject to hashing must have the format specified above.	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.	By transmitting the ID, you can re-link an order from one customer 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. If you haven't transmitted id and client_uniq_id in both uploads, then you'll have two distinct customers and two orders in the system. If client_uniq_id has been transmitted in both uploads, then you'll have a single order and a single customer like before. 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: The order is created but not paid. CANCELLED: Canceled. SPAM: Spam.	Conversions with the IN_PROGRESS status are added to the goal “CRM: Order created”. Conversions with the PAID status are added to the goal “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. If no status is specified for the conversions, all conversions are added to the goal “CRM: Order paid”.
revenue	Revenue. The final price of the order. A decimal value.	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 md5 hashes of the customer's email addresses.The email addresses that are subject to hashing must have the format specified above.	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 md5 hashes of the customer's phone numbers.The phone numbers that are subject to hashing must have the format specified above.	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.	By transmitting the ID, you can re-link an order from one customer 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. If you haven't transmitted id and client_uniq_id in both uploads, then you'll have two distinct customers and two orders in the system. If client_uniq_id has been transmitted in both uploads, then you'll have a single order and a single customer like before. 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: The order is created but not paid. CANCELLED: Canceled. SPAM: Spam.	Conversions with the IN_PROGRESS status are added to the goal “CRM: Order created”. Conversions with the PAID status are added to the goal “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. If no status is specified for the conversions, all conversions are added to the goal “CRM: Order paid”.
revenue	Revenue. The final price of the order. A decimal value.	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:

1. Add new conversions to the file in real time or at least once a day.
2. Be sure that the file includes up-to-date conversions over the previous three days.

By following these rules, you ensure that the strategy algorithms receive signals about the completed goals at a minimal delay and can timely change the bids in your campaigns.

Stage 3. Adding a link to the source

1. Go to the Conversions page, then click Add a conversion source.

   
2. Select a source for the upload:

   File by link

   1. Enter the name of the source.
   2. Add a link to the conversion file.
   3. Select the Yandex Metrica tag from the list for data upload: the Yandex Direct username you add the source from and the username of the chief representative, if you add from the representative's username, must have access to edit the tag.
   4. If needed, specify the value of conversions. For example, set it manually. If you enter your conversion revenue in the file, select the value “From file”.

   File over FTP

   1. Enter the name of the source.
   2. Add the server username and password so that the Yandex Metrica's robot can collect the data.
   3. Enter the port and host.
   4. In the Path to the file on the server field, enter a link to the file on the server for the username specified in the source settings.

      To determine the file path, use any FTP client. Enter your username and connect to your server.

      The path should start with “/”. For example:

      • /file_name.csv
      • /folder_name/file_name.csv

      To test the path, download the file at this path using your FTP client.

   5. Select the Yandex Metrica tag from the list for data upload: the Yandex Direct username you add the source from and the username of the chief representative, if you add from the representative's username, must have access to edit the tag.
   6. Enable if the protocol is secure.

   7. If needed, specify the value of conversions. For example, set it manually. If you enter your conversion revenue in the file, select the value “From file”.

   File over SFTP

   1. Enter the name of the source.
   2. Add the server username and password so that the Yandex Metrica's robot can collect the data.
   3. Enter the port and host.
   4. In the Path to the file on the server field, enter a link to the file on the server for the username specified in the source settings.

      To determine the file path, use any SFTP client. Enter your username and connect to your server.

      The path should start with “/”. For example:

      • /file_name.csv
      • /folder_name/file_name.csv

      To test the path, download the file at this path using your SFTP client.

   5. Select the Yandex Metrica tag from the list for data upload: the Yandex Direct username you add the source from and the username of the chief representative, if you add from the representative's username, must have access to edit the tag.

   6. If needed, specify the value of conversions. For example, set it manually. If you enter your conversion revenue in the file, select the value “From file”.

   Google Sheets

   Attention.

   Grant the “View” access to the spreadsheet for the account import@yandex-direct-conversions.iam.gserviceaccount.com. For secure data storage, restrict access to the spreadsheet.

   Make sure that the data you need to transmit is on the first tab of the spreadsheet.

   1. Enter the name of the source.
   2. Specify a link to Google Sheets.
   3. Select the Yandex Metrica tag from the list for data upload: the Yandex Direct username you add the source from and the username of the chief representative, if you add from the representative's username, must have access to edit the tag.

   4. If needed, specify the value of conversions. For example, set it manually. If you enter your conversion revenue in the file, select the value “From file”.
   5. Google Sheets example

It's enough to add a conversion source only on one Yandex Direct username. After you upload the data, the goals created in Yandex Metrica will be available on all Yandex Direct usernames that have access to the Yandex Metrica tag to which the conversions were uploaded.

First-time upload and update of the conversion data

When you upload your conversion data for the first time, enable Offline conversion tracking. Conversions are added only to the sessions that occurred after you enabled the option. This means that the conversions received before the first data upload won't be linked to sessions and displayed in Yandex Metrica reports.

This option sets the interval within which the conversion data that you transmit to Yandex Metrica will be added to the session data. The interval is 21 days. This means that the conversion data won't be added to the session data if the conversion took place later than 21 days since the latest site session.

When the conversion data has been added to the session data, you have 90 days after the date of the session to fix or update this conversion. This might be the case when you need to change the conversion revenue after the order is paid and change the conversion status from IN_PROGRESS to PAID.

How do I check that everything is running properly?

If the goals were created, it means that the file was validated: the next time the data is uploaded, statistics on conversions that could be attributed to sessions that occurred after the first upload will appear in Yandex Metrica and in the Conversion center.

If there are no conversions created in Yandex Metrica or an error bar appears in the Conversion center within 24 hours, it means there was an error in the file itself or in the source settings. Learn about the most common errors in the "Loading errors" section.

Loading errors

If a red bar with an error message appears when you add a source to the Conversion center, use a solution from the list:

Error connecting to the server. Check your connection settings

Make sure that the server data is correct: check the port, host, and path to the file on the server.

You don't have permission to write data to the Yandex Metrica tag. Request permission or try connecting from another account

Make sure that the Yandex Direct username that you use to add the source to the Conversion center has edit access to the Yandex Metrica tag specified in the source settings. If you are adding a source from a representative's username, make sure that the username of the chief representative has access to edit the tag.

Error downloading the file. Check your connection settings

Make sure that all data specified in the source settings is correct. Try to download the file yourself using the link or from the FTP server that you specified.

Invalid server authentication credentials. Check your connection settings

Make sure that you have entered the correct username and password to the server.

Invalid delimiter in the file. Check the file and update it

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.

To transmit multiple values in one column, enclose them in double quotation marks and use a comma without a space to separate them. For example, "79876543210,79991234567".

No valid data found in the file. Check the file and update it

Check that the column names, date and time format, phone numbers, and email addresses are correct.

Insufficient rights to download the file. Check your connection settings

Grant the “View” access to the spreadsheet for the account import@yandex-direct-conversions.iam.gserviceaccount.com. For secure data storage, restrict access to the spreadsheet.

The file is too large, the maximum size is 300 MB

Upload a smaller file. If you are uploading for the first time, just send the conversions that you received yesterday.

Unsupported file encoding. Only UTF-8 encoding is supported

Change the encoding of the file.

The table can include only one sheet. Check the table and update it

The table cannot contain more than one sheet. Move all the data in the table to one sheet and delete the rest. Update the file on the source.

Internal error downloading the file. Contact support to solve the issue

Unknown error. Contact your personal manager or the support service.

Errors in the file

Once you have uploaded the data from the source to the conversion center, you might get a file with errors. This means that some data in the source was invalid. These kinds of errors are collected in the file. The ways to solve them are given in the table.

Conversion statistics

In the Conversion center, you can track statistics on the completion of goals that were previously created in Yandex Metrica.

For example, this is useful if you run ads in several usernames and want to see the conversion statistics on all usernames. Instead of adding a conversion source to each Yandex Direct username, add it to one username, upload the data about the created Yandex Metrica goals on all the other usernames, and track statistics on the completion of goals:

1. On the Conversions page, click Add a conversion source. Select Yandex Metrica.
2. Select the Yandex Metrica tag for which you uploaded the data on offline conversions and call conversions. If the tag isn't in the list, ask the tag owner to allow access for your username.
3. Select the goals available on the tag. If revenue transmission isn't configured for the goals, set the value manually.