Docs navigation

Docs / Connectors

Connect Snowflake

Converise authenticates to Snowflake with key-pair auth: a dedicated user carrying a read-only role. The private key is encrypted at rest and never returned to the browser.

1. Set up key-pair authentication

  1. 1

    Generate an RSA key pair (PKCS#8)

    shell
    openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -out rsa_key.p8 -nocrypt
openssl rsa -in rsa_key.p8 -pubout -out rsa_key.pub
  2. 2

    Register the public key on a Snowflake user

    sql
    ALTER USER CONVERISE_READER SET RSA_PUBLIC_KEY = '<contents of rsa_key.pub without header/footer>';
  3. 3

    Grant read-only access

    Grant the user a read-only role (SELECT on your experiment data) and USAGE on an auto-resuming warehouse.

Table, schema, and column names are matched uppercase — as Snowflake stores unquoted identifiers. The account identifier is orgname-accountname (from Admin → Accounts).

2. Connect in Converise

  1. 1

    Open the connect form

    Go to Connectors and pick Snowflake from the catalog.

  2. 2

    Fill in the key-pair user

    Enter the Account identifier, User, the private key (PKCS#8 PEM, including the BEGIN/END lines), the Warehouse, and optionally a Role.

  3. 3

    Set up the data source and KPIs

    On the connector page point the Data source at the table (or view) that holds outcomes as database.schema.table — or paste your own SQL, or fill it from a preset (GA4 export on BigQuery). Pick the column roles from the live schema: subject, timestamp, variant, optionally the experiment key, event name and value columns; switch on a separate assignments table when your platform stores exposures apart from outcomes. Then list the KPIs — an event name or a column that counts, reduced per subject as a conversion (count), a quantity (sum) or revenue (sum). Set once; every experiment on this connector binds in three clicks.

  4. 4

    Schedule per experiment, not here

    There is nothing to schedule on the connector. When you bind an experiment, choose whether it refreshes automatically once a day (off by default — each run bills warehouse queries) and at which UTC hour, ideally after your warehouse ETL completes.

  5. 5

    Check the connection and save

    Click Check connection to run a test query, then save. When editing later, leave the credential fields blank to keep the stored key.

Next step

Bind an experiment to the connector on its Data sources tab — see Binding evidence.

PreviousDatabricksNextBinding evidence