Reverse ETL / activation

Reverse ETL moves data in the opposite direction to the usual flow. Normally, data travels from your apps into a central data warehouse for reporting. With reverse ETL, the results of that analysis travel back out into the tools your team uses every day. For example, a warehouse might calculate which customers have not logged in for 30 days, and reverse ETL pushes that list into your email tool so a win-back campaign can target them. Heap, RudderStack, Segment and Spectacle are tools in the library that list this feature.

Teams often do their best analysis in a warehouse, then struggle to act on it because sales and marketing tools cannot see the results. Reverse ETL closes that gap without manual CSV exports. You need it when you already keep customer data in a warehouse and want audiences, scores or segments to show up inside other tools. You do not need it when your data lives in one or two apps that already share information directly, or when you have no warehouse at all.

• Which destination tools are supported, and can you add your own through an API or webhook.
• How often the sync runs, and whether it updates only changed records or resends everything.
• What happens to a record that fails to sync, and whether you are alerted.
• Whether the people who use the destination tools can set up syncs, or only someone technical.