Setup guide
Connect in about 10 minutes
Troubleshooting
Fix common errors
Release notes
What’s changed
Features
Sync overview
- Access: two read-only roles on the one bucket you connect — Storage Object Viewer (
roles/storage.objectViewer) to read files, and Storage Legacy Bucket Reader (roles/storage.legacyBucketReader) so the transfer service can look up the bucket’s location. - Cadence: self-serve connections sync once a day, and a day’s data appears the next morning. Connections set up with the Auxia team can check for new files about every hour. When will my data show up? →
- Mode: event files sync as a full refresh of each date folder, so re-runs are always safe. User attribute files sync as new rows only.
- Transfer: files are copied into Auxia-side storage with Google Cloud Storage Transfer Service, then mapped into Auxia’s unified tables.
File requirements
The short version — the full rules are in File source requirements:- One folder per table, with every file in a folder sharing one schema.
- Date folders such as
dt=2026-10-02/let Auxia read only the newest day. - Append-only: never overwrite or delete a file; write corrections as new files.
- CSV needs a header row and comma delimiters.
Limitations
- Whole-file compression (
.parquet.gz,.csv.gz) and archives (.tar.gz) aren’t supported. Client-side encrypted files (such as PGP) are supported only in limited cases. - Avro, ORC, Delta Lake, and Iceberg need the Auxia team rather than the wizard.
- More than about 1 TB per run works, but talk to your Auxia contact before committing to a timeline.
- Dates in file names (rather than folder names) aren’t detected.
- A new connection doesn’t load history automatically. Contact your Auxia point of contact to load a past date range.
- Data in Snowflake or Databricks can be connected by first exporting it to GCS. See Don’t see your source?