Sources Overview

The event data originates via a source in RudderStack. The most common event sources are your apps and web properties, but can include third-party cloud apps, server integrations, and even your own data warehouse.

The following sections provide more detail on the available source types, with links to the setup guides for each source.

If you’re new to RudderStack, going through the Quickstart guide to create your first source is recommended.

Event Streams

RudderStack’s Event Streams feature lets you collect event data from all your sites and applications and route it to a wide array of customer tools and data warehouses.

SDKs

RudderStack provides open source SDKs for web, mobile, and server applications:

Web

Track customer event data from your website and web apps and send it to the specified destinations:

Mobile

Use native mobile SDKs for the mobile operating systems and development frameworks:

Server

Use server-side SDKs to track event data from your backend applications and send it to the specified destinations:

Cloud Apps

RudderStack lets you ingest event data from your cloud apps and route it to the desired destinations.

Reverse ETL

With RudderStack’s Reverse ETL capabilities, you can use your data warehouse as a data source. You can tap into your warehouse data and enrich data pipelines elsewhere in your stack, for enhanced customization, personalization, and targeting.

API

It is recommended to use a native SDK for tracking and routing user events from your sources. RudderStack’s SDKs offer automatic tagging of user context, event batching, and retry functionality during delivery failure.

If you don’t see a supported SDK or library for your environment, you can send your data directly to the RudderStack HTTP API.

Questions? Contact us by email or on Slack