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:- Create a Google BigQuery source within Zeotap CDP.
- Integrate the created source with the Google BigQuery platform.
Prerequisites
- 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.
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.
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.
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.
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.
PRIVATE_KEY is the private portion of the public/private key pair:
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.Open the Sources application
Start a new source
Choose the category

Choose Google BigQuery

Enter the BigQuery details
- Sync frequency
- Project ID
- Dataset
- Table

Select the Service Account Owner
- 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.

Choose the Data Entity

Set the Delta Queries Selection

- 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.

Create the 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.Copy the Service URL

Open your BigQuery project
Open the project in a new tab

Open the permissions panel

Add a principal

Paste the Service URL
Assign the role

Save the grant
Test the connection

Confirm the result

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.
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
FAQ
Should I choose Customer or Zeotap as the Service Account Owner?
Should I choose Customer or Zeotap as the Service Account Owner?
How often can the BigQuery source sync?
How often can the BigQuery source sync?
Can I ingest only the rows that changed since the last sync?
Can I ingest only the rows that changed since the last sync?
Are tables with JSON columns supported?
Are tables with JSON columns supported?
Can I also send Zeotap data out to BigQuery?
Can I also send Zeotap data out to BigQuery?
Next steps
- Explore the BigQuery source overview →
- Explore best practices for BigQuery →
- Explore how to map the Catalogue for Customer Data (CE) →
- Explore how to map the Catalogue for Non-Customer Entity (NCE) data →
- Explore how to add a Non-Customer Entity (NCE) attribute in the Catalogue →
- Explore the Join Key Enricher and how to configure it →
- Explore the Google BigQuery destination →
- Explore the other Data Warehouse sources →