The App Settings page enables configuration of functions that affect the way app data is displayed and processed in AppsFlyer. These settings affect data from all media sources. Only app owers can access the setting page.
To open the app settings page, in AppsFlyer, go to Configuration > App Settings.
After making changes to the app settings ensure that you save the changes. To do so, click
SDK dev key
The AppsFlyer Dev key is a unique key per account, which is essential for the success of SDK integrations on all platforms. Developers can get the key from the App settings page.
Define loyal user trigger
In the Analytics section you can define the parameter of a loyal user. By default, a loyal user is defined as a user who has opened the app 3 times or more during its lifetime. If you select one of the configured events in the dropdown menu, loyal users are defined accordingly.
This change is reflected retroactively, so upon selecting a new event to represent loyalty, all the historic loyal user data is re-calculated to reflect the change.
The default loyal user definition is highly indicative of user quality. However, it is also easy to replicate by fraudsters. AppsFlyer recommends using a more complex Loyal user trigger to increase the reliability of this KPI. For more details, read this.
App store country
The App Store Country setting allows you to select the country in which your app is available.
When the app is not available on the default US app store, you must select the country where the app is available. Otherwise, AppsFlyer redirects users to their local country's App Store, based on resolving their devices IP. In the rare cases where this IP is unusable AppsFlyer redirects to the default App store in the US.
1. If the app is not available in the set country on the App Settings page, AppsFlyer is not able to retrieve and update your app's icon on the dashboard, causing it to seem "Pending".
2. For iOS apps that are available in more than one country but not in the US, set the app store country to one of the countries where the app is available. By doing so, even if the app is not available in the US, the App store redirects users to their country stores.
By default, all app data is reported based on the UTC +0 time-zone. The time-zone setting here allows for changing the default time zone to any local time zone, to make data alignment easier.
Selecting time zone for your app (other than utc +0):
When selecting a time zone for your app, the following conditions apply:
- You can change the time zone for either new or live apps
- Time zone change takes effect at midnight UTC +0, upon which the dashboard screens, alongside the raw data reports, update to reflect the change
- Changing the time zone for an app affects the view of the app owners, as well as for all agencies and partners that have access to the app's dashboard
Changing the time zone after initial selection:
If you decide to make an additional change to the time zone, you MUST follow these instructions:
- Ensure at least 48 hours have passed since the last time zone selection
- Change the time zone to UTC +0
- You must then wait an additional 48 hours before selecting the new time zone
For more details about localization, see here.
By default, the app's currency is set to USD. You can change the default currency via your App Settings page, under Localization.
Below are the ways in which the data is presented in the various dashboard views and reports.
Dashboard and Raw Reports
The dashboard and Raw Reports present all of your data in your selected currency.
Data from Push API shows:
- Selected Currency
- The Currency in USD
The Pull API shows the currency in USD by default. To receive the data in your preferred currency, please add the following to your request link:
- Currency change is only available to apps with no revenue or cost.
- For new apps, the currency can also be set when the app is added.
The Re-attribution window is a time frame starting from the first install time during which re-installs cannot be attributed as new installs. You can now change this window's value from the default 3 months to anything between 1-24 months. For more details click here.
To enable or disable Retargeting campaigns measurement, with any supporting media source, turn on Enable Retargeting Campaign Measurement.
Note, that if you don't enable the Retargeting Campaign Management, re-installs that take place during the re-attribution window are not counted.
For more information about retargeting click here.
Minimum time between re-engagement conversions
Turning on Enable Retargeting Campaign Measurement also reveals the Minimum time between re-engagement conversions setup.
Following users re-engagements with your app, AppsFlyer attributes their in-app events to the retargeting network, during the Re-engagement window. This helps you to measure the effectiveness of retargeting campaigns.
However, if another network brings a new re-engagement during this window, it replaces the last re-engagement and all subsequent events are attributed to the new network. The Minimum time between re-engagement conversions setup enables you to set a time frame during which AppsFlyer ignores new re-engagements.
You can set this window's time period in hours (1-23), days (1-30), or leave it disabled (None).
These settings do not affect the time between install and re-engagement.
iOS apps that implement the iOS uninstall attribution feature need to upload the P12 certificate here.
Android apps require a Firebase/GCM Server Key to be defined here for android uninstall attribution.
Enable ip masking
You can toggle the On/Off button to enable app owners to mask the end-users' device IP addresses in the raw data reports.
For more details about IP Masking, see here.
iOS 10.3 redirect fallback
For iOS 10.3 and above users only. Details here.
Change app name
The account's admin can determine the name of your app, which is then displayed throughout the dashboard and data reports. This is especially useful if you have different versions of the same app, for example for regional distribution reasons.
Note that while this change affects the display of the app, the app ID, used to identify the app when using various AppsFlyer APIs, remains the same.
app names are limited to 50 characters.