> ## Documentation Index
> Fetch the complete documentation index at: https://learn.kubit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect RudderStack

> Send RudderStack events to Kubit through a Snowflake destination, or connect the warehouse where RudderStack already loads them.

Kubit reads RudderStack events in one of two ways: RudderStack loads them into a Kubit Snowflake account through its Snowflake destination, or Kubit queries the warehouse where RudderStack already loads them.

## Choose a path

| Path | Use it when | Where events end up |
| - | - | - |
| **Snowflake destination** | You don't load RudderStack events into a warehouse yet | A Kubit-hosted Snowflake account |
| **Connect your warehouse** | RudderStack already loads event tables into your Snowflake, BigQuery, Databricks or ClickHouse | Your warehouse. Kubit queries the tables in place. |

## Snowflake destination

Use RudderStack's Snowflake destination to forward all events to a Kubit Snowflake account.

### 1. Get Snowflake credentials from Kubit

Kubit provides the Snowflake credentials for the destination.

### 2. Add the destination

Follow RudderStack's [Snowflake destination setup steps](https://www.rudderstack.com/docs/destinations/warehouse-destinations/snowflake/#configuring-snowflake-destination-in-rudderstack) with the credentials from Kubit.

### 3. Wait for the first sync

RudderStack loads data from the moment the destination is enabled. It uses its [warehouse schema](https://www.rudderstack.com/docs/destinations/warehouse-destinations/warehouse-schema/): one table per `track` event, plus aggregate `tracks`, `pages`, `screens` and `identifies` tables.

### Historical data

The destination only loads events from the moment it's enabled. To load older events, use RudderStack's [Event Replay](https://www.rudderstack.com/docs/user-guides/administrators-guide/event-replay/). Event Replay requires contacting RudderStack's Customer Success team.

## Connect your warehouse

If RudderStack already loads your events into a warehouse, and you've modeled them, connect that warehouse instead of adding a destination.

| Benefit | Why |
| - | - |
| One source of truth | Your warehouse stays the single source of truth, so you can always reconcile your metrics |
| No replay | You don't need to coordinate an event replay with RudderStack |

Follow the page for your warehouse under [Bring your own warehouse](https://learn.kubit.ai/warehouses/overview.md). For RudderStack's ClickHouse destination, [RudderStack events on ClickHouse](https://learn.kubit.ai/product-analytics/cookbook/rudderstack-clickhouse.md) walks through the grants, views and model end to end.

## Next steps

* [Bring your own warehouse](https://learn.kubit.ai/warehouses/overview.md): connect the warehouse that already holds your events.
* [Reports overview](https://learn.kubit.ai/product-analytics/reports/overview.md): build your first report on the events.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.