Destinations Overview

A RudderStack destination is the target for your source event data. It is generally categorized into the following types:

• Event Stream destinations consume your event data to complement their offering related to marketing, analytics, CRM, etc.
• Warehouse destinations are data storage and processing platforms like Amazon Redshift, Snowflake, or Google BigQuery.
• Webhook destination forwards the SDK events to your configured webhook endpoint.

RudderStack currently supports integration with over 150 destinations. This section provides detailed documentation on setting up these destinations in RudderStack and the types of sources these can be set up with, to send your event data in no time.

Event Stream destinations

The below table lists the RudderStack-supported Event Stream destinations and different source types that you can use with them:

Warehouse destinations

The below table lists the RudderStack-supported warehouse destinations and different source types that you can use with them:

Destinations supporting only Reverse ETL sources

The below table lists the RudderStack-supported destinations which can be set up only with Reverse ETL sources:

Webhook destination

RudderStack supports the webhook destination which lets you send the events generated via RudderStack’s SDKs, Cloud Apps, and Reverse ETL sources:

To send events to a destination that RudderStack does not support currently, you can build a new integration for that destination by referring to the Contributor’s guides.

Questions? Contact us by email or on Slack