BigQuery Reporting & Dashboards | ATX AnalyticsTable Connector

Google BigQueryATX AnalyticsTable connects to Google BigQuery and keeps the bill in view. Analysts query the warehouse from a grid, cache the result locally and work on it there — so scrolling, filtering and re-formatting do not each become another billed query.

What you can do

Sign-in with a service-account JSON key, or with Application Default Credentials (gcloud, Workload Identity) and no stored key at all
An optional cap on bytes billed per query
Partition-aware: tables that require a partition filter are explained in plain words, and partition metadata is read from INFORMATION_SCHEMA, which costs nothing to scan
Save a result into the project's local DuckDB database so paging over it is billed once, not once per page
Export results into BigQuery tables; dashboards, PDF reports and scheduled refresh over BigQuery data

How to connect Google BigQuery

Open Settings → Connections and add a BigQuery connection.
Paste a service-account JSON key, or leave it empty to use Application Default Credentials.
Optionally set a cap on bytes billed per query.
Query, then save large results into the project's DuckDB database before paging and formatting them.

Security and governance

The service-account key is held in the encrypted vault and never written into the project
Application Default Credentials let a managed environment authenticate without any key file on disk

Availability

Database and warehouse connectors are counted per workspace: three on Corporate PRO, five on Corporate Advanced and Advanced Plus, unlimited on Corporate Unlimited, and every connector on Free and Individual.

More integrations

Glossary terms on this page

KPI dashboard: definition

ATX Institute on LinkedIn

This site needs JavaScript for the full experience. Every page above is reachable without it.