Dashboards on the dataset you already have
Build leadership dashboards and scheduled reports straight on your BigQuery tables, with no export and no second copy to keep in sync.
Go Fig + Google BigQuery
Put the tables your data team keeps in Google BigQuery behind your dashboards, scheduled reports, and Celeste's answers, read in place and never changed.
Key facts
What you can do with Google BigQuery in Go Fig
Google BigQuery is where many companies already keep the tables their reporting runs on. Connect it and those tables become part of your data foundation without moving anything. Your data team sets it up once with a solutions engineer. Your data stays in your BigQuery, and Go Fig queries the tables there instead of copying them into its own storage. The connection is read only, so nothing in BigQuery ever changes. The numbers your data team already trusts then drive dashboards and scheduled reports, sit next to the CRM and the other systems you connect, and answer questions in Celeste, Go Fig's AI analyst.
Website and product activity beside revenue
If your website or product activity already lands in BigQuery, it can sit next to the customers and revenue from your other systems, so one dashboard shows both side by side.
One source of truth
Leadership, finance, and sales work from the same tables your data team reports from, so the figures quoted in a meeting match what everyone else sees.
What Go Fig reads from Google BigQuery
How to connect Google BigQuery
Create a service account
In Google Cloud, your data team creates a service account (a login meant for software, not a person) and downloads its key as a JSON file.
Give it read access
They give the service account permission to read the dataset Go Fig should use and to run queries on it. Read only means it can look but never change anything.
Enter the details in Go Fig
With your solutions engineer, they add the JSON key, the project, the dataset, and its location (the region where the dataset is stored).
Check the tables
Confirm Go Fig can see the tables you expect. From then on, Go Fig reads them in BigQuery each time they are used.
Questions about Go Fig + Google BigQuery
Who sets up the connection?
Someone on your data team who can create a service account in Google Cloud, working with a solutions engineer. After that one setup, the reports, dashboards, and answers built on it need nothing from anyone else.
Does Go Fig copy our BigQuery data?
No. Your tables stay in your BigQuery, and Go Fig queries them there instead of keeping its own copy. To find the right table, it does keep field names, descriptions, and a few sample rows in its search index, as our security page explains.
How current is the data?
As current as your dataset. Go Fig queries BigQuery each time the data is used, so when your data team refreshes a table, the next report reflects it.
Can Go Fig edit or delete our BigQuery tables?
No. The connection is read only. Go Fig can look at the dataset you share, but never change it.
What goes into the connection?
A Google service account key as a JSON file, plus the project, the dataset, and the dataset's location.
Ready to connect Google BigQuery?
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.