---
title: BigQuery
slug: bigquery
docTags: 
createdAt: 2025-06-02T18:45:36.968Z
---

# Introduction

BigQuery is Google Cloud’s fully managed, serverless data warehouse that enables fast SQL-based analysis of large datasets. As a data warehouse destiantion, BigQuery can serves as the central data foundation, where raw customer data from multiple sources (e.g., CRM systems, web analytics, transactions, marketing tools) is collected, cleaned, and unified.

# Getting started

- Google Cloud [Project ID](https://support.google.com/googleapi/answer/7014113?hl=en)
- BigQuery [Dataset](https://cloud.google.com/bigquery/docs/datasets-intro)
- Access Key (Google Service Account JSON for BigQuery)

### Service account configuration

A **Service Account** is a special account with an id that looks like *`NAME@PROJECT.iam.gserviceaccount.com`*. The account can have a key (or several keys) which is represented by JSON. 

Please note, to use Service Account as an authorization mechanism, the resource (google doc, analytics account, add account etc) should be shared with that account.

The easiest way to create Service Account is through **[Google Cloud Console](https://console.cloud.google.com/):** go to Navigation ("burger" at top right corner) → *IAM & Admin* → *Service account*. Create service account and download key JSON.

There a few other ways (including console utils), please see [documentation](https://cloud.google.com/iam/docs/creating-managing-service-account-keys)

The Service Account key can be referred to in a few different ways when setting up BigQuery as a Chord CDP Destination:

::::CodeDrawer{title="Service Account Key (Examples)" isResponseExpanded="false" autoGeneratedAnchorSlug="service-account-key-examples" legacyHash="9FzlwMALWNxpm9TPLmZB9"}
:::CodeblockTabsExamples
JSON

```json
auth:
  service_account_key: {
    "type": "service_account",
    "project_id": "<PROJECT_ID>",
    "private_key_id": "<PK_ID>",
    "private_key": "<PRIVATE_KEY>",
    "client_email": "<EMAIL>",
    "client_id": "CID",
    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
    "token_uri": "https://oauth2.googleapis.com/token",
    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
    "client_x509_cert_url": "<CERT_URL>"
  }
```

JSON String

```json
auth:
  service_account_key: '{"type":"service_account","project_id":"<PROJECT_ID>","private_key_id":"<PK_ID>","private_key":"<PRIVATE_KEY>","client_email":"<EMAIL>","client_id":"CID","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://oauth2.googleapis.com/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","client_x509_cert_url":"<CERT_URL>"}'
```

Path to File

```none
auth:
  service_account_key: '/path/to/file.json'
```
:::

:::CodeblockTabsResponses
```javascript
```
:::
::::

# Connecting to the BigQuery CDP destination

1. Log into the Chord data platform.
2. Navigate to the CDP.
3. Click the **"Add"** button next to Destinations.
4. Select **BigQuery&#x20;**&#x66;rom the destination catalog.
5. Enter in the destination name and these required credentials:
   1. Project ID
   2. Dataset
   3. Access Key
6. Click **"Create"&#x20;**&#x74;o connect.

:::hint{type="danger"}
Before connecting destinations in the Chord CDP, please verify with all Destination owners that all **non-Chord CDP** configured destinations are *disabled.*
**
Running external destinations alongside configured Chord CDP destinations ***can result in duplicate events downstream.&#x20;***
:::