Scheduled Data Exports
Export Transactions, In-App Currency, and Ad Monetization Metrics data to cloud storage or email on a schedule, with selectable columns per feed
Scheduled Data Exports are available to all users signed up after September '23, the legacy Grow and Pro plans, and Enterprise plans. If you're on a legacy Free or Starter plan and want to access this integration, migrate to our new pricing via your billing settings.
Scheduled Data Exports deliver your apps' data to a cloud storage provider or to email on a schedule you control. Use them to analyze RevenueCat data in your own systems.
How Scheduled Data Exports work
Each integration connects RevenueCat to one destination. On that integration, you enable one or more feeds, which are datasets that each have their own column catalog. You also choose the columns to include, the delivery cadence, and whether to receive CSV or Parquet files. At each scheduled run, RevenueCat delivers the files for every enabled feed to your destination.
Connection types
Feeds
A feed is a dataset that RevenueCat exports on a schedule. Each feed has its own column catalog in the dashboard and lands in its own location in your storage destination.
The feeds available today are listed below. Each feed has its own page with its columns and delivery behavior.
| Feed | Description | Folder |
|---|---|---|
| Transactions | Per-transaction Customer and revenue data. | None |
| In-App Currency | Per-row in-app currency ledger: balance adjustments with running balance. | virtual_currency |
| Ad Monetization Metrics (beta) | Daily ad metrics per app and Customer. | ad_monetization_metrics |
Each feed writes to <base>/<folder>/<date>/<folder>_<timestamp>.<ext>, so feeds never collide in the same destination. The exception is Transactions, which writes to <base>/<date>/transactions_<timestamp>.<ext> to keep existing integrations' paths stable.
<base> is the optional path prefix you configure on the integration (empty by default), and <date> is a dated subfolder such as 2023-01-01/. Parquet and multi-file deliveries use folder-based names instead of the single-file _<timestamp> suffix.
Enable feeds from the integration settings in the dashboard. You can enable any combination of the available feeds on a single integration.
All feeds on an integration use the same destination. For cloud storage, you configure the bucket and credentials once, and each feed delivers to that bucket under its own path. For Email, you configure the recipient list once, and every feed sends download links to those addresses.
Selecting columns
Each feed has a column catalog that lists every available column for that feed. You choose which columns belong in each feed's export. When you save, future deliveries reflect your selection, and past exports aren't rewritten. The default selection covers the most commonly used fields; you can expand or trim it at any time.
For step-by-step instructions, see Selecting columns for an export.
Export frequency
By default, exports run once per day. How much data each delivery contains depends on the feed:
- Incremental feeds can send only new and updated rows when Receive new and updated transactions only is enabled, which reduces the volume you process per delivery. On Enterprise plans, these feeds can be delivered every 4, 6, 8, 12, or 24 hours. For any cadence outside those options, contact your Customer Success Manager or visit our pricing page.
- Full-snapshot feeds re-export the entire dataset on each run and don't support incremental delivery.
Each feed's delivery behavior is noted on its feed page, linked from the Feeds table.
The date and time set in Next export start time is when the next export should start being generated, not when it will be delivered.
Output format
Scheduled Data Exports can deliver CSV or Parquet files. You can change the format from the integration settings in the dashboard.
CSV exports are gzip compressed, comma-delimited, and by default produced as a single file per delivery. For CSV exports larger than approximately 1 GB, enable Split export into multiple files to break each delivery into smaller files.
Parquet exports use Snappy compression and always produce multiple files per delivery; RevenueCat doesn't merge them.