The Snowflake integration allows Email Meter to push enriched email analytics data directly to your own Snowflake instance. This enables you to combine your email statistics with other business data in your data warehouse.
The Snowflake integration transfers data to a database that you own and control. This gives you full ownership of the data and the flexibility to transform, combine, and query it alongside your other datasets.
Email Meter handles the data synchronization process, ensuring your Snowflake instance receives regular updates with the latest email metrics and analytics.
Requirements
Before you can set up the Snowflake integration, please make sure that you meet the requirements below:- A Snowflake account with administrative access
- A dedicated database for Email Meter data
- A Snowflake user with permissions to create schemas in the target database
- A Snowflake warehouse for data loading operations
Instructions
To set up the integration, you’ll need to create a dedicated user and configure the appropriate permissions in your Snowflake account. Follow these steps:Create a database
Log in to your Snowflake account and create a dedicated database for Email Meter data:You can customize the database name according to your naming conventions.
Create a warehouse
Create a warehouse that will be used for data loading operations:The warehouse size can be adjusted based on your data volume. An X-Small warehouse is typically sufficient for most use cases.
Generate a key pair
Generate a private and public key pair for authentication. Run these commands in your terminal:You will be prompted to create a passphrase for the private key. Make sure to save this passphrase securely.
Assign the public key to the user
Extract the public key value (without the header/footer lines) and assign it to the user:
The public key value is the content of the
.pub file without the -----BEGIN PUBLIC KEY----- and -----END PUBLIC KEY----- lines.Share credentials with Email Meter
Once the previous steps are completed, please share the following information with your Project Manager or Business Intelligence Consultant:
- Host: Your Snowflake host URL (e.g.,
xy12345.us-east-1.aws.snowflakecomputing.com) - Role: The role name (e.g.,
EMAILMETER_ROLE) - Warehouse: The warehouse name (e.g.,
EMAILMETER_WH) - Database: The database name (e.g.,
EMAILMETER) - Username: The user name (e.g.,
EMAILMETER_USER) - Private key: The private key file (
snowflake_emailmeter_key.p8) - Private key passphrase: The passphrase used to encrypt the private key
You can find your Snowflake host URL in your browser’s address bar when logged into Snowflake. It follows the format
account-identifier.region.cloud.snowflakecomputing.com (e.g., xy12345.us-east-1.aws.snowflakecomputing.com).Integrate Snowflake with other tools
Once your email analytics data is in Snowflake, you can easily connect it to your favorite Business Intelligence tools. Here are some popular integrations:Frequently asked questions
How often is the data synchronized?
How often is the data synchronized?
Data synchronization frequency depends on your specific requirements. We typically offer daily synchronization, but more frequent updates can be configured based on your needs. Please discuss your requirements with your Business Intelligence Consultant.
What Snowflake regions are supported?
What Snowflake regions are supported?
We support all Snowflake cloud regions across AWS, Azure, and Google Cloud. Your data will be transferred to whichever region hosts your Snowflake account.
Can I use an existing database instead of creating a new one?
Can I use an existing database instead of creating a new one?
Yes, you can use an existing database. Just make sure the dedicated role has the appropriate permissions to create schemas in the target database.
Where can I find the data schema?
Where can I find the data schema?
As our email analytics product is customized to your needs, each client’s schema might be a bit different. Please get in touch with your Business Intelligence Consultant to request your own schema documentation.
Why do you use key pair authentication?
Why do you use key pair authentication?
Key pair authentication provides enhanced security compared to username/password authentication. It uses RSA key pairs, which are more resistant to brute-force attacks and don’t require storing passwords. This is the industry-recommended approach for production environments and automated integrations.