# Load Snowplow data to Snowflake
> Send Snowplow data to Snowflake for analytics and data warehousing with automatic table management, schema evolution, and efficient data loading via Snowpipe or batch.
> Source: https://docs.snowplow.io/docs/destinations/warehouses-lakes/snowflake/
> Documentation index: https://docs.snowplow.io/llms.txt

[Snowplow supported](/docs/destinations/#destinations-catalog "Built and supported by Snowplow") · Warehouse or lake loader · Streaming · Batch · AWS, Azure, GCP

> **Info: Cloud availability**
>
> The Snowflake integration is available for Snowplow pipelines running on **AWS**, **Azure** and **GCP**.

The Snowplow Snowflake integration allows you to load enriched event data (as well as [failed events](/docs/fundamentals/failed-events/)) directly into your Snowflake warehouse for analytics, data modeling, and more.

## What you will need

Connecting to a destination always involves configuring cloud resources and granting permissions. It's a good idea to make sure you have sufficient priviliges before you begin the setup process.

> **Tip:** The list below is just a heads up. The Snowplow Console will guide you through the exact steps to set up the integration.

Keep in mind that you will need to be able to:

- Provide your Snowflake account locator URL, cloud provider and region

- Allow-list Snowplow IP addresses

- Generate a key pair for key-based authentication

- Specify the desired database and schema names, as well as a warehouse name

- Create a role with the following permissions:

  - `USAGE`, `OPERATE` on warehouse (for testing the connection and monitoring, e.g. as part of the [Data Quality Dashboard](/docs/monitoring/#data-quality-dashboard))
  - `USAGE` on database
  - `ALL` privileges on the target schema

## Getting started

You can add a Snowflake destination through the Snowplow Console. (For self-hosted customers, please refer to the [Loader API reference](/docs/api-reference/loaders-storage-targets/snowflake-streaming-loader/) instead.)

### Step 1: Create a connection

1. In Console, navigate to **Settings** > **Connections**
2. Select **Set up connection**
3. Choose **Event loading**, then **Snowflake**
4. Follow the steps to provide all the necessary values
5. Click **Complete setup** to create the connection

### Step 2: Create a loader

1. In Console, navigate to **Destinations** > **Warehouses and lakes**. Click **Add destination** and select **Snowflake**
2. **Select a pipeline**: choose the pipeline where you want to deploy the loader.
3. **Select your connection**: choose the connection you configured in step 1.
4. **Select the type of events**: enriched events or failed events
5. Click **Continue** to deploy the loader

You can review active destinations and loaders by navigating to **Destinations** > **Warehouses and lakes**.

## How loading works

The Snowplow data loading process is engineered for large volumes of data. In addition, our loader applications ensure the best representation of Snowplow events. That includes automatically adjusting the tables to account for your custom data, whether it's new event types or new fields.

For more details on the loading flow, see the [Snowflake Streaming Loader](/docs/api-reference/loaders-storage-targets/snowflake-streaming-loader/) reference page, where you will find additional information and diagrams.

## Snowplow data format in Snowflake

All events are loaded into a single table (`events`).

There are dedicated columns for [atomic fields](/docs/fundamentals/canonical-event/), such as `app_id`, `user_id` and so on:

| app\_id | collector\_tstamp       | ... | event\_id                            | ... | user\_id                             | ... |
| ------- | ----------------------- | --- | ------------------------------------ | --- | ------------------------------------ | --- |
| website | 2025-05-06 12:30:05.123 | ... | c6ef3124-b53a-4b13-a233-0088f79dcbcb | ... | c94f860b-1266-4dad-ae57-3a36a414a521 | ... |

Snowplow data also includes customizable [self-describing events](/docs/fundamentals/events/#self-describing-events) and [entities](/docs/fundamentals/entities/). These use [schemas](/docs/fundamentals/schemas/) to define which fields should be present, and of what type (e.g. string, number).

For self-describing events and entities, there are additional columns, like so:

| app\_id | ... | unstruct\_event\_com\_acme\_button\_press\_1                      | contexts\_com\_acme\_product\_1                                |
| ------- | --- | ----------------------------------------------------------------- | -------------------------------------------------------------- |
| website | ... | data for your custom `button_press` event (as a `VARIANT` object) | data for your custom `product` entities (as a `VARIANT` array) |

Note:

- "unstruct\[ured] event" and "context" are the legacy terms for self-describing events and entities, respectively
- the `_1` suffix represents the major version of the schema (e.g. `1-x-y`)

You can learn more [in the API reference section](/docs/api-reference/loaders-storage-targets/schemas-in-warehouse/).

> **Tip:** Check this [guide on querying](/docs/destinations/warehouses-lakes/querying-data/?warehouse=snowflake) Snowplow data.
