Google BigQuery

This page describes how to configure Google BigQuery as an Activations destination.

Getting Started

In this guide, we will show you how to connect Activations 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.

🔑 Permissions and Service Accounts

In order to connect to your BigQuery projects, Activations uses a service account. This service account can be provided by you or managed by Activations (recommended).

Option A: Upload Service Account Key

If you would prefer to have Activations 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.

Option B: Use Activations-managed Service Account

Otherwise, one you save your connection, Activations 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 Activations UI.

gcloud projects add-iam-policy-binding cs-sandbox-123456 \
  --member serviceAccount:census-12345abcd1234512345abcdabcd@sutrolabs-giza-production.iam.gserviceaccount.com \
  --role roles/bigquery.dataOwner

  gcloud projects add-iam-policy-binding cs-sandbox-123456 \
  --member serviceAccount:census-12345abcd1234512345abcdabcd@sutrolabs-giza-production.iam.gserviceaccount.com \
  --role roles/bigquery.jobUser

To optimize the time it takes to load your tables within the Activations UI when creating and editing syncs, only grant the Activations service account permissions to the datasets you want to use within your Activations syncs. This will reduce the number of tables Activations needs to load and display as well as limit the number of tables to which Activations has access.

️ Supported Objects and Sync Behaviors

Object Name	Supported?	Sync Keys	Behaviors
Table	✅	Required columns	Update or Create, Update Only, Mirror, Add

Learn more about all of our sync behaviors in our Syncs documentation.

Contact Support if you want Activations to support more BigQuery objects and/or behaviors

Optimize UI Performance

To optimize loading time within the Activations UI when creating and editing syncs limit the visibility of the Activations service account to only the tables and schemas you want to use for syncs within Activations. This will reduce the number of tables Activations needs to load and display.

Network Access Controls

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 Activations' 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 Activations GCP bucket. To do that, you'll need to add gs://sutrolabs-giza-unloads-production in the allow list for BigQuery unloads.

Need help connecting to Google BigQuery?

You can reach out to our support team.