Connect a Reverse ETL source to Yandex.Metrica Offline Events

Configure a Reverse ETL source with your Yandex.Metrica Offline Events destination.

This guide takes you through the steps to connect a Reverse ETL source to the Yandex.Metrica Offline Events destination.

Set up connection


The Reverse ETL feature supports only source-driven pipeline configuration.

Make sure you have set up a RETL source and connected it to your Yandex.Metrica Offline Events destination before following the below steps.

  1. Confirm the connection settings for Yandex.Metrica Offline Events destination and click Continue.
To sync the data successfully, make sure to give RudderStack the necessary permissions to access your Yandex.Metrica account. Also, enter the Counter ID and Goal ID in the configuration settings.
  1. In the Data Mapping section, select the Object.
  2. Specify the Sync mode to specify how RudderStack should sync the data to Yandex.Metrica.
  3. In Choose identifier, specify the warehouse column that RudderStack uses to identify your records.

You can map this warehouse column to any of the following Yandex.Metrica fields:

  • User ID
  • Client ID
  1. Map the other warehouse columns to specific Yandex.Metrica fields using the Map fields setting.

Supported mappings

RudderStack maps the following properties to the corresponding Yandex.Metrica properties:

RudderStack sends the offline conversion events as identify calls to Yandex.Metrica.
RudderStack propertyYandex.Metrica propertyDescription
USER_IDMapped when the user ID is assigned by the site owner.
CLIENT_IDMapped when the site visitor ID is assigned by Yandex.Metrica.
YCLIDMapped when the click ID on a Yandex.Direct ad is assigned by Yandex.Direct.
TargetThe goal ID.
DateTimeDate and time of the conversion in UNIX timestamp.
properties.pricepriceCost of the goal specified using a dot (.) as the decimal operator.
properties.currencycurrencyCurrency using the three-letter code as per ISO 4217 standards.
properties.commentcommentSent as a query parameter.


Why can’t I add a Reverse ETL source from the destination page?

The Reverse ETL feature supports only source-driven pipeline configuration. It means that you must configure a Reverse ETL source in RudderStack and then connect it to a new or existing destination. Note that this destination should not be connected to any other source.

See Reverse ETL FAQ for more information.

Questions? Contact us by email or on Slack