Export Amplitude Data to Snowflake

Load your Amplitude event data into your Snowflake account. You can set up recurring syncs through the Amplitude UI, as well as manually start a sync of your historical data.

Considerations¶

Depending on your company's network policy, you may need add these IP addresses to your allowlist in order for Amplitude's servers to access your Snowflake instance:

• 52.33.3.219
• 35.162.216.242
• 52.27.10.221

Limits¶

• Maximum running time for a single Snowflake SQL query is 12 hours.

Set up a recurring data export to Snowflake¶

Creating a recurring data export is a simple, three-step process you can handle yourself. Each sync completes within five to ten minutes, though often it's much closer to real time. This method also lets you watch jobs.

To set up a recurring export of your Amplitude data to Snowflake, follow these steps:

1. In Amplitude Data, click Catalog and select the Destinations tab.
2. In the Warehouse Destinations section, click Snowflake.
3. Under Export Data to Snowflake, choose which data you'd like to include in this export: Export events ingested today and moving forward, Export all merged Amplitude IDs, or export both.
4. Review the Event table and Merge IDs table schemas and click Next.

5. In the Snowflake Credentials For Amplitude section, enter the following information:

   • Account Name: This is the account name on your Snowflake account. It's the first part of your Snowflake URL, before 'snowflakecomputing.com'.
   • Warehouse: The warehouse Amplitude uses to load the data. Ideally, this should be a warehouse dedicated to loading Amplitude data to prevent other Snowflake operations aren't disrupted.
   • Database: The database where the data should be stored. Dedicate this database specifically to Amplitude data.
   • Username: The username Amplitude uses to connect to the Snowflake account.
   • Password: The password associate with the username.
   • Role: The role that the connection will use to write this data. The default value of role is AMPLITUDE only.

   Warning

   These credentials are case-sensitive, so keep that in mind.

6. Click Next. Amplitude attempts to upload test data using the credentials you entered. If the upload is successful, click Finish.

All future events are automatically sent to Snowflake.

From here, Amplitude generates micro-batch files at five-minute intervals and loads them to customer-owned Snowflake accounts directly every 10 minutes. You are able to see the data in your Snowflake accounts within 20 minutes after Amplitude receives the events.

Export historical Amplitude data to Snowflake¶

To export your historical data from Amplitude into Snowflake, navigate to the integration, then click Export Data and select a date range.

This process can take anywhere from a single day to several weeks. It depends on your data volume, warehouse size, cluster count, network bandwidth, and number of concurrent historical data exports you currently have, among other factors.

Reduce your Snowflake computation costs¶

If you are looking to reduce the Snowflake computation costs when receiving data from Amplitude, try these methods:

• Modify warehouse size and number of clusters. For shorter export cadences (15 to 30 minutes), try starting with xsmall or small. Then upgrade as needed.
• When backfilling data into Snowflake, start with a small warehouse and upgrade as needed.
• You can also try reducing the auto suspend time to 60s. This option might not be available within the Snowflake UI, but can be manually set via direct Snowflake query.

Snowflake export format¶

Event table schema¶

The Event table schema includes the following columns:

Merged User table schema¶

The Merged User table schema contains the following:

Still have questions? Ask them in the Community.