Skip to main content
BigQuery source configuration form

​
Overview

The BigQuery source synchronizes data from a Google BigQuery table directly into Reelevant. This is ideal for teams that centralize their data in BigQuery and want to leverage it for personalization.

​
Configuration

​
Required Fields

​
Authentication

BigQuery supports two authentication methods:
Authenticate using a Google Cloud service account key.
The minimum required role is BigQuery Data Viewer (roles/bigquery.dataViewer) on the target dataset. If you use a custom SQL query, the service account also needs BigQuery Job User (roles/bigquery.jobUser) on the project.

​
Optional Fields

​
Custom SQL Queries

When you provide a custom SQL query, Reelevant executes it against BigQuery instead of reading the entire table. This is useful for:
  • Filtering rows (e.g. SELECT * FROM my_table WHERE active = true)
  • Selecting specific columns
  • Joining multiple tables
  • Applying transformations
The query must be valid BigQuery Standard SQL. Make sure the service account has permission to run jobs in the project.

​
Incremental Sync

BigQuery supports incremental synchronization when used with the Keep Previous Data update mode. To enable this: When configured, Reelevant only fetches rows where the timestamp field is greater than the last recorded value, appending new data to the existing dataset.
If your datasource uses the Override Previous Data update mode (the default), the timestamp field is not needed — the entire table or query result is re-imported on each sync.

​
Supported Data Types

BigQuery data types are automatically converted:

​
How It Works

  1. Reelevant authenticates with BigQuery using the provided credentials.
  2. If a custom query is provided, it is executed. Otherwise, the full table is exported.
  3. For large tables, Reelevant uses an optimized export-to-GCS pipeline for better performance.
  4. Fields are extracted and made available for mapping.
  5. On subsequent syncs, the query or table is re-read (or incrementally fetched if configured).
Ensure the service account has read access to the specified dataset and table. The minimum required role is BigQuery Data Viewer. For custom queries, the service account also needs BigQuery Job User.