The ETL Export integration is available on the Pro plan.
RevenueCat can automatically send data deliveries of all of your apps' transaction data to various cloud storage providers. These are in the form of gzip compressed .csv files delivered daily.
All dates and times are in UTC.
|Header||Can be null||Comments|
|Can be used as a unique user identifier to find all of a user's transactions.|
|Can be used together with |
|✅||Last seen country of the subscriber.|
|The product identifier that was purchased.|
|Purchase time of transaction.|
|✅||Expected expiration time of subscription. Null when |
For Google Play,
|✅||Expiration time of a grace period (if applicable) for a subscription. Will remain set while a subscription is in its grace period, or if it exited its grace period without renewing. Null when a subscription is not in a grace period or expiration was not due to a grace period.|
|✅||Single reference point of a subscriber’s expiration and entitlement revocation; inclusive of each store’s logic for cancellations, grace periods, etc.|
|The source of the transaction. Can be |
|✅||The gross revenue generated from the transaction. All prices are converted to USD. Can be null if product prices haven't been collected from the user's device.|
|DEPRECATED: The estimated percentage of the transaction price that will be paid out to developers after commissions, but before VAT and DST taxes are taken into account. (will be either 0.7 or 0.85)|
We recommend using
|The portion of a transaction’s price that will be deducted by the store for taxes. VAT & Digital Services Taxes may be withheld by stores depending on the store and country. To learn more about how RevenueCat estimates taxes, click here.|
|The portion of a transaction’s price that will be detected by the store for commission. In stores where taxes are deducted before commission, this value will not equal the published commission from a store, because that commission is calculated on the post-tax revenue.|
|orderId or transaction_identifier. Can be used as unique id.|
|orderId of first purchase or |
|✅||When a refund was detected, |
|✅||When we detected an unsubscribe (opt-out of auto renew).|
|✅||When we detected billing issues, |
|✅||The currency that was used for the transaction.|
|✅||The product's price in the currency that was used for the transaction.|
|✅||An array of entitlements that the transaction unlocked or |
|Always starts at 1. Trial conversions are counted as renewals. |
|✅||The offering presented to users. Can be used to filter Experiment transactions.|
|✅||For App Store transactions: can be |
|✅||The reserved subscriber attributes set for the subscriber. Keys begin with |
|✅||The custom attributes set for the subscriber.|
|✅||Last seen platform of the subscriber.|
*Available only on our most recent ETL export version
Re-enable integration to update to latest version
If your exports don't contain all of the columns above, you may be on an older export version. To update to the latest version disconnect, and re-connect the integration from the RevenueCat dashboard.
All transaction data is based on the store receipts that RevenueCat has received. Receipts often have inconsistencies and quirks which may need to be considered. For example:
- The expiration date of a purchase can be before the purchase date. This is Google's way of invalidating a transaction, for example when Google is unable to bill a user some time after a subscription renews. This doesn’t occur on iOS.
- If you migrated to RevenueCat, Google subscriptions that were expired for more then 60 days before being migrated will not have transaction histories in ETL files.
- Apple and Google do not provide the transaction price directly, so we must rely on historical data for the products that we have. This isn’t 100% accurate in cases where the prices were changed or receipts were imported.
- Renewal numbers start at 1, even for trials. Trial conversions increase the renewal number.
- Data is pulled from a snapshot of the current receipt state, this means that the same transaction can be different from one delivery to another if something changed, e.g.refunds, and billing issues. You should recompute metrics for past time periods periodically to take these changes into account.
We try to normalize or at least annotate these quirks as much as possible, but by and large we consider receipts as the sources of truth, so any inconsistencies in the transaction data can always be traced back to the receipt
The following sample queries are in Postgresql.
-- Active Trials as of your [targeted_date] SELECT COUNT(*) FROM [your_table_name] WHERE date(effective_end_time) > [targeted_date] AND date(start_time) <= [targeted_date] AND is_trial_period = 'true' AND (effective_end_time IS NULL OR DATE_DIFF('s', start_time, effective_end_time)::float > 0) AND (ownership_type IS NULL OR ownership_type != 'FAMILY_SHARED') AND store != 'promotional' AND is_sandbox <> 'true' -- The RevenueCat Active Trials chart excludes -- promotional transactions and transactions resulting from family sharing -- since they do not reflect auto-renewing future payments.
-- Active Subscriptions as of your [targeted_date] SELECT COUNT(*) FROM [your_table_name] WHERE date(effective_end_time) > [targeted_date] AND date(start_time) <= [targeted_date] AND is_trial_period = 'false' AND (effective_end_time IS NULL OR DATE_DIFF('s', start_time, effective_end_time)::float > 0) AND (ownership_type IS NULL OR ownership_type != 'FAMILY_SHARED') AND store != 'promotional' AND is_sandbox <> 'true' -- The RevenueCat Active Subscriptions chart excludes trials, -- promotional transactions, and transactions resulting from family sharing -- since they do not reflect auto-renewing future payments.
-- Revenue generated on [targeted_date] SELECT SUM(price) as revenue FROM [your_table_name] WHERE date(start_time) = [targeted_date] AND is_trial_period = 'false' AND (effective_end_time IS NULL OR DATE_DIFF('s', start_time, effective_end_time)::float > 0) AND (ownership_type IS NULL OR ownership_type != 'FAMILY_SHARED') AND store != 'promotional' AND is_sandbox <> 'true' -- Transactions which are refunded can be identified through the refunded_at field. -- Once refunded, price will be set to $0, so revenue will always be net of refunds.
Updated 8 days ago