Skip to main content

What this page covers

The Snowflake connector documented in this group is a source: it brings data into Zeotap CDP by connecting to a table in your Snowflake account and pulling it in on the sync frequency you choose when you create the source. To send data the other way — out of Zeotap CDP and into Snowflake — see the Snowflake destination. This page covers a connection error you can hit while setting up or running a Snowflake source, together with the ingestion specification — storage regions and PII handling — that applies to the data the source brings in. For the setup procedure itself, see Create a Snowflake Source and Load Data.

Data ingestion specification

Supported regions

Currently, Zeotap CDP supports data ingestion in the following regions:
  • EU — all EU countries’ data is ingested to the bucket provisioned for you in the EU region.
  • UK — United Kingdom data is ingested to the bucket provisioned for you in the UK region.
For the full list of country-to-region mappings, see Region of Storage.

Supported PII

For raw personal identifiers (PII), Zeotap CDP masks the PII information across the UI for all roles once you classify them in your organisation’s catalogue. Flagging the raw PII fields in your organisation’s catalogue is a critical step and is the responsibility of the organisation. The encrypted data is only available to the downstream systems for activation purposes.
Note:Zeotap CDP uses the RSA encryption algorithm.

Troubleshooting

Allow the blocked IP address in Snowflake

1
Contact your Snowflake Account Admin or Security Admin and give them the IP address displayed in the error message.
2
Ask them to include that IP address in the Allowed IP Addresses block.
3
If you are the only Account Admin or Security Admin user for the Snowflake account, reach out to Snowflake Support for assistance.
Note:To avoid this error, follow these recommendations:
  1. Designate at least two Account Admin or Security Admin users for your Snowflake account.
  2. Work with your network and security teams to check whether a CIDR block range can be provided in the Allowed IP Addresses list. This approach can help avoid issues with dynamic IP addresses.

Next steps

Last modified on September 24, 2026