SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How Can I Send Reverse ETL (RETL) Data to Unsupported Destinations?

Question

How can I send data to a destination that is not supported by Reverse ETL(RETL)?

 

Product

Reverse ETL

 

Environment

Segment Console

 

Answer

Currently, Segment only supports integrations that are explicitly listed in the Reverse ETL destination catalog. If your desired destination is not available in the RETL catalog but exists in the standard Connections destination catalog, you can use the Segment Connections destination as a workaround.

By routing data from your warehouse into a standard Segment source first, you can forward it to any regular destination.

 

The Workaround Pipeline:

To bypass the RETL catalog limitation, construct your data pipeline using the following flow:

Reverse ETL Model ➔ Segment Connections Destination ➔ HTTP API Source ➔ Standard Destination (Not available in RETL catalog)

Have more questions? Submit a request
We can’t wait to see what you build.
Powered by Zendesk