Skip to main content
New Introducing Orchestrator Learn more
Data Warehouse integration

BigQuery + Conversion

Segment and personalize from BigQuery without filing engineering tickets.

BigQuery
Into Conversion
Conversion

How Conversion works with BigQuery

Conversion connects to BigQuery through a dedicated service account and runs the SQL queries you write on a schedule you choose. Each query's rows become contacts, custom objects related to contacts, or events that can trigger workflows and filter audiences. Access is limited to the datasets you share with the service account, and Conversion never writes to your project.

What syncs

Data Direction Details
Contacts Into Conversion Created or updated from query rows, matched on userId when present and on email otherwise. Creating a contact requires an email.
Custom objects Into Conversion Any custom object type you create in Conversion, with relationship fields to contacts built in the same query using JSON_OBJECT.
Events Into Conversion Rows with an event name and timestamp land on the contact timeline. An eventId keeps re-synced rows from duplicating.

How to connect BigQuery

  1. 1 Create a dedicated Google Cloud service account with the BigQuery Job User and BigQuery User roles, and generate a JSON key for it.
  2. 2 Share each dataset you want to sync with the service account as BigQuery Data Viewer, or grant that role across the project.
  3. 3 If your project uses VPC Service Controls or IP restrictions, allow Conversion's IP addresses.
  4. 4 Under Settings > CRM & Syncing > Connections, add a BigQuery connection with your project ID and the full JSON key, then create a sync for each destination.

See Conversion with BigQuery

Book a demo and we'll walk through the BigQuery integration on a stack that looks like yours.