Data Quality user documentation
home/Integrations/Snowflake/Overview/Prerequisites

Prerequisites

Before you configure the Experian Data Quality app for Snowflake, make sure you have the required Snowflake privileges, Experian credentials, and access to the source data described below.

Snowflake access

You will need:

  • A Snowflake account with permissions to install and run Snowflake Native Apps with Streamlit.
  • A warehouse that can be selected when opening the app.
  • A role with permissions to install or administer the installed application.
  • Access to the app's APP_PUBLIC application role for users who need to open the app or call validation procedures.
  • A role such as ACCOUNTADMIN, or an equivalent custom role, to create security integrations, network rules, secrets, and external access integrations.

The app also requests these Snowflake privileges:

Privilege Why it is needed
CREATE EXTERNAL ACCESS INTEGRATION Allows the app to connect to Experian API endpoints.
EXECUTE TASK Allows the app to trigger the orchestration task for bulk jobs.
EXECUTE MANAGED TASK Allows the serverless background task to process queued jobs.

Experian access

You will need Experian OAuth client credentials for the validation services you want to use:

  • OAuth client ID
  • OAuth client secret
  • Entitlements for Experian Address Validation, Experian Email Validation, and/or Experian Phone Validation

If you do not already have credentials, contact your Experian representative or Contact Sales.

Network access

The setup process creates Snowflake objects that allow outbound HTTPS access to:

  • api.experianaperture.io
  • sso.experianaperture.io (using the OAuth token endpoint configured for the security integration)

Your Snowflake administrator must be able to create these objects in your account:

  • NETWORK RULE
  • SECURITY INTEGRATION
  • SECRET
  • EXTERNAL ACCESS INTEGRATION

Source data

For bulk validation, prepare a source table or view with:

  • One column containing the address, email address, or phone number to validate.
  • A stable unique ID column used to join results back to your source records.
  • Optional address country and dataset override columns if different rows need different address configuration.

Grant the installed application SELECT access to every source table or view used by a bulk job:

GRANT SELECT ON TABLE SOURCE_DB.SCHEMA.CONTACTS_TABLE TO APPLICATION EDQ;

Replace EDQ if the app was installed with a different application name.

Snowflake

Overview

Related resources