Skip to main content
BigQuery is a source: the practices below apply to data you bring into Zeotap CDP from a BigQuery table. To send data the other way — out of Zeotap CDP and into BigQuery — see the Google BigQuery destination instead. A BigQuery source reads one table, identified by project, dataset and table name, on the sync frequency you set when you create it. Tables with JSON column types are not supported. Prepare the table against the three points below before you create the source; Create and Implement a BigQuery Source covers the setup itself.

​
At Least One User ID per Source

The table must have the details of at least one ID, such as email, cellphone, cookies or ADID. An ID is a mandatory requirement for a source, because it is what Zeotap CDP matches incoming records on.

​
Country Column in Data

Ensure that the Country column is present in the BigQuery table being ingested, and that it is filled with valid values. Records must be tied to a country before a data collection can be created; where the table carries no country of its own, the country can be hard coded instead. We recommend that you use ISO alpha-3 country codes.

​
Data Privacy and Compliance

Ensure that the region selection is in line with the data being ingested — the region you choose when creating the source must match the country of the records in the table, so that data belonging to one region is not ingested into another region’s bucket. This is to ensure data privacy and compliance. For how a country resolves to a storage region, see Region of Storage.

​
Next steps

Last modified on September 24, 2026