App settings
You can navigate to the General tab of the App Settings page to manage your app's behavior, appearance, and revenue sharing. Here, you can customize your app's name and icon, manage your Adapty SDK and API keys, set your Small Business Program status, and choose the timezone for your app's analytics and charts.
1. App details
Choose a unique name and icon that represent your app in the Adapty interface. Please note that the app name and icon will not affect the app's name and icon in the App Store or Google Play. Also, make sure to select an appropriate App Category that accurately reflects your app's purpose and content. This will help users discover your app and ensure it appears in the appropriate app store categories.
2. Member of Small Business Program and Reduced Service Fee
If you're a member of the Apple Small Business Program and/or Google's Reduced Service Fee program, you can let Adapty know by specifying the period that you are a member. Adapty will adjust the commission rate accordingly, so you can keep more of your revenue. Please note that this setting applies only to future transactions, and you need to update it if your Small Business Program status changes. You can learn more about the App Store Small Business Program and Google's Reduced Service Fee.
3. Reporting timezone
Choose the timezone that corresponds to the location where you're based, or where your app's analytics and charts are most relevant. We recommend using the same timezone as your App Store Connect or Google Play Console account to ensure consistency. Please note that this timezone setting does not affect third-party integrations in the Adapty system, which use the UTC timezone.
You can access the timezone settings in the Reported timezone section of the General Tab on the App Settings page. You can also choose to set the same timezone for all the apps in your Adapty account by checking the corresponding box.
4. Installs definition for analytics
Choose what is defined as a new install event in analytics:
| Base | Description |
|---|---|
| New device_ids | (Recommended) Each installation of the app from the store on a device is counted as a new install. This includes both first-time installs and reinstalls. Installs are counted per device ID and are not affected by user authentication. Creating a profile (on SDK activation or logout), logging in, or upgrading the app does not generate additional install events. For example, if the same app is installed on 5 different devices, you will see 5 installs in analytics. |
| New customer_user_ids | This option is intended for apps that identify users in Adapty. For logged-in users, only the first installation associated with a customer user ID is counted as an install. Installations on additional devices are not counted as new installs. Anonymous users (users who have not logged in) are not counted in analytics. Reinstalling the app or logging in again does not create additional installs. App stores and attribution platforms (such as App Store Connect, Google Play Console, and AppsFlyer) use a device-based approach to counting installs. If you count installs by customer user IDs in Adapty, install numbers may differ from these external services. ⚠️ If you do not identify users in Adapty, no installs will be counted with this option enabled. |
| New profiles in Adapty | (Legacy) Every app installation, reinstallation and anonymous profiles created during logouts are counted as new installs. |
Keep in mind that this option only affects the Analytics page and does not impact the Overview page, where you can configure the view separately.
5. App Store price increase logic
To maintain accurate data and avoid discrepancies between Adapty analytics and App Store Connect results, it is important to select the appropriate option when adjusting configurations related to price increases in App Store Connect.
So you can choose the logic that will be applied to subscription price increases in Adapty:
- Subscription price for existing users is preserved: By selecting this option, the current price will be retained for your existing subscribers, even if you make changes to the price in the App Store Connect. This means that existing subscribers will continue to be billed at their original subscription price.
- When the subscription price is changed in App Store Connect, it changes for existing subscribers: If you choose this option, any price changes made in the App Store Connect will be applied to your existing subscribers as well. This means that existing subscribers will be charged the new price reflecting the updated pricing set in the App Store Connect.
It is important to consider that the selected option not only affects analytics in Adapty but also impacts integrations and overall transaction handling behavior.
Please ensure that you select the designated option that aligns with your desired approach to handling subscription prices for existing subscribers. This will help maintain accurate data and synchronization between Adapty analytics and the results obtained from the App Store Connect.
6. Sharing paid access between user accounts
Main article: Sharing paid access between user accounts
The Sharing paid access between user accounts setting determines what Adapty does when more than one user profile attempts to access the same purchase. You can specify a separate access sharing setting for the sandbox environment.
If your application doesn't authenticate users, you can ignore this setting. Anonymous profiles associated with the same store account always share their access level.
| Setting | Best for | Description |
|---|---|---|
| Enabled (default) | Applications without authentication. | All user profiles associated with the same store account share the access level. The user can reinstall the app, access the app from a different device, log in and out. |
| Transfer access to new user | Applications that allow purchases with or without authentication. | Adapty limits purchase access to 1 customer ID at a time. When a new authorized customer ID accesses the application, the old one loses access. |
| Disabled (use with caution) | Applications with mandatory authentication. | No access level sharing. Each purchase ties the product to the currently active customer ID. Without mandatory authentication and hand-coded purchase access control, your customers can lose access to their products, and your application can fail store review. |
7. SDK and API keys
Use a Public SDK key to integrate Adapty SDKs into your app, and a Secret Key to access Adapty's Server API. You can generate new keys or revoke existing ones as needed.
8. Test devices
Specify the devices to be used for testing to ensure they get instant updates for paywall or placement changes, bypassing any caching delays. For more information, see Testing devices.
9. Cross-placement variation stickiness
Define how long after a test completion a user is still served with the variants in the test. This affects analytics accuracy and user experience — as serving a user with a different offer than what they have seen before might influence their decision to buy.
The maximum and default stickiness period is 90 days.
Consider the following:
- Changing this setting will affect all the users who previously received a variation. They will instantly qualify for a new paywall when they see a placement, which can spoil the results of your running A/B tests.
- If the stickiness period is over for a user, they can be served with a new paywall or A/B test. However, even then, they won't be able to be a part of any other cross-placement test ever.
10. Delete the app
If you no longer need an app, you can delete it from Adapty.
Please be aware that this action is irreversible, and you won't be able to restore the app or its data.