BigQuery integration
Bring tables you already keep in Google BigQuery into Dashworx, and load modelled Dashworx data back into your own BigQuery project for wider analysis.
About the BigQuery integration
Google BigQuery is Google Cloud’s serverless data warehouse. Data is organised into projects, datasets and tables, queried with standard SQL, and billed by storage plus either the bytes each query scans or reserved slot capacity. It is also where the native GA4 export lands, as daily event tables with nested parameters, and where many teams already keep CRM extracts, finance data and the output of their own models.
Connecting BigQuery as a source lets Dashworx read those tables and model them alongside the 600+ other sources it connects. A margin table your data team maintains, or the raw GA4 event export, can then sit in the same dashboards as ad spend and store orders. Partitioned and date-sharded tables, such as GA4’s events_YYYYMMDD format, are common, so the datasets and date ranges to read are agreed during setup.
Because the connection runs in both directions, BigQuery can be the place your team builds on Dashworx data as well as a source for it.
What data you get from BigQuery
Tables and views
Partitioned tables
Date-sharded tables
GA4 event export
Google Ads Data Transfer tables
Search Console bulk export
CRM and ERP extracts
Finance and margin tables
Product cost tables
Nested and repeated fields
Custom dimensions
Custom metrics
…and more.
What teams do with BigQuery data
Visual Intelligence
Combine your own margin model with ad spend
Read the product margin table your analysts keep in BigQuery and show profit after ad spend by channel, not just revenue.
LEARN MORE →
Conversational AI
Ask questions of your GA4 BigQuery export
Once the GA4 event export is modelled, ask about events and journeys in plain English instead of writing SQL against nested parameters.
LEARN MORE →
AI Dashboard Generator
Generate dashboards from warehouse tables
Describe the report you need and get a dashboard built from BigQuery tables combined with your other connected sources.
LEARN MORE →
Send Dashworx data to BigQuery
Dashworx can write its modelled data into a BigQuery dataset in your own Google Cloud project. That means cleaned, aligned tables from every connected source, with consistent channel names and date formats, rather than one raw export per platform that your team has to reconcile first.
Teams use this when the data needs to go further than a dashboard: joining marketing performance to internal tables only the warehouse holds, feeding attribution or forecasting models, or pointing a BI tool at the same numbers Dashworx shows. Because the data lives in your project, access is managed with your own IAM roles and the history is kept under your own retention policies. Storage and query costs for the dataset are billed to your Google Cloud account.
How to connect BigQuery to Dashworx
01
Request your connection link
Ask for your secure BigQuery connection link from within Dashworx or through your account manager. It’s tied to your workspace, so only your team can use it.
02
Connect in one click
Open the link, sign in to BigQuery and authorise access. No API keys, developer time or spreadsheets required.
03
We aggregate and align your data
The Dashworx team brings your BigQuery data together with your other sources, then aligns it to your visual intelligence dashboards and smart AI features, so it’s analysis-ready without manual clean-up.
04
Get notified when you’re live
You’ll receive an in-platform notification as soon as your BigQuery connection is complete, and your data starts appearing across your dashboards.
Frequently asked questions
What does Dashworx do with my connected data?
How long does it take for my data to appear after connecting?
Do I need technical skills or a developer to connect a source?
How often is my data refreshed?
How is my data kept secure?
Can I connect multiple accounts from the same platform?
What if the platform I use isn’t listed?
Connect BigQuery in minutes
Book a demo and we’ll show you your own data, connected and visualised, before you commit.