Google BigQuery

This destination is currently under final review and will be available soon.

BigQuery is Google's data warehouse that enables scalable analysis over data. This integration allows pushing all your event properties to BigQuery.

Key features

The Google BigQuery destination provides the following key features:

  • Events structure: our Events reference feeds BigQuery, meaning that your data is properly bridged to the expected fields in an optimized way.

  • Universal schema: store events data without adjusting BigQuery's schema.

Destination setup

Ensure BigQuery API is enabled. More details are available following this LINK. Use Destination filters to refine events and/or other properties matching your specific needs.

First, you need to create a BigQuery table, with a specific schema, for storing raw data into it. See the following two subsections for a complete walkthrough.

Dataset

Access BigQuery console to locate your (1) project identifier and click (2) the three dots on the right. Select (3) Create dataset from the menu or, alternatively, you can use an existing dataset and jump to the next subsection.

Input a (4) dataset identifier (E.g. "myDatasetId"), select a (5) location type and click (6) CREATE DATASET.

Table

Create a table with the following structure:

The esiest way to create it is to click (7) the plus button:

copy and paste the following query in (8) the input area:

CREATE TABLE IF NOT EXISTS [PROJECT_ID].[DATASET_ID].[TABLE_ID] (rawDataCa STRING NOT NULL, createdAt TIMESTAMP NOT NULL) OPTIONS(description="CA raw event data stored in Google BigQuery")

Replace [PROJECT_ID] , [DATASET_ID] and [TABLE_ID] with your project, dataset and table identifier respectively. You set your table identifier at this step.

and then click the (9) RUN button.

Configuration

[1] This feature allows you to set an event property holding a dynamic value by adding two open braces ({{) in front of your property name and two close braces (}}) at the end (E.g. {{myEventPropertyPathAndName}}).

Quick reference

[1] Use Destination filters to specify your matching events. [2] Two columns: rawDataCa contains all your event properties, while createdAt is the creation timestamp.

Last updated