Provision your Reltio tenant for the Reltio Data Pipeline for Snowflake (GCP)
Learn how to provision the Reltio Data Pipeline for Snowflake on your Reltio tenant.
You'll need to gather this information:
- Bucket Name
- Customer GCP project
- Reltio tenant ID
- Reltio tenant environment name
Gather the information mentioned in the table below and submit a support case to Reltio to configure your tenant for the Reltio Data Pipeline for Snowflake.
Note: Parameters marked with an asterisk (*) are mandatory.
| Parameter | Possible values | Recommended values | Description |
|---|---|---|---|
| Cloud provider* | GCP | GCP | The cloud platform that hosts the external staging storage used by Snowflake. |
| Upload service account key file* | Any valid GCP service account key file (.json) | Upload the dedicated service account key file created for Reltio Data Pipeline | The JSON key file for the GCP service account that provides access to the staging bucket. The service account must have sufficient permissions for read, write, and storage operations. |
| Project name | Any valid GCP project name | Use the project created for Snowflake staging integration | The GCP project name associated with your staging bucket. |
| Bucket name | Any valid Cloud Storage bucket name | A dedicated bucket created specifically for Reltio Data Pipeline | The name of the GCP Cloud Storage bucket that serves as the external staging area for Snowflake. |
| Staging bucket region | Any valid GCP region (for example, us-central1, europe-west1) | us-central1 (default) | The region where the Cloud Storage bucket is hosted. Specify this only if the bucket region is outside the US. |
| Attribute format | STANDARD, EXTENDED | STANDARD | Defines the format in which attribute values are exported from Reltio. |
| Transmit OV values only | Yes / No | Yes, if only operational data is required | When set to Yes, exports only operational values (OVs) to the Cloud Storage staging bucket. |
| Data filtering | Yes / No | Yes, if attribute filters are defined | When set to Yes, enables attribute-level filtering for data exported to Snowflake. Filtering conditions must be configured separately. |
| Serialize initial sources in crosswalks | Yes / No | No, unless data lineage tracking is required | When set to Yes, sends the initial source information for each crosswalk record to the staging bucket. |
Note: By default, the data pipeline exports entities, relationships, interactions, matches, and merges to your Snowflake account. If you wish to export Activity logs or Workflow data, mention that explicitly in your Support case. After the Support case is completed, you must run the Create Snowflake Objects for Activity logs export using the Scripts API in your Snowflake account to enable export of Activity logs.