English (US)
Home Tutorials DataBridge integrating Google BigQuery with OnSign

DataBridge integrating Google BigQuery with OnSign

DataBridge gives you real-time access to OnSign player data by automatically mirroring events — playback, interactivity, app activity, and player status — to Google BigQuery as they happen. No manual exports or scheduled reports needed.

This guide covers two main parts:

  • Part 1 — Create a Google Cloud project, configure a Service Account with BigQuery Admin permissions, and generate the JSON authentication key.
  • Part 2 — Create a BigQuery Dataset and connect it to OnSign through the External Data Storage settings.

Part 1 — Setting Up BigQuery Access

Step 1 — Open IAM & Service Accounts

  1. Go to console.cloud.google.com and select your project (e.g. databridge-demo).
  2. In the left-hand menu, navigate to IAM & Admin → Service Accounts.

Note: Ensure that you are logged into an organization and have a project selected before proceeding.

 

Step 2 — Create a Service Account

  1. Click + Create service account at the top of the page.
  2. Fill in the form fields:
  1. Click Create and continue to proceed to the Permissions step.

Step 3 — Assign BigQuery Admin Role

  1. In the Permissions step, click Select a role.
  2. Search for and select BigQuery Admin.
  3. Click Continue, then Completed to finish creating the Service Account.

Note: You may see a message saying "Policy updated. It may take a few minutes for these changes to become active." — this is expected.

 

Step 4 — Generate the JSON Key

  1. In the Service Accounts list, click the three-dot menu (⋮) next to your new account.
  2. Select Manage keys.
  3. Click Add key → Create new key.
  4. Select JSON as the key type and click Create.
  5. The .json file will download automatically — save it somewhere secure.

Important: This JSON file contains your Service Account's private key. It cannot be recovered if lost — you would need to generate a new key. Never commit this file to a public repository.

 

Part 2 — Connecting BigQuery to OnSign

Step 5 — Create a Dataset in BigQuery

  1. Go to console.cloud.google.com/bigquery.
  2. In the left panel, click the three-dot menu (⋮) next to your project name.
  3. Select Create dataset and fill in the settings:
  1. Click Create dataset to confirm. The new dataset will appear in the project tree. 

Note: A dataset ID consists of two parts. The first part corresponds to the Project ID, while the second part, which appears after the period (.), corresponds to the BigQuery Dataset ID. For example, in my-project.sales_data, my-project is the Project ID and sales_data is the BigQuery Dataset ID.

 

Step 6 — Open External Data Storage in OnSign

  1. In OnSign, click your user icon in the bottom-left corner.
  2. Go to Settings → External Data Storage.
  3. Click + New External Storage.

Step 7 — Select the Data Source

  1. In the New External Storage window, set Platform to Google BigQuery.
  2. Choose a Source from the available options:
Source BigQuery Table Description
Playback Events playback_events Content playback records from players
Interactivity Events interactivity User interaction events
App Events app_events Events generated by apps on players
Player Info and Status player_status Real-time player status and information
  1. Click Confirm to proceed.

Note: Each data source creates a separate table in your BigQuery dataset. You can add multiple connections with different sources.

 

Step 8 — Configure the BigQuery Connection

  1. Fill in the configuration fields:

 

  1. Optionally, use the Fields selector to choose which event fields to store — or leave blank to store all fields.
  2. Optionally, add a Notification Email to receive alerts if data delivery fails.
  3. Click Confirm to save. OnSign will now start sending data to BigQuery automatically.

Note: Enabling For Internal Use hides the connection from end users — only platform owners will see it.

 

Step 9 — Add More Data Sources (Optional)

You can connect multiple sources to the same dataset. Repeat Steps 6–8 for each additional source. For example, adding Player Info and Status as a second connection creates a player_status table alongside playback_events in the same dataset.

Note: The Player Info and Status source includes an extra Data Ingestion Period field, which controls how frequently player status data is sent to BigQuery (every 5, 10, 15, or 30 minutes).

 

If you still have questions, watch the step-by-step video guide below.