Before you connect BigQuery

Work with your Google Cloud administrator and Optiply support. Agree the project, dataset, query configuration, enabled directions and permissions before creating credentials.

Read-only import access is separate from outbound writes. BigQuery Data Editor includes write permissions. BigQuery Job User permits query jobs but does not alone grant access to table data. Do not grant project-wide editing rights to solve an import error.

A service-account JSON key contains private credentials. Keep the whole file out of support messages, screenshots and shared documents. If your organization blocks key creation, ask your administrator for an approved setup. Do not bypass the policy.

Steps to connect BigQuery

Prepare the service account in Google Cloud

  1. Select the intended project in Google Cloud console.
  2. Under APIs & Services → Library, check that the BigQuery API is enabled.
  3. Open IAM & Admin → Service Accounts.
  4. Select the agreed existing service account, or choose Create service account with your administrator's approval.
  5. For a new account, enter its name and description.
  6. Review the generated service account ID before continuing.
  7. Choose Create and continue when assigning approved project roles, or Done when access is managed separately.
  8. Ask your administrator to grant only the approved data and job permissions at their agreed scopes.
  9. Open the service account and select Keys.
  10. If key creation is approved, choose Add key → Create new key.
  11. Select JSON, then Create.
  12. Save the downloaded key privately.

Google's service-account key guide explains key creation and organization-policy restrictions. A lost private key cannot be downloaded again. Arrange replacement through your administrator and support.

Select BigQuery in Optiply

  1. Open Settings → Integrations, then Add a source after the source lists load.
  2. In Select a source, search for BigQuery.
  3. Select BigQuery under Database, not BigCommerce.
  4. Choose Next to open Connect to system.
BigQuery under Database, alongside the separate BigCommerce result.
BigQuery under Database, alongside the separate BigCommerce result.Enlarge

Enter the agreed connection settings

Continue only when a credential form is offered. If Contact us appears instead, use that support route to agree setup. The screenshots show one form. The offered fields can vary.

  1. Enter the intended project identifier in BigQuery project ID.
  2. Enter the agreed service-account values in the credential fields below.
  3. Enter the intended Dataset ID.
  4. Review Queries with support before entering the agreed configuration.
  5. Review the project, dataset, permissions and enabled directions with your administrator and support.
  6. When the configuration is confirmed and Connect is available, choose Connect.
  7. Return to Settings → Integrations to check the linked source.
  8. Check the agreed imported sample records with support.
Project and service-account credential fields, with private entered values hidden.
Project and service-account credential fields, with private entered values hidden.Enlarge
Client ID, client certificate URL, Dataset ID and Queries fields.
Client ID, client certificate URL, Dataset ID and Queries fields.Enlarge

If BigQuery is missing or the form differs, stop before entering credentials and contact support.

Fields in the BigQuery connection form

FieldMeaning
BigQuery project IDThe Google Cloud project identifier, not a user email address.
Service Account Private Key IdIdentifier of the service-account key.
Service Account Private KeyThe private signing key. Enter it only through the approved credential form.
Service Account Client EmailThe service account's email identity, not your personal login.
Service Account Client IdThe service account's client identifier.
Service Account Client Cert URLThe certificate URL associated with the service account.
Dataset IDThe dataset within the agreed project. It is separate from the project ID.
QueriesThe extraction configuration agreed with support. Do not paste arbitrary SQL or invent its format.

Have your administrator and support match the credential values to the offered fields before submission. Use this table only for matching labels in your form. If the form requires different values, stop and ask support. The masked screenshot values are not examples to copy.

What you see when BigQuery connection worked

The source appears in the linked-source list. Check the connection outcome and agreed sample records with support. Connected and a completed form are separate from successful data import and correct record relationships.

Limits of connecting BigQuery

If your account reaches its integration limit, the dialog routes you to support instead of a credential form.

Connector availability, query settings and enabled directions depend on the agreed account configuration. No fixed first-sync deadline follows from pressing Connect. Dataset data access, permission to run query jobs and permission to write outputs are different grants.

If BigQuery connection did not work

For blocked service-account or key creation, ask your administrator to review your permissions and organization policy. Keep existing security restrictions in place.

If Connect is unavailable or the connection fails, contact support with the step and sanitized error. Ask your administrator to check the project, service account, dataset and permission scopes. Never include the JSON key or private field values. Mask identifying details before sharing a screenshot.

Questions customers ask about the BigQuery connection

Do I need to contact Optiply to set up a BigQuery connection?

Yes, agree the project, dataset, Queries configuration and permissions with Optiply Support before you create credentials. If the BigQuery connection dialog shows Contact us instead of a credential form, Support continues the setup with you.

What do I need to connect BigQuery to Optiply?

You need a service-account JSON key for the intended Google Cloud project, the BigQuery project ID, the Dataset ID and the Queries configuration agreed with Support. Keep the JSON key out of support messages and screenshots.