Build With RevenueCat

Build a customized mobile subscription business with RevenueCat. We do the heavy lifting of normalizing subscribers from any source and maintain a single source of truth for subscription status, so you can get back to building your app.

RevenueCat is a powerful, secure, reliable, and free to use in-app purchase server with global support. All you need to get started is an API key.

Get Started    REST API Endpoints

ETL Exports

Data deliveries of all of your apps' transaction data

πŸ‘

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 .csv files delivered daily.

Setup Instructions

Transaction Format

πŸ“˜

All dates and times are in UTC.

Header

Can be null

Comments

rc_original_app_user_id

Can be used as a unique user identifier to find all of a user's transactions.

rc_last_seen_app_user_id_alias

Can be used together with rc_original_app_user_id to match transactions with user identifiers in your systems.

country

βœ…

Last seen country of the subscriber.

product_identifier

The product identifier that was purchased.

start_time

Purchase time of transaction.

end_time

βœ…

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).

store

The source of the transaction. Can be app_store, play_store, stripe, or promotional.

is_auto_renewable

true for auto-renewable subscriptions, false otherwise.

is_trial_period

true if the transaction was a trial.

is_in_intro_offer_period

true if the transaction is in an introductory offer period.

is_sandbox

true for transactions made in a sandbox environment.

price_in_usd

βœ…

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.

takehome_percentage

0.7 or 0.85. Use this to calculate the proceeds of a transaction.

store_transaction_id

orderId or transaction_identifier. ​Can be used as unique id.

original_store_transaction_id

orderId of first purchase or original_transaction_id. Can be used to find all related transactions for a single subscription.

refunded_at

βœ…

When a refund was detected, null if none was detected. Can be checked for existence to indicate transactions which have been refunded.

unsubscribe_registered_at

βœ…

When we detected an unsubscribe (opt-out of auto renew).

billing_issues_detected_at

βœ…

When we detected billing issues, null if none was detected.

purchased_currency

βœ…

The currency that was used for the transaction.

price_in_purchased_currency

βœ…

The product's price in the currency that was used for the transaction.

entitlement_identifiers

βœ…

An array of entitlements that the transaction unlocked or null if it didn't unlock any entitlements.

renewal_number

Always starts at 1. Trial conversions are counted as renewals. is_trial_conversion is used to signify whether a transaction was a trial conversion.

is_trial_conversion

If true, this transaction is a trial conversion.

presented_offering

βœ…

The offering presented to users. Can be used to filter Experiment transactions.

reserved_subscriber_attributes

βœ…

The reserved subscriber attributes set for the subscriber. Keys begin with $.

custom_subscriber_attributes

βœ…

The custom attributes set for the subscriber.

platform

βœ…

Last seen platform of the subscriber.

πŸ“˜

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.

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.
  • Google returns only 90 days of recent transaction history, so some old transactions maybe missing if Google fetch tokens were imported.
  • 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

Sample Queries

The following sample queries are in Postgresql.

-- Active trials
SELECT
  COUNT(*)
FROM
  transactions
WHERE
  end_time > NOW()
  AND is_trial_period = TRUE
  AND renewal_number = 1
  AND is_sandbox = FALSE
  AND refunded_at IS NULL;
-- Active subscriptions
SELECT
  COUNT(*)
FROM
  transactions
WHERE
  end_time > NOW()
  AND is_trial_period = FALSE
  AND is_sandbox = FALSE
  AND refunded_at IS NULL;

-- The RevenueCat charts exclude promotional transactions.
-- you can include the following filter to exclude promotional
-- transactions from your queries as well
product_identifier NOT ILIKE 'rc_promo%'
-- Revenue past 28 days (USD)
SELECT
  SUM(price)
FROM
  transactions
WHERE
  start_time > (CURRENT_DATE - INTERVAL '28 days')
  AND is_sandbox = false;

Updated 11 days ago


ETL Exports


Data deliveries of all of your apps' transaction data

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.