Google BigQuery - Auxia Docs

Google BigQuery is Google Cloud’s serverless data warehouse. Auxia’s BigQuery connector reads tables directly from your GCP project using a read-only service account, so there’s nothing to export or schedule on your side.

Setup guide

Connect in about 15 minutes

Troubleshooting

Fix common errors

Release notes

What’s changed

Features

Feature	Supported	Notes
Self-serve setup	✅	Guided wizard in the Auxia Console
AI-assisted schema mapping	✅	Proposes user ID, event, and attribute mappings; you review and correct
Incremental sync (new rows only)	✅	Native tables with append support
Full-refresh sync	✅	Views, snapshots, and tables without append support
Row filtering	✅	AND/OR rules, grouped conditions
User ID resolution via joins	✅	Resolve a table’s user ID through up to five joined tables
Transfer only	✅	Land a table in Auxia without mapping it; transform it later
Project- or dataset-level access	✅	Grant access to a whole project or specific datasets
Data Health monitoring	✅	Per-stage status, run history, and row counts
Capture deletes	❌	Sources must be append-only
Edit a connection after creation	Coming soon
Choose your own sync time	Coming soon
Self-serve backfills	Coming soon	Today, request backfills from your Auxia contact

Sync overview

Access: a service account unique to your Auxia project, granted BigQuery Data Viewer (read-only) on your project or datasets.
Mode: Auxia chooses full refresh or new rows only from your table’s shape. Native tables with append support sync incrementally every hour; everything else syncs daily as a full refresh.
Faster syncs: need fresher data? The Auxia team can configure a custom cadence, as often as roughly every 10 minutes. When will my data show up? →
Copies, not changes: Auxia copies only the tables and columns you map into its platform. Nothing is created, duplicated, or modified in your project.

Table requirements

Each table is checked during setup. A table that fails a check is flagged with the reason and how to fix it:

Check	Requirement
Partitioning	Partitioned by a date or timestamp column at day granularity, or date-sharded (`events_YYYYMMDD`)
Append support	Required for tables adding more than 1 TB per day — use a native table, not a view
Table type	Native tables are preferred. Views sync as full refresh
Nesting depth	Nested fields within the project’s depth limit — flatten deeply nested `STRUCT`s

See Source data requirements for requirements shared by all connectors.

Supported table types

Auxia recognizes these BigQuery schemas automatically and pre-fills their mapping:

GA4 events, intraday events, and user attributes exports
Firebase Analytics events
Amplitude, Mixpanel, and Segment event exports
Generic event tables, and columnar or row-based user attribute tables

Limitations

Deletes and in-place updates (UPDATE, DELETE, MERGE) are not captured.
A new connection doesn’t load history automatically. Contact your Auxia point of contact to load a past date range.
Join keys must have the same data type on both sides — Auxia won’t cast them.
More than about 1 TB per run works, but talk to your Auxia contact before committing to a timeline.

Setup guide

Troubleshooting

Release notes

​Features

​Sync overview

​Table requirements

​Supported table types

​Limitations

Features

Sync overview

Table requirements

Supported table types

Limitations