Skip to main content

Scheduled Data Exports

👍Pro Integration

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.

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. The exports use a semicolon delimiter, so if they do not appear to be formatted correctly when viewed as spreadsheets, you may need to change your delimiter settings in the spreadsheet software.

Setup Instructions

📘

Customers on our Enterprise plan have the option to receive data exports more frequently than once per day when receiving new and updated transactions only. Contact your Customer Success Manager with questions, or visit our Pricing Page to learn more.

Version Change Log

Transaction Format

Applicable to the latest version

📘

All dates and times are provided in UTC.

HeaderDescriptionTypeExample valueCan be null
rc_original_app_user_idCan be used as a unique user identifier to find all of a user's transactions.string$RCAnonymousID:87c6049c58069238dce29853916d624c
rc_last_seen_app_user_id_aliasCan be used together with rc_original_app_user_id to match transactions with user identifiers in your systems.string$RCAnonymousID:87c6049c58069238dce29853916d624c
countryStore country of a transaction when known, or an IP-based estimate of a subscriber's country when not known.stringGB
country_sourcefrom_sdk when the store country of a transaction is known, or estimated when country is sourced from an IP-based estimate.stringfrom_sdk
product_identifierThe product identifier that was purchased.stringrc_subscription_monthly
product_display_nameThe display name of the product identifier if one has been setstringMonthly $9.99
product_durationThe standard duration of the product if one is known by RevenueCat. May be null if RevenueCat does not know the authoritative duration.

product_duration does not represent the trial or introductory period length of a transaction, it only represents the standard duration of the product that's been subscribed to.
stringP1M
start_timePurchase time of transaction.datetime2023-01-01 08:27:06
end_timeExpected expiration time of subscription. Null when is_auto_renewable = false
For Google Play, end_time can be before start_time to indicate an invalid transaction (e.g. billing issue).
datetime2023-02-01 08:27:06
grace_period_end_timeExpiration 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.datetime2023-02-17 08:27:06
effective_end_timeSingle reference point of a subscriber’s expiration and entitlement revocation; inclusive of each store’s logic for refunds, grace periods, etc.datetime2023-02-17 08:27:06
storeThe source of the transaction. Can be app_store, play_store, stripe, or promotional.stringplay_store
is_auto_renewabletrue for auto-renewable subscriptions, false otherwise.booleantrue
is_trial_periodtrue if the transaction was a trial.booleanfalse
is_in_intro_offer_periodtrue if the transaction is in an introductory offer period.booleanfalse
is_sandboxtrue for transactions made in a sandbox environment.booleanfalse
price_in_usdThe revenue (converted to USD) generated from the transaction after accounting for full and partial refunds. Can be null if product prices haven't been collected from the user's device.float0
purchase_price_in_usdThe gross revenue (converted to USD) generated from the transaction. Remains set for refunded transactions. Can be null if product prices haven't been collected from the user's device.float9.99
takehome_percentage[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 tax_percentage and commission_percentage to calculate proceeds instead. Learn more here.
float0.7
tax_percentageThe 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.float0.1442
commission_percentageThe 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.float0.15
store_transaction_idorderId or transaction_identifier.string123456789012345
original_store_transaction_idorderId of first purchase or original_transaction_id. Can be used to find all related transactions for a single subscription.string011223344556677
refunded_atWhen a refund was detected, null if none was detected. Is not set in the case of upgraded transactions for which the App Store issues a partial refund.datetime2023-02-20 05:47:55
unsubscribe_detected_atWhen we detected an unsubscribe (opt-out of auto renew).datetime2023-02-16 14:17:10
billing_issues_detected_atWhen we detected billing issues, null if none was detected.datetime2023-02-01 08:27:15
purchased_currencyThe currency that was used for the transaction.stringGBP
price_in_purchased_currencyThe revenue (in the purchased currency) generated from the transaction after accounting for full and partial refunds. Can be null if product prices haven't been collected from the user's device.float0
purchase_price_in_purchased_currencyThe gross revenue (in the purchased currency) generated from the transaction. Remains set for refunded transactions. Can be null if product prices haven't been collected from the user's device.float3.99
entitlement_identifiersAn array of entitlements that the transaction unlocked or null if it didn't unlock any entitlements.string array["membership", "full_access"]
renewal_numberAlways starts at 1. Trial conversions are counted as renewals. is_trial_conversion is used to signify whether a transaction was a trial conversion.integer2
is_trial_conversionIf true, this transaction is a trial conversion.booleantrue
presented_offeringThe offering presented to users.stringDefault Offering
ownership_typeWill be PURCHASED when a recorded transaction results from the subscriber’s direct purchase of it, or FAMILY_SHARED when a recorded transaction results from the subscriber having received it through Family Sharing.

NOTE: The FAMILY_SHARED designation is only supported on App Store transactions.
stringPURCHASED
reserved_subscriber_attributesThe reserved attributes set for the Customer (subscriber). Keys begin with $.string JSON{"$ip": {"value": "203.78.120.117", "updated_at_ms": 1672549200}, "$gpsAdId": {"value": "80480bdc-06e0-11ee-be56-0242ac120002", "updated_at_ms": 1672549200}, "$androidId": {"value": "12345a9876b4c123", "updated_at_ms": 1673097132390}}
custom_subscriber_attributesThe custom attributes set for the Customer (subscriber).string JSON{"feature_setting": {"value": "1", "updated_at_ms": 1672549200}, "survey_response": {"value": "2", "updated_at_ms": 1599112814785}}
platformLast seen platform of the subscriber.stringandroid
experiment_idThe unique ID of the Experiment that the subscriber is or was enrolled in. Will be null if the subscriber has not been enrolled in an experiment. Learn more about Experiments here.stringprexp3a8a234abc
experiment_variantThe value of the Experiment variant that the subscriber is or was enrolled in. a represents the Control, and b represents the Treatment. Will be null if the subscriber has not been enrolled in an experiment. Learn more about Experiments here.stringa
updated_atThe last time an attribute of the transaction was modified.datetime2023-02-20 05:47:55
offer*The offer that was used for a transaction (if applicable).stringblack_friday_discount
offer_type*The type of offer that was used for a transaction (if applicable).stringoffer_code
first_seen_time*The time the customer was first seen by RevenueCat.datetime2023-01-01 03:00:00
auto_resume_time*The time when a Play Store subscription would resume after being paused.datetime2023-03-20 03:00:00

*Available only on our most recent export version

A note on transaction data

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 export files.
  • Apple and Google do not always provide the transaction price directly, so we rely on historical data & store APIs. This may result in inaccuracies if receipts were imported, or if a product price was increased before your App Store Connect API Key was added.
  • 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. due to a refund or billing issue). You should recompute metrics for past time periods periodically to take these changes into account. You can use the updated_at field to detect if a transaction may have changed since a prior export.
  • Data is up to date as of the export beginning to be generated. Thus, changes could occur between the start of an export generating and its delivery that would not be reflected in that export.

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 date and time set in Next export start time via the dashboard is when the next export should start getting generated and is not when the next export should be delivered.

Updating to the latest version

If you're on an older version of our exports, updating is easy:

  1. Open app.revenuecat.com
  2. Navigate to your Project in Project Settings
  3. Click on your Scheduled Data Exports integration in the “Integrations” side panel
  4. Click UPDATE TEMPLATE
  5. After confirming that your data pipeline is configured to ingest the described changes, click UPDATE in the confirmation modal to complete the update.

Image

⚠️Data Format Changes

Please note that Version 4 and all subsequent templates include data format changes which must be incorporated into your data pipeline before updating. Learn more here.

Handling updated transactions correctly

We strongly recommend keeping the option to "Receive new and updated transactions only" enabled to significantly reduce the amount of data that you need to process in each daily export.

Image

However, handling transaction updates can be tricky, so consider these tips to make it easier:

  1. For most stores, store_transaction_id will be unique for each transaction, but for Stripe it is not; so for best results we recommend treating every unique set of [store_transaction_id + renewal_number] as a unique transaction.
  2. Instead of overwriting prior transaction states when receiving an updated transaction, considering adding them as new rows to your output table and setting a property like is_latest to ensure you're never double-counting different versions of the same transaction. Or, you could set an ingested_time property to order the transactions by the most recent version you received from RevenueCat.
  3. When in doubt, use updated_at (provided by RevenueCat in your export) as a reference point to determine the latest version of a transaction if you have multiple prior versions and can't otherwise confidently determine which one is latest.

Sample queries for RevenueCat measures

You can use the following sample queries (written in Postgresql) as starting points for reproducing common RevenueCat measures.

-- Active Subscriptions as of a specified date

SELECT
COUNT(*)
FROM
[revenuecat_data_table]
WHERE date(effective_end_time) > [targeted_date]
AND date(start_time) <= [targeted_date]
AND is_trial_period = 'false'
AND DATE_DIFF('s', start_time, end_time)::float > 0)
AND 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.

Sample queries for customized measures

Scheduled Data Exports are a powerful way to add your own customizations on top of the core measures provided by RevenueCat. Check out the following sample queries (written in Postgresql) for some ideas.

-- How many Active Subscriptions do I have with a given custom attribute value?

SELECT
COUNT(*)
FROM
[revenuecat_data_table] rc

WHERE date(effective_end_time) > [targeted_date]
AND date(start_time) <= [targeted_date]
AND is_trial_period = 'false'
AND DATE_DIFF('s', start_time, end_time)::float > 0)
AND ownership_type != 'FAMILY_SHARED'
AND store != 'promotional'
AND is_sandbox != 'true'
AND json_extract_path_text(custom_subscriber_attributes, '[custom_attribute_key].value') = [custom_attribute_value]