What this is
Snowflake is a Zeotap CDP destination: data flows out of Zeotap CDP and into your Snowflake account. To move data the other way — importing data that already lives in Snowflake into Zeotap CDP — see the Snowflake source. Snowflake is a cloud-based data warehousing platform designed for scalable data storage, processing, and analytics. It is known for its flexibility, performance, and ease of use in handling large volumes of structured and semi-structured data. Integrated with Zeotap CDP, it allows you to send batched and real-time data based on the audiences (segments) and workflows created in Zeotap CDP. Delivery runs in two hops. You establish a connection between your Google Cloud Storage (GCS) bucket and your Snowflake account. Zeotap CDP pushes data to your GCS bucket, where you can set up automation to receive data either in batches at fixed intervals or in real time by configuring a Pub/Sub notification for the bucket.Audiences and Segments refer to the same thing throughout the Zeotap CDP UI — a group of customer profiles that match a set of criteria you define.
Prerequisites
Before you begin with the integration, ensure you have the following:
- A Google Cloud Storage bucket for storing your data files.
- A Pub/Sub topic to enable notifications for automating data loading.
- A Snowflake account, together with the database, schema, and table where the data should land.
Supported identifiers and actions
Use this integration to send any number of identifiers and attributes to Snowflake. However, sending event attributes when transferring data from audiences to Snowflake is not supported.
With Stream data to Snowflake, you enable batching in the action to aggregate real-time data before sending it to Snowflake. Batching occurs based on two factors: Batch duration and Record count, whichever is met first. For example, if you set the batch duration to 2 minutes and the Record Count to 100, then the file is generated and sent when either condition is met.
How the integration works
This architecture illustrates the integration of Snowflake with Zeotap CDP Infrastructure.
Storage integration
Storage Integration is a feature in Snowflake that securely connects Snowflake with external cloud storage systems, such as Google Cloud Storage (GCS). This integration enables Snowflake to access and interact with external storage securely and efficiently. Permissions required for theSTORAGE_GCP_SERVICE_ACCOUNT:
- Storage Object User
- Storage Insights Collector Service
Notification integration
Notification Integration enables Snowflake to automatically detect and respond to new data in external storage for auto-ingest scenarios like Snowpipe. This integration works by sending notifications (for example, through Pub/Sub) when new data is available, triggering the data loading process. Without this integration, Snowflake would rely on manual processes or continuous pulling, which is less efficient. Permissions required for theGCP_PUBSUB_SERVICE_ACCOUNT:
- Pub/Sub Subscriber
- Monitoring Viewer
The bucket-side and Pub/Sub-side grants are covered in Connect Snowflake to your Google Cloud Storage bucket.
Connect Snowflake to your Google Cloud Storage bucket
An integration in Snowflake securely connects Snowflake to external cloud storage, such as Google Cloud Storage (GCS). Snowflake creates a service account for the integration, which you use to grant access to your GCS bucket. This service account acts as a secure link between Snowflake and GCS. Complete the following sections in order before you create the destination in Zeotap CDP.Run the SQL commands in a Snowflake worksheet
Every Snowflake command in this procedure runs in a SQL worksheet in the Snowflake console.1
In the Snowflake console, navigate to Projects > Worksheets.
2
Click create New SQL worksheet.

3
Choose the Database and Schema where you want to send the data, as shown below.

4
Enter the command you want to run and click the Run button. In this example, the provided command is used to create the storage integration.

Create a storage integration in Snowflake
To connect Snowflake to your GCS bucket, create a storage integration object. This defines the connection and permissions. Run the following command in the Snowflake SQL worksheet to create the storage integration:- Replace
<INTEGRATION_NAME>with a name for your integration (for example,my_gcs_integration). - Replace
<YOUR_BUCKET_NAME>with the name of your GCS bucket.

Note the
STORAGE_GCP_SERVICE_ACCOUNT value, which is the service account Snowflake created for the integration. You need this to grant permissions to the bucket, as described in Grant the storage service account access to the bucket.Grant the storage service account access to the bucket
The GCS bucket resides at your end, so you need to grant access to the Snowflake service account created in the previous section (STORAGE_GCP_SERVICE_ACCOUNT). To do so, perform the following steps:
1
Open the Google Cloud Console.
2
In the left panel, navigate to your Cloud Storage > Buckets.
3
Select your GCS bucket and go to the PERMISSIONS tab.
4
Under VIEW BY PRINCIPALS, click GRANT ACCESS.
5
Under Add principals, add the service account (
STORAGE_GCP_SERVICE_ACCOUNT) as a new principal, select the custom role you have created, and assign the following roles to it:storage.buckets.getstorage.objects.updatestorage.objects.getstorage.objects.liststorage.objects.deletestorage.objects.restore
For information about how to create a custom role in the Google Cloud Console, see the Google Cloud documentation.

6
Click Save.
Create a Pub/Sub notification for the bucket
Notification Integration enables Snowflake to detect when new data arrives in GCS. So, configure a notification connection between the GCS bucket and a Pub/Sub topic. Run the following command in the Google Cloud Console shell:- Replace
<TOPIC>with the Pub/Sub topic name. - Replace
<BUCKET-NAME>with the name of your GCS bucket.
Create a notification integration in Snowflake
To automate the process, set up notifications using Pub/Sub. Run the following command in the Snowflake SQL worksheet:- Replace
<INTEGRATION_NAME>with a name for the integration (for example,my_notification_integration). - Replace
<SUBSCRIPTION_ID>with the ID copied in Create a Pub/Sub notification for the bucket.
Note the
GCP_PUBSUB_SERVICE_ACCOUNT value, which is the service account created for the Notification integration. You need to grant permissions to the Pub/Sub subscription, as described in the next two sections.Grant the Pub/Sub service account access to the subscription
Snowflake needs to be notified when new data arrives in GCS. Hence, grant the Snowflake service account (GCP_PUBSUB_SERVICE_ACCOUNT) access to your Pub/Sub subscription:
1
Open the Google Cloud Console and search for Pub/Sub.
2
Select Pub/Sub Subscriptions.

3
Select the subscription you created for the bucket notification.
4
Click the three dots on the subscription and click View Permissions > Add Principal.
5
Add the role Pub/Sub Subscriber and click Save.

Grant monitoring access to the Pub/Sub service account
Grant the Snowflake service account (GCP_PUBSUB_SERVICE_ACCOUNT) monitoring viewer access:
1
Open the Google Cloud Console.
2
In the left panel, navigate to IAM & Admin > IAM.
3
Under VIEW PRINCIPALS, click GRANT ACCESS.
4
Assign the following role to the Snowflake service account:
Monitoring Viewer

Create a stage in Snowflake
Create a stage referencing the GCS bucket. Run the following command in the Snowflake SQL worksheet:- Replace
<STAGE_NAME>with the stage name. - Replace
<BUCKET-NAME>with your GCS bucket name. - Replace
<STORAGE_INTEGRATION_NAME>with the storage integration name you created earlier.
Create a Snowpipe
Create a Snowpipe to load data from the GCS bucket into Snowflake automatically. Run the following command in the Snowflake SQL worksheet:- Replace
<PIPE_NAME>with the pipe name. - Replace
<NOTIFICATION_NAME>with the notification integration name you created earlier. - Replace
<TABLE_NAME>with the destination table name. - Replace
<STAGE_NAME>with the stage name you created earlier. - Replace
<FOLDER>with the folder name for the data.
Understand the destination components
Ensure that you have the details of the following Google Cloud Storage components before creating the destination in Zeotap CDP.-
Bucket — the name of your Google Cloud Storage bucket. You can obtain this information from your Google Cloud Storage account as shown in the image below.

-
Folder — a logical container for organising stored objects within a bucket. In reality, there are no actual folders in Google Cloud Storage. Instead, the folder concept is emulated by employing object key names containing slashes (”/”) to replicate a hierarchical arrangement. You can obtain this information from your Google Cloud Storage account as shown in the image below.

- Account — the Zeotap Service Account used to access the Google Cloud Storage account. Ensure that you whitelist the Zeotap Service Account to successfully push audiences (segments) from Zeotap CDP to Google Cloud Storage.
Create the Snowflake destination in Zeotap CDP
Perform the following steps to create a destination for Snowflake:1
Open the Destinations application
Log into the Zeotap CDP App and go to the DESTINATIONS application.
2
Start a new destination
Click + Create Destination..png?fit=max&auto=format&n=UNwlFBI6l-jpipWP&q=85&s=562fa59a1a1e2b76442fa98f6e6f991e)
.png?fit=max&auto=format&n=UNwlFBI6l-jpipWP&q=85&s=562fa59a1a1e2b76442fa98f6e6f991e)
3
Select Snowflake
Under the All Destinations section, search for Snowflake and click it..png?fit=max&auto=format&n=UNwlFBI6l-jpipWP&q=85&s=653728565c7ed5863548171765d4086f)
.png?fit=max&auto=format&n=UNwlFBI6l-jpipWP&q=85&s=653728565c7ed5863548171765d4086f)
4
Fill in the destination fields
A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen you find the list of fields required for the integration to be established. Provide the required details:a. Enter a name for the destination.b. In the Destination Instance Name field, provide a desired value for this internal field.c. In the Bucket field, provide the name of the Google Cloud Storage bucket.d. In the Folder field, provide the folder path in your storage location where Zeotap CDP can store your exported data.e. Under Account, choose either Zeotap Service Account or Client Service Account Json using the drop-down menu based on the type of authentication you need. If you wish to use the Zeotap Service Account, then ensure that you whitelist it to send audiences (segments) from Zeotap CDP to Snowflake.
Ensure you follow the below points while providing the folder path:
- The folder path should follow the below structure:
folder_name/sub_folder_name/
- The folder name should not start with a
/ - The folder name and sub-folder name should end with a
/

-
If you choose Zeotap Service Account as the Account, then ensure that you whitelist the service account provided by Zeotap CDP to send the audiences (segments) from Zeotap CDP to Snowflake. This service account information auto-populates under Service Account to be Whitelisted as shown in the image below.

-
If you choose Client Service Account Json as the Account, then you need to upload the JSON file with the required authentication information using the + Select File option so that Zeotap CDP can push the audiences to the Google Cloud Storage platform.

5
Choose the action and map fields
In the new screen that appears, choose the appropriate action and mapping. Under Choose your Action, choose either Send data to Snowflake or Stream data to Snowflake, depending on whether you want to use Audiences (batched data activation) or Journeys (real-time activation).a. If you choose Send data to Snowflake as your action, then you can send any attributes and identifiers to Snowflake and link it to any Audience created.b. If you choose Stream data to Snowflake as your action, then you can send any attributes and identifiers to Snowflake and link it to any workflow created in Journeys.Use the Enable Batching checkbox to aggregate data before sending it to Snowflake through the workflow. Batching occurs based on two factors: processing time and record count, whichever occurs first. For example, if you set the batch processing time to 2 minutes and the record count limit to 100, then the file is generated and sent to Snowflake when either condition is met.

6
Create the destination
After finalising the attributes and identifiers to send, click Create Destination.
Link an audience or a workflow to the destination
The created destination gets listed in the Audiences and Journeys applications, which can be linked to an audience or a workflow as per your requirement.- For batched activation with the Send data to Snowflake action, see Link the destination.
- For real-time activation with the Stream data to Snowflake action, see Create a workflow.
Verify the data lands in Snowflake
After linking an audience or a Journeys workflow to the destination, Zeotap CDP sends the data to your Google Cloud Storage bucket. Snowflake then pulls the data from the bucket into your Snowflake account. In Snowflake, the data appears in theDatabase/Schema/Table you selected for data transfer, as shown below.

Next steps
- Explore the Snowflake source → — import data from Snowflake into Zeotap CDP
- Explore linking an audience to the destination → — activate an audience against the destination you just created
- Explore creating a Journeys workflow → — send real-time data through the destination
- Explore how destinations work → — actions, mappings, and delivery across all destinations