Skip to main content
Export your referral intelligence to a table in your own Google BigQuery. After every enrichment job, Clustr upserts new and updated opportunities into the table, keeping your warehouse and BI tools current. It is a data export, not an OAuth app. You connect with a Google service-account key, and Clustr only ever writes to the one table it manages.
Connecting BigQuery is admin-only, under Integrations, Apps, BigQuery in the dashboard.

Connect BigQuery

Create a service account in Google Cloud, then run the three-step wizard.
1

Paste your service-account key

In Google Cloud, create a service account, grant it BigQuery Data Editor and BigQuery Job User, and download its JSON key (Service Accounts, Keys, Add key, JSON). Paste the whole JSON into Clustr and click Continue. Clustr reads the project from the key.
The JSON is a credential. Clustr stores it encrypted and uses it only to write the export table.
2

Pick a dataset

Use existing (pick a dataset Clustr found) or Create new. Click Continue.
3

Confirm and sync

Clustr checks <dataset>.clustr_referral_paths and either creates it or reuses it. Click Connect to save the connection and run the first full export.
After the initial sync, Clustr pushes new and updated opportunities at the end of every enrichment job automatically.

How It Works

Clustr writes a single table, <dataset>.clustr_referral_paths, one flat, denormalized row per opportunity. Rows are upserted on id with a MERGE, so re-syncing never duplicates, and a full sync also removes opportunities that no longer exist in Clustr. Because it is keyed and idempotent, the table is safe to query live, build views on, or point a BI dashboard at.

Settings

The BigQuery panel shows connection status and sync controls.

Table Schema

clustr_referral_paths is keyed on id (used for upserts); all other data fields are stored as STRING so the export never fails on type coercion. Full column reference:

Troubleshooting