At a Glance:
Application settings provide flexibility to make adjustments to your app’s configuration even after the initial setup. If you need to update parameters like currency, category, or re-attribution window, you can do so from the Application Settings panel.
Application Settings and Modifiable Parameters.
App Details
Update your application information and details here.
Application Name
If your application name has changed and you want it to reflect within the Apptrove platform, simply edit and update the name in the settings.
Category
Each application belongs to a specific category. If needed, you can update your app’s category by selecting a new one from the available drop-down list.
Currency
If your business has started dealing with a different currency, you can modify the currency setting to reflect the latest one you are using.
Changing the app currency impacts how revenue and monetary values are displayed across the platform.
Points to Note
Updating the currency affects reports, dashboards, event revenue, cohort reports, and exports
Historical and future revenue data will be shown in the newly selected currency
It is recommended to verify your currency selection before running live campaigns
SDK Types
SDK (Software Development Kit) types define how your application interacts with tracking and analytics services. Selecting the right SDK type ensures proper data collection and attribution.
Minimum Duration Settings
Set the minimum duration between sessions in either minutes or hours, depending on how you wish to define a session within your app.
Attribution Settings
Attribution settings help Apptrove determine which campaign, partner, or media source should receive credit for an install, re-engagement, or event. By configuring these windows, you can control how long Apptrove should consider a click, impression, or reinstall eligible for attribution.
Attribution Windows
Click-Through Attribution Window
This defines the maximum time between an ad click and app install for the install to be credited to that campaign.
How it works
User clicks an ad
User installs and opens the app within the configured window
The install is attributed to that media source
If the install happens after this window expires, it is treated as organic. A lookback window typically defines the maximum time after a click within which an install can be attributed.
Example
Click window = 7 days
User clicks an ad on Day 1
Installs on Day 5 → Attributed
Installs on Day 10 → Organic
View-Through Attribution WindowThis defines the maximum time between viewing an ad (without clicking) and installing the app.
How it works
User sees an ad impression
Does not click
Later installs the app within the configured window
The install is attributed to that impression
View-through attribution typically uses a shorter default window, often around 24 hours.
Example
View window = 24 hours
User views an ad at 10 AM
Installs at 8 PM → Attributed
Installs after 24 hours → Organic
Note: If both a click and an impression exist, click attribution takes priority over impression attribution.
Re-Engagement Window
This defines how long a retargeting campaign continues to receive credit for user activity after an existing user reopens the app through a retargeting campaign.
How it works
Existing user clicks on a retargeting campaign
Opens the app
Events performed during the configured window are attributed to that retargeting campaign
Example
Re-engagement window = 30 days
User re-engages today
Any in-app events during the next 30 days are credited to that retargeting campaign
Re-engagement windows commonly default to 30 days in attribution platforms.
Re-Attribution Window
This defines how long Apptrove considers a reinstall as part of the previous install instead of counting it as a new user acquisition.
How it works
User installs the app
Uninstalls it
Reinstalls within the re-attribution window
If the reinstall happens within this period:
It is treated as a reinstall, not a new install
If the reinstall happens after the window expires:
It is treated as a new install
Re-attribution windows often default to around 90 days.
Example
Re-attribution window = 90 days
User installs on Day 1
Reinstalls on Day 60 → Reinstall
Reinstalls on Day 120 → New Install
Unique Key for Uninstall Identifier
To track uninstalls, you can choose specific application events from the drop-down and map them accordingly for data tracking and analysis.
Post Analysis of Fraud
Post Analysis of Fraud allows Apptrove to continue monitoring attributed installs and events for suspicious activity even after the initial attribution is completed.
This helps identify fraud patterns that may appear later, such as:
Unusual event spikes
Abnormal user behavior
Delayed fraud signals
Fraud Analysis Window
This window defines how long Apptrove should continue analyzing installs and events for fraudulent activity after attribution.
Example:
If the fraud analysis window is set to 7 days, Apptrove will continue checking that the install and its related events for fraud signals for the next 7 days.
Note: In case your application is not live, you can choose to "Disable" the live mode. Also, you cannot change or modify the URL, operating system, or Timezone for your application
Whitelisting Device IDs
Manage your list of trusted device IDs for testing and validation.
All installs and related events coming from the whitelisted device IDs will not be marked as rejected, allowing you to safely test integrations, attribution, and event tracking from trusted devices. Device identifiers such as IDFA, IDFV, and GAID are commonly used in mobile attribution for device-level tracking and testing.
You can whitelist up to a maximum of 10 device IDs.
Note: Only add trusted or test devices to avoid unintentionally bypassing rejection or fraud checks for live traffic.
Block In-App Events from Tracking
This feature allows you to block selected in-app events from being tracked in Apptrove. Any event added to this list will not be recorded, whether it is sent via the SDK or through server-to-server (S2S) integrations. This helps teams prevent unnecessary or irrelevant events from appearing in reports and ensures cleaner, more accurate data.
Important Note:
Once an event is disabled, it will not be tracked by any method, and no data related to the event will be stored or visible across the Apptrove platform, including:
No data in the Reports section
No records in the Logs section
Event will not be available for selection in Integrations (both Agency and Partner)
No visibility in Audience Segmentation
Event will not appear in Validation Rules / Rule Sets
No data in Custom Dashboards or Webhooks
Event will not be available for Custom Formula Metrics
If a user chooses to re-enable a disabled event, a cool-down period of up to 15 days applies. This means an event cannot be enabled again until 15 days have passed since it was disabled.
Anti-Fraud (Organic) Settings
This setting applies specifically to organic events, including installs, in-app events, uninstalls, and sessions. These fraud checks help prevent unauthorized or misleading activity from being recorded.
App Version Mismatch: Ensures that the version of a tracked install is not lower than the latest version available on the App Store or Play Store.
Duplicate IP: Blocks multiple installs originating from the same IP address to prevent fake or manipulated install counts.
Untrusted Device: Blocks installs and events from devices with untrusted builds.
Fake Device: Blocks installs and events from fake or emulated devices that do not meet authenticity checks.
Broaden your knowledge:
We are delighted to have assembled a world-class team of experienced professionals who are ready to take care of your queries and answer any questions you may have.
Feel free to reach out to us at any time by emailing us at support@apptrove.com or by using the in-platform chat feature. We'd love to hear from you!
