Google BigQuery
This page describes how to configure Google BigQuery as a Census destination.
Last updated
This page describes how to configure Google BigQuery as a Census destination.
Last updated
In this guide, we will show you how to connect Census to Google BigQuery as a destination.
If you are configuring Google BigQuery as a source (to query data from BigQuery to sync elsewhere), that process is documented separately here: Google BigQuery as a Source
Visit the Destinations page and click + New Destination.
Enter your Google Cloud Project ID.
In order to connect to your BigQuery projects, Census uses a service account. This service account can be provided by you or managed by Census (recommended).
If you would prefer to have Census to use a service account that you own (instead of our automatically-managed account) to connect to BigQuery, you may provide its service account key JSON file here.
Otherwise, one you save your connection, Census will create a dedicated Google Cloud Service Account for each BigQuery destination. After the previous step, this account was created. To load data into BigQuery, the account needs the appropriate permissions.
Click the Activate Cloud Shell (near top right) icon in Google Cloud and execute the following commands.
Replace cs-sandbox-12345
with your Project ID.
Replace census-12345abcd1234512345abcdabcd@sutrolabs-giza-production.iam.gserviceaccount.com
with the service account provided in the Census UI.
To optimize the time it takes to load your tables within the Census UI when creating and editing syncs, only grant the Census service account permissions to the datasets you want to use within your Census syncs. This will reduce the number of tables Census needs to load and display as well as limit the number of tables to which Census has access.
Object Name
Supported?
Sync Keys
Behaviors
Table
✅
Required columns
Update or Create, Update Only, Add
Learn more about all of our sync behaviors in our Syncs documentation.
Contact us if you want Census to support more BigQuery objects and/or behaviors
To optimize loading time within the Census UI when creating and editing syncs limit the visibility of the Census service account to only the tables and schemas you want to use for syncs within Census. This will reduce the number of tables Census needs to load and display.
While BigQuery itself doesn't support IP allow lists, you can use VPC Service Controls to wrap your BigQuery instance and limit access. You can find Census's set of IP address for your region in Network Access Controls.
When using VPC Service Controls, you will also need to allow BigQuery unloads to the Census GCP bucket. To do that, you'll need to add gs://sutrolabs-giza-unloads-production
in the allow list for BigQuery unloads.
You can send our support team an email at support@getcensus.com or start a conversation from the in-app chat.