BigQuery

BigQuery

NinjaCat supports connecting to Google BigQuery as a custom dataset source. This allows you to query data stored in your BigQuery project and surface it in NinjaCat reports and Data Cloud.

This connector signs in with a Google account (OAuth). NinjaCat does not accept a vendor's service-account JSON key file — there is no field for it in the connector setup form.

Prerequisites

Before setting up a BigQuery connection, ensure you have:

  • A Google account you can sign into.
  • That account must be granted, on the Google Cloud project that holds the data:
    • BigQuery Job User
    • BigQuery Data Viewer
  • If the data lives in a project you don't own (e.g. data provided by a vendor or partner), the project owner has to grant those roles to your Google account first — this can't be done from within NinjaCat.
  • Each BigQuery connector is tied to a single signed-in Google account. If you need to connect a different project owned by a different party, create a new connector rather than reusing one built for another project.

Setup Steps

  1. Go to Settings-> Data Sources -> Add Network -> Search for Big Query and authenticate with Google
  2. Go to Data Cloud → Connectors for the agency.
  3. Click New Connector → BigQuery. -> Give the Connector a name and associate the Credential you setup in step 1
  4. Go to Add Dataset
  5. Enter Dataset Name, Project ID, SQL Query
  6. Optional: set Dataset Location if your dataset isn't in the US multi-region.
  7. Save.

Connection Fields

FieldRequiredDescription
Project IDYesYour Google Cloud project ID
Dataset NameYesThe BigQuery dataset name
SQL QueryYesThe table or view to query
Dataset LocationNoThe region where your BigQuery dataset resides (e.g., US, EU, us-central1, us-east4). Leave blank to use the default behavior (US multi-region).

Dataset Location Field

What It Does

The Dataset Location field is a free-text input field. Enter the region identifier that matches the location of your BigQuery dataset — for example:

  • US (US multi-region, the default if left blank)
  • EU (Europe multi-region)
  • us-central1
  • us-east4

When to Use It

Set the Dataset Location field if your BigQuery dataset is stored outside the US multi-region (i.e., any region other than US). If you have previously seen errors like:

Not found: Job <project>:<job_id> was not found in location US

this field resolves those errors by telling NinjaCat which region to route queries to.

Existing connections are unaffected when the field is left blank. Leaving it blank preserves the previous default behavior (US multi-region).

How to Find Your Dataset's Location

  1. Open the Google BigQuery console
  2. Expand your project and select the dataset
  3. Click Dataset info — the Data location field shows the region

Enter that value exactly (case-sensitive) in the Dataset Location field in NinjaCat.

On-Screen Connection Errors

Connection and region errors are now surfaced directly on screen as you set up or edit a dataset. If NinjaCat cannot connect to your BigQuery dataset, you will see an error message displayed as a notification.

⚠️

Note on error messages: The error text shown is passed through from Google's API response. Messages may include Google's raw error text, such as:

Not found: Job <project>:<job_id> was not found in location US

If you see a message referencing an unexpected location (e.g., location US when your data is in eu-west1), set the Dataset Location field to match your dataset's actual region in BigQuery.

Troubleshooting

SymptomLikely CauseResolution
Authorization / permission error when signing inThe signed-in Google account doesn't have access to the projectAsk the project owner (or vendor) to grant BigQuery Job User + BigQuery Data Viewer, then reconnect
"I only have a service-account JSON key"Vendor issued key-based accessNot supported today — ask the vendor to grant a Google user account instead
"Job … was not found in location US"Dataset is outside the US multi-regionSet Dataset Location to the correct region

Related Pages

  • BigQuery Fields — Available dimensions and metrics for BigQuery datasets

Did this page help you?