After you install Adapty SDK and release the app, you can find your users and subscribers in the Profiles section. But what if you have legacy infrastructure and want to migrate to Adapty? Or just want to see your existing data in Adapty?
Data import is not mandatory
Adapty will automatically grant access levels to the historical users and restore their purchase events once they open the app with the SDK on board. For that use case, there is no need for importing historical data. The import will ensure percise analytics if you have a lot of historical transactions, but generaly not required for the migration.
You can export your data to a CSV file and then import it to Adapty. Let's see how to do that.
|Id of your user
|The date of subscription expiration, i.g. next charging date, datetime with timezone (2020-12-31T23:59:59-06:00)
|Datetime of profile creation (2019-12-31T23:59:59-06:00)
|format ISO 3166-1 alpha-2
|datetime with timezone (2020-12-31T23:59:59-06:00)
|iOS Identifier for advertiser
|It's similar to idfa, but for Android
|The entire iOS receipt file (learn more). When importing historical data with this receipt we use a legacy import mechanism established prior to the introduction of StoreKit 2.
|The original transaction ID or OTID (learn more), used in StoreKit 2 import mechanism. As one user can have multiple OTIDs, it is enough to provide at least one for successful import.
Note: We require In-app purchase API credentials for this import to be set up in your Adapty Dashboard. Learn how to do it here.
|Token of a Stripe object that represents a unique purchase. Could either be a token of Stripe's Subscription (
sub_...) or Payment Intent (
There are 2 groups of required fields: user_id and data identifying purchase for the corresponding platform:
- iOS: apple_receipt_encoded OR apple_original_transaction_id
- Android: google_product_id+google_purchase_token+google_is_subscription
- Web: stripe_token
Without them Adapty won't be able to fetch transactions.
We highly recommend passing the country. If it's not passed, we will use the USD price and the United States country as a fallback.
If you want the cohort analytics to be precise, please specify created_at as well, otherwise we'll have to assume that date from the first purchase date.
- Make sure that the column names are specified and the same as in the table above, check for typos.
- Don't bother adding empty columns for data you don't have.
- Please, make sure there are no extra columns, that are not mentioned in the table.
- Separate values by commas and don't take values in quotation marks.
Once again, please refer to the examples above. If the file is more than 1 GB, please attach a data sample with just ~100 lines so we can check it.
Upload the files to Google Disk (you can compress them, but please keep them separate) and share the link with our team.
In order for us to fetch the prices and price changes for all iOS products, including the legacy products that will never be purchased through Adapty SDK, kindly share the docs with those prices.
You don't need to bother creating the correct format, as it is already provided by Apple. Here is how you can get it from Apple Connect:
- Open the desired subscription
- "View all Subscription Pricing" here
- And "Download" here
Below is an example of a file you should get. We'll understand the products' IDs from the names of the folders that collect the prices, so please name the folders, separately for each product. For some reason, Apple doesn't mention the product name anywhere in the exported file, so it must be done manually. Probably, there will be several folders, please add them to a flat archive to make sure nothing gets lost.
Please, refer to this example.
Finally, please, make sure to set up the App Store price increase logic to avoid any analytics discrepancies. Please, confirm that you've done it in your request to Support. Yes, we really care for the precision of our analytics 🤓
Right now we don't have an automatic tool for that. Please contact us using the chat widget on the dashboard or just email us at [email protected].
Do not worry - importing historical data will not create any duplicates, even if that data overlaps with the one you already have in Adapty.
Updated 13 days ago