Raw data only. Triple Whale lands as warehouse tables. It is not modeled in dashboards or Uni yet, and it does not replace the Triple Whale app.These export tables already live in your dedicated warehouse. Register them from Triple Whale’s setup page; they are separate from the SourceMedium-delivered tables selected under Warehouse → Raw data.
Vendor documentation
The in-app destination is Data Warehouse Export. The knowledge-base article starts from Data → Integrations and connects BigQuery there. Both end at the same BigQuery destination.
Plan requirements
To add a new connection on Foundation, ask a workspace admin to upgrade to Pro. In Connect, the source shows Requires Pro and links to your plan details. If your workspace already has this source connected, you can continue using and managing it on Foundation.Pro: self-serve BigQuery export
Pro delivers a dedicated BigQuery project you administer. You grant Triple Whale write access on a dataset in it. Connect shows the project ID.What you need
- An active Triple Whale account with Data Warehouse Export
- Access to your dedicated BigQuery project (Connect shows the project ID)
How to connect
1
Create an isolated dataset
In your dedicated BigQuery project, create a dataset for this export (for example
triple_whale_export). Triple Whale recommends an isolated dataset so the exporter cannot write elsewhere.2
Grant Triple Whale write access on that dataset
Open the dataset → Share → Manage Permissions → Add principal. Add
srv-big-query-exporter@shofifi.iam.gserviceaccount.com with BigQuery Data Editor. Grant it on the dataset, not the whole project. Triple Whale’s BigQuery setup is the vendor procedure.3
Connect BigQuery in Triple Whale
Open Data Warehouse Export (or Data → Integrations → BigQuery), click Connect on BigQuery, enter the project ID and dataset ID, check the box confirming the service account was added, and save.
4
Create a scheduled export
Click New Export, pick the BigQuery destination, set a New Table ID (Triple Whale creates the table), and write SQL that selects the columns you need. Do not use
SELECT *. Triple Whale’s schema is dynamic and wildcard selects break as fields change.For measurement next to platform ROAS, start from Triple Whale-attributed tables such as pixel_joined_tvf, not ads_table (channel-reported). Include event_date when the table requires it.Choose Export Now or a recurring schedule (hourly, daily, or weekly). Each run appends rows. Triple Whale does not de-duplicate. Add an exported_at timestamp in the SQL and de-duplicate in BigQuery using their de-duplication guide.5
Confirm in SourceMedium
Open Triple Whale setup in SourceMedium and choose Find my datasets. Select the export dataset and tables, then Verify and save source. SourceMedium checks table read access and records the location, verification time, table modification time and stored row count. This does not certify future exports or deduplication. A table or view that would scan more than 10 GB can’t be checked. After you resume a paused source, open Configure warehouse source and choose Verify and save source so SourceMedium checks it again.If the SQL schema later changes, create a new table and update your selection. Triple Whale does not alter an existing export table’s schema.
What data syncs
The tables Triple Whale creates from the export SQL you configure. Grain and columns are those of that query. First release is those warehouse tables only. History can be backfilled by running the same export SQL in date batches (for example month by month).Notes
- This is Triple Whale Data Warehouse Export to BigQuery, not the Custom SQL API (that is a pull).
- Exports append. Querying the raw table without de-duplication inflates totals.
- First release is tables you query, not a dashboard replacement.

