BigQuery

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 https //support google com/googleapi/answer/7014113?hl=en bigquery 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 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 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 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 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 auth service account key '/path/to/file json' connecting to the bigquery cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select bigquery from the destination catalog enter in the destination name and these required credentials project id dataset access key click "create" to connect 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