Connect a Reverse ETL source to Lytics Bulk Upload

Configure a Reverse ETL source with your Lytics Bulk Upload destination.

This guide takes you through the steps to connect a Reverse ETL source to the Lytics Bulk Upload destination.

Set up connection

warning

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

Make sure you have set up a RETL source and connected it to your Lytics Bulk Upload destination before following the below steps.

  1. Confirm the connection settings for Lytics Bulk Upload destination and click Continue.

  2. In the Data Mapping section, specify the Sync mode. RudderStack supports syncing to this destination only via the Upsert mode.

  3. Select track event type to send the event data to downstream destinations.

info
RudderStack uses the BulkCSVUpload Lytics API endpoint to send track calls to Lytics.
  1. In Choose identifier, choose at least one user identifier from user_id and anonymous_id from the dropdown.

Refer Mapping configuration section for more information on above settings.

Next steps

FAQ

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