Do you need to transfer one or more apps from another AppsFlyer account to your own account?
This usually happens when an app owner starts to handle user acquisition internally, instead of an agency that was handling the app's marketing beforehand.
Another typical case is when companies sell their apps to other app owners.
This article explains how this can be done and answers the FAQs related to transferring apps.
Apps Transfering FAQs
Which Accounts May Transfer Apps?
Apps can be transferred between any two consenting AppsFlyer accounts, that have no outstanding unpaid invoices.
Apps cannot be transferred if either account is suspended, or approaching suspension.
Asking to Transfer Apps
Only AppsFlyer admins are permitted to transfer apps between accounts. Contact your dedicated AppsFlyer Customer Success Manager, or write to firstname.lastname@example.org
AppsFlyer requires a written formal email consent, including all names of apps to be transferred, from both account owners involved in the moving.
If both accounts belong to the same company, please state so in your email.
What to do with the Dev Key?
Every account in AppsFlyer has a unique dev key, which MUST be set in the SDK of all new apps to enable attribution.
The receiving account owner can ask to retain the old dev key (default behavior) or to reset the app's dev key to the receiving account's dev key.
For apps with active user bases it is not advisable to reset the dev key, as it causes new data to be collected ONLY for the new app installs, which have the new dev key set in the app's code.
What Happens with the App's Historical Data?
After transferring the app between accounts, its historic data is fully retained and accessible from the new account's dashboard (only).
Note that the data is retained whether the dev key is reset or not.
Account Dependent Features
|Feature||App transfer effect||AppsFlyer recommendation|
|Integrated Partners||All partners configuration persist||
Go over all the active partners setup to verify the configuration and permissions are relevant for your account
|Push API||Push API setup persists||Check it to see if your data is not being sent to other companies against your wish|
The OneLink template is configured on the account level. Therefore the receiving account can't access this setup and edit the template. OneLink URLs based on the old template may also not work in some cases
Make sure the OneLink template is deleted from the giving account before the transfer of the app
|Deep linking||AppsFlyer's deep linking is based on the OneLink template, and therefore may face the same problems following an app transfer||See recommendation for OneLink template above|
|Audiences||Audiences are configured on the account level and stop updating daily after the transfer||Redefine all required audiences in the receiving account after the transfer|