Skip to main content
This page covers the Google BigQuery source — pulling data into Zeotap CDP from a table in your BigQuery project. To send Zeotap audience data out to BigQuery instead, see Google BigQuery destination.

What this is

Zeotap simplifies the data onboarding process by letting you connect directly to the source data residing in BigQuery through the Sources application, within Zeotap CDP. The integration sits in the Data Warehouse source category: you point it at one project, dataset and table, choose how often Zeotap re-reads that table, and the records are ingested as either Customer Data or Non Customer Data. You can harness the Zeotap–Google BigQuery source integration to strengthen your data analytics capacities. It also empowers you to analyse diverse datasets, create precise customer segments, curate personalised content and refine advertising strategies. Setting up the integration takes two passes:
  1. Create a Google BigQuery source within Zeotap CDP.
  2. Integrate the created source with the Google BigQuery platform.

Prerequisites

Before you create a BigQuery source in the Sources application, confirm:
  • You have an account with BigQuery, and the data you want to import into Zeotap already resides in that account.
  • You know the Project ID, Dataset and Table that hold the data — see Gather the BigQuery and sync details.
  • You have decided the Region the data is ingested into and the Sync frequency the source should run on.
  • You have decided who the Service Account Owner is — Customer or Zeotap. If Customer, create the JSON key file in Google Cloud beforehand and have it ready to upload.
  • The table you are ingesting does not use JSON column types. Zeotap CDP does not support tables with JSON column types.

Supported identifiers and data entities

You can ingest any identifier or attribute of your choice from a BigQuery table into Zeotap CDP. The BigQuery source supports delta fetch, so a run can be restricted to the rows that changed since the previous run.

Data entities

Zeotap supports the following two groups of data entities:
  • Customer Data — refers to a wide range of information, such as demographic, behavioural, product-related, derived and modelled information. This data is gathered from various brand interfaces, platforms, tools and services.
  • Non-customer Entity Data — refers to data that is not directly tied to a user but to an attribute associated with the user. The most common forms of Non-Customer Entity Data are product catalogues, order data, feed data, campaign data, account data and so on. In the source form this group is labelled Non Customer Data.
For more information on the data entities supported by Zeotap CDP, see Supported data entities.

Gather the BigQuery and sync details

Collect the following before you open the source form. The Zeotap-side settings come first, then the values you read out of the Google Cloud console.
  • Source Name — the name you will see within Zeotap once you successfully create the source.
  • Region — the region where the data needs to be stored. Zeotap currently supports data ingestion in the following regions:
    • EU — all EU countries’ data is ingested to the bucket provisioned for you in the EU region.
    • UK — the United Kingdom’s data is ingested to the bucket provisioned for you in the UK region.
  • Sync frequency — defines how often data is ingested from the source. Zeotap currently supports Sync once, Every hour, Every 3 hours, Every 6 hours, Every 12 hours, Daily, Weekly and Monthly.
  • Sync Time — when you choose Daily, Weekly or Monthly as the sync frequency, you can specify the exact time for the sync to occur.
  • Sync Period — indicates whether the selected Sync Time is in the AM or PM.
  • Sync Day — if Weekly sync is selected, you can specify the day of the week on which the sync should run.
  • Monthly Sync date — if Monthly sync is selected, you can specify the day of the month on which the sync should run.
  • Data Entity — whether the records you are ingesting are Customer Data or Non Customer Data. See Data entities for what each group covers.

Project ID

A Project ID is a unique string that differentiates your project from all others on Google Cloud. You can use the Google Cloud console to generate a Project ID. You can find the Project ID in the Google Cloud console Dashboard page. In the example below, the Project name is My Sample Project and the Project ID is my-sample-project-191923.
Google Cloud console dashboard showing the Project name and Project ID

Dataset

Datasets are top-level containers that are used to organise and control access to your tables and views. In the example below, the Dataset is GBQ_dataset.
BigQuery explorer showing a dataset inside a project

Table

A BigQuery table contains individual records organised in rows. Each record is composed of columns/fields. Every table is defined by a schema that describes the column names, data types and other information. In the example below, the tables are Demotest, DemotestBQ, Table006, Table007 and TableBQ. Zeotap CDP does not currently support tables with JSON column types.
BigQuery explorer showing the tables inside a dataset

Service Account Owner

In the Google BigQuery source integration, a Service Account Owner refers to a user account that has owner privileges for configuring and overseeing significant queries within the integration. This ownership entails the authority to view, modify and manage the data in Google BigQuery. The responsibilities of a Service Account Owner in Google BigQuery include performing administrative tasks, managing passwords and permissions, and configuring service accounts for integration with external data sources within the Google Cloud Platform (GCP). Select the Service Account Owner based on your requirement. You can choose either Customer or Zeotap:
  • If you select Customer, a section appears where you upload the JSON key file that you have created. Click + SELECT FILE to upload the JSON key file. To learn how to create a JSON key file, see Create and delete service account keys in the Google Cloud documentation.
  • If you select Zeotap, you can proceed directly to the Data Entity selection step.

Service Account Key JSON

The Service Account Key JSON is necessary to use a service account from outside of Google Cloud, such as on other platforms or on-premises. For information on creating a Service Account Key JSON in the Google Cloud console, see Create and delete service account keys.
Google Cloud console panel for creating a service account key in JSON format
Once you create a JSON key, store the key file securely so you can authenticate your service account later. The downloaded key has the following format, where PRIVATE_KEY is the private portion of the public/private key pair:
The service-account key grants access to your BigQuery data. Keep the JSON file out of tickets, chat threads and version control.

Create the BigQuery source in Zeotap CDP

After you have obtained all the information described above, perform the following steps to create a BigQuery source within Zeotap CDP.
1

Open the Sources application

Navigate to the Sources application in the Zeotap CDP App.
2

Start a new source

Click CREATE SOURCE.
3

Choose the category

Choose Data Warehouse as the Category.
Source category picker with Data Warehouse selected
4

Choose Google BigQuery

Select Google BigQuery as the data source.
Data Warehouse source picker with Google BigQuery listed
5

Enter the BigQuery details

Enter the information below, based on your BigQuery account. How to procure each of these details is covered in Gather the BigQuery and sync details.
  • Sync frequency
  • Project ID
  • Dataset
  • Table
BigQuery source form showing the sync frequency, project, dataset and table fields
6

Select the Service Account Owner

Select the Service Account Owner based on your requirement. You can choose either Customer or Zeotap.
  • If you select Customer, a section appears where you upload the JSON key file that you have already created. Click + SELECT FILE to upload it. To learn how to create a JSON key file, see Create and delete service account keys.
  • If you select Zeotap, proceed directly to the Data Entity selection step.
Service Account Owner set to Customer, with the JSON key file upload control
7

Choose the Data Entity

Under Data Entity, depending on the type of data that you want to ingest, choose either Customer Data or Non Customer Data, then proceed with the source creation. For what each group covers, see Data entities.
Data Entity selection offering Customer Data and Non Customer Data
8

Set the Delta Queries Selection

Under Delta Queries Selection, decide whether or not you want to consider deltas (data additions/changes) in a dataset for a specific time period, based on the values of the timestamp column. Based on your requirement, select either true or false.
Delta Queries Selection toggle set on the BigQuery source form
If you select true, the fields Delta Column Name and Delta Column Data Type are enabled, and you must provide the following details:
  • Under Delta Column Name, provide the name of the column that you want to fetch data from.
  • Under Delta Column Data Type, choose the time increment for fetching the data from the selected column.
Delta Column Name and Delta Column Data Type fields enabled
If you select false, you are not required to make any additional selections. You can proceed directly to the source creation step.
9

Create the source

Click CREATE SOURCE.

Integrate the created source with the Google BigQuery platform

Upon successfully creating the source within Zeotap CDP, go to the IMPLEMENTATION DETAILS tab. Under this tab, you can find details about the created source, based on the Service Account Owner selected.

Scenario 1 — Zeotap is the Service Account Owner

If you selected Zeotap as the Service Account Owner while creating the source, perform the following steps to integrate the source with the Google BigQuery platform.
1

Copy the Service URL

In the IMPLEMENTATION DETAILS tab, under Access Details, copy the Service URL.
Access Details section of the Implementation Details tab showing the Service URL
2

Open your BigQuery project

Go to the Google BigQuery console and open your project.
3

Open the project in a new tab

On your project, click the three dots and click Open in > New tab.
BigQuery project overflow menu with the Open in New tab option
4

Open the permissions panel

In the new tab, click SHARING and then click Permissions.
Sharing menu in BigQuery with the Permissions option
5

Add a principal

Click ADD PRINCIPAL.
BigQuery permissions panel with the Add Principal control
6

Paste the Service URL

Under Add principals, in the New principals field, paste the Service URL that you copied earlier.
7

Assign the role

Under Assign roles, choose BigQuery > BigQuery Data Viewer.
Assign roles picker with BigQuery Data Viewer selected
8

Save the grant

Click SAVE.
9

Test the connection

Return to the IMPLEMENTATION DETAILS tab. Beside the Service URL field, click TEST CONNECTION.
TEST CONNECTION control beside the Service URL field
10

Confirm the result

Upon successful integration, a message appears confirming that the connection is successfully established, allowing you to begin data ingestion.
Confirmation message that the BigQuery connection was successfully established

Scenario 2 — Customer is the Service Account Owner

If you selected Customer as the Service Account Owner while creating the source, the IMPLEMENTATION DETAILS tab appears as shown in the image below. In this case, no additional steps are needed to integrate the source with the Google BigQuery platform.
Implementation Details tab for a BigQuery source with Customer as the Service Account Owner

Verify the source is ingesting data

  • Scenario 1 only — TEST CONNECTION on the IMPLEMENTATION DETAILS tab returns a message confirming that the connection is successfully established.
  • The source appears on the Sources listing. Once data begins flowing into the source, the source status changes to Integrated and the Preview Data tab is populated. Open that tab to confirm the columns and values that arrived before you map them in the Catalogue — see Components of the Preview Data tab.

Troubleshooting

If the source still does not connect after re-checking the values above, contact the Zeotap support team at support@zeotap.com. Include the source name, the Service Account Owner you selected, the Project ID, Dataset and Table, and the time of the failed attempt.

FAQ

Both are supported. If you choose Zeotap, you grant the Zeotap Service URL the BigQuery Data Viewer role on your project after the source is created (Scenario 1). If you choose Customer, you upload your own service-account JSON key during source creation and no further steps are needed on the BigQuery side (Scenario 2).
The supported sync frequencies are Sync once, Every hour, Every 3 hours, Every 6 hours, Every 12 hours, Daily, Weekly and Monthly. For Daily, Weekly and Monthly you also set a Sync Time and Sync Period (AM/PM), plus the day of the week for Weekly and the day of the month for Monthly.
Yes. Set Delta Queries Selection to true, then name the timestamp column under Delta Column Name and choose the time increment under Delta Column Data Type. Setting it to false re-reads the full table on every run.
No. Zeotap CDP does not currently support BigQuery tables with JSON column types.
Yes, through a separate integration. See Google BigQuery destination.

Next steps

Last modified on November 17, 2026