Skip to main content
Connectors come in two kinds:
  • Self-serve — you set them up yourself in the Auxia Console with a guided wizard, usually in under 15 minutes.
  • Assisted — you grant access or share data, and the Auxia team completes the setup with you.
New to data ingestion in Auxia? Start with How ingestion works.

Google BigQuery

Self-serve. Tables and views, synced hourly or daily — or more often with the Auxia team. Recognizes GA4, Firebase, Segment, and Mixpanel exports.

Google Cloud Storage

Self-serve for Parquet, CSV, and JSON files. Avro, ORC, Delta Lake, and Iceberg with the Auxia team.

Amazon S3

Self-serve for Parquet, CSV, and JSON files. Avro, ORC, Delta Lake, and Iceberg with the Auxia team.

Amazon Kinesis

Assisted. Real-time streams with a fixed event schema.

​
More connectors

Snowflake

Assisted. Direct connection (recommended), or a scheduled export to GCS.

Databricks

Assisted. Unity Catalog direct read (recommended), or Delta Transfer through Amazon S3.

SFTP

Assisted. Push files to an Auxia-hosted SFTP server, with SSH key authentication.

Google Cloud Pub/Sub

Assisted. Real-time events and user attributes.

Amplitude

Assisted. Auxia pulls your events every 30 minutes (recommended), or Amplitude streams them through Pub/Sub.

Firebase

Self-serve via BigQuery. Connect the Firebase BigQuery export.

​
Your app or website

SDK and Log Events API

Send events from your app or backend as they happen — the freshest data Auxia can get. Needs developer work on your side, and complements a warehouse connection rather than replacing it.
Auxia doesn’t connect to Segment or Mixpanel directly. If their data already lands in your BigQuery, connect it from there — Auxia recognizes Segment, Mixpanel, and GA4 export schemas automatically during mapping.

​
Don’t see your source?

Most sources have a route through an existing connector: For other S3-compatible storage or anything else, contact your Auxia point of contact — Auxia adds integrations based on customer needs.