Reverse ETL FAQ
Get answers to some frequently asked Reverse ETL questions.
It's expected that when you select Updated records, the records do not change after the first sync. During the first sync, the reverse ETL system calculates a snapshot of all the results and creates records in the _segment_reverse_etl schema. All the records are considered as Added records instead of Updated records at this time. The records can only meet the Updated records condition when the underlying values change after the first sync completes.
Yes, you can sign up for Reverse ETL sync notifications for failed or partially successful syncs. Segment sends notifications for every sync failure.
To receive Reverse ETL sync notifications:
- From your workspace's homepage, navigate to the Monitor tab and select Alerts.
- On the Default tab, select Reverse ETL.
- Identify the event you'd like to be alerted for and select the menu icon under the Actions tab.
- Click Enable alert and select the notification channels for which you'd like to receive alerts.
- Click Save.
For more information about Reverse ETL alerting, refer to the Monitor documentation.
Segment uses the gosnowflake library to connect with Snowflake, which internally uses TLS for the HTTP transport.
No. In Reverse ETL, Segment executes queries in a common table expression, which can only bind the results from one single subquery. If there are multiple semicolons ; in the query, they'll be treated as several subqueries (even if the second part is only an inline comment) and cause syntax errors.
Functions aren't supported by Reverse ETL. As a workaround, instead of using the Segment Connections integration, use the Webhook (Actions) integration behind your Reverse ETL extraction. With that in place, you can send data to Source Functions. You can write the code in that function to do the work you had wanted to do in the Insert Function. From there, the data your code allows to move on, flows into a Segment source just like it would if you were using Segment Connections.