Skip to main content
The Snowflake integration writes 3RD’s Export API datasets into a schema in your own Snowflake account and refreshes them every day. Your data team can join AI-visibility data with web analytics, CRM and paid-media data in SQL, dbt or any BI tool that reads Snowflake. It runs on the same data as the Export API, so the numbers match the API and the 3RD dashboard.
The managed sync is available on plans that include the Export API. If you would rather run the load yourself, see Load it yourself with the Export API.

What you need

  • A Snowflake user with ACCOUNTADMIN, or with SECURITYADMIN and SYSADMIN, to run the setup script once.
  • Your Snowflake account identifier in the form ORGNAME-ACCOUNTNAME. Find it in Snowsight under your account menu → Account → View account details.
  • The owner or admin role in your 3RD organization.

Set it up

1

Start the connection in 3RD

Go to Brand → Integrations, and under Reporting open Snowflake. Click Connect. Enter your account identifier. The user, role, warehouse, database and schema names are filled in with defaults; change them if your naming rules require it.
2

Run the setup script in Snowflake

3RD shows a setup script with a public key filled in. Copy it into a Snowflake worksheet and run it. It creates a dedicated role, warehouse, schema and service user for 3RD:
3

Test the connection

Back in 3RD, click Test connection. If it fails, the message tells you which step to fix. See Troubleshooting.
4

Choose brands and datasets

When the test passes, 3RD starts loading your history. Under What to sync, untick any tables or brands you don’t want. 3RD then refreshes every day.
5

Give your team read access

The sync role can only write to its own schema. Grant read access to the roles your analysts use:
The person who uses 3RD is often not the person who administers Snowflake. Send the setup script to your data team; nothing in it is secret, because the private key never leaves 3RD.

Security

  • No password. 3RD signs in with key-pair authentication. It generates the key pair, keeps the private key encrypted, and shows you only the public key.
  • Least privilege. The role can use one warehouse and create tables in one schema. It cannot read anything else in your account.
  • Write-only. 3RD never reads your data. It writes and replaces only the tables it created.
  • Your compute. The sync runs on the XSMALL warehouse you created, which suspends after a minute idle. A daily run takes seconds.
If your account uses a network policy, 3RD can’t reach it yet: 3RD has no fixed IP addresses to add to the policy. Contact support before you connect.

Tables

Each dataset becomes one table in your schema. Column names are the Export API field names in upper case; see the Export API reference for what each field means. Every dated table also has BRAND_ID, which joins to BRANDS.ID, and _SYNCED_AT, the time the row was written.

How the sync works

  • Daily refresh. Each run reloads the last 7 days, because AI answers for recent days can still arrive. Older days don’t change.
  • Atomic. 3RD loads new rows into a staging table, then replaces the days it reloaded in one transaction. A failed run leaves your tables as they were.
  • History. The first sync goes back as far as your plan’s Export API history allows, up to two years. See Pagination and history.
  • New columns. When 3RD adds a field to the Export API, the column is added to your table. Existing columns are never renamed or dropped.
  • Sync now. Click Sync now in settings to run a sync outside the daily schedule, or Reload history to load your whole history again.
Check freshness from Snowflake:

Example query

Weekly visibility per AI model for one brand:
Sum the counts and divide, rather than averaging VISIBILITY_RATE: a day with more answers should weigh more.

Manage the connection

  • Rotate key. In settings, click Rotate key. 3RD shows an ALTER USER … SET RSA_PUBLIC_KEY_2 = '…' statement (or RSA_PUBLIC_KEY, whichever slot is free). Run it, then click Confirm new key. Once the new key signs in, 3RD switches to it and shows the statement that removes the old one.
  • Disconnect. Click Disconnect. 3RD deletes its private key and stops syncing. Your tables stay. To remove the user, run DROP USER THIRD_SYNC_USER;.
  • Plan changes. If your plan no longer includes the Export API, syncing stops and your tables stay as they were.

Troubleshooting

The Snowflake settings page in 3RD shows the latest error. After 14 days of failed syncs, 3RD stops syncing until you click Sync now.

Load it yourself with the Export API

If you prefer to run the load inside Snowflake, call the Export API from a Snowpark stored procedure. You need an Export API key; see Authentication.
1

Allow Snowflake to call 3RD

2

Create the table and the procedure

This example loads /visibility. Use the same pattern for the other endpoints, with the columns from the Export API reference.
3

Schedule it

Get your brand ids from /api/export/v1/brands, load your history once, then schedule a daily refresh of the last 7 days: