Sign in →

Data Exports

Export platform datasets to S3, cloud storage, and warehouses — on demand or on a recurring schedule — in Parquet, CSV, or JSONL, with partitioning and connection testing.

Updated 2026-07-29Suggest edits

Data Exports

Data Exports (Intelligence → Data Exports) streams Aforo datasets out to your own storage and warehouses. The page is organized around three concepts.

Three concepts

TabWhat it manages
DestinationsConfigured targets (S3, signed URL, …) with connection testing
ExportsAd-hoc and triggered export jobs with live progress
SchedulesRecurring, cron-driven exports

Datasets

usage_events, usage_daily, invoices, invoice_line_items, subscriptions, customers, wallet_transactions, payment_transactions, credit_notes, bill_runs, bill_run_event_index, and audit_log.

Formats & partitioning

  • Formats — Parquet, CSV, JSONL.
  • Partitioning — NONE, DAY, HOUR, or CUSTOMER.

Destinations

StatusMeaning
ACTIVEConfigured and usable
INACTIVEDisabled
ERRORLast connection test failed

Eight destination types are live: S3, SIGNED_URL, GCS, AZURE_BLOB, SNOWFLAKE, BIGQUERY, REDSHIFT, and DATABRICKS. Use Test on a destination to validate credentials before relying on it.

The export wizard

The unified wizard walks you through Destination → Data → Filters → Format → Cadence → Review. Cadence is the key choice:

CadenceBehavior
NowOne-off export over a date range
ScheduleRecurring, with cron + timezone + lookback window
BothCreate a schedule and run it immediately

Export jobs move through QUEUED → RUNNING → COMPLETED (or FAILED / CANCELLED), tracking rowsExported and bytesExported. The Exports header shows a live summary ("N jobs · N running · N schedules · N destinations").

ℹ

Job creation is idempotent — the wizard sends an idempotency key, so a retried submit won't create a duplicate export.