Anonymous IP filtering

Important:

If you are using Samsung Cloud, reach out to your Adjust representative or email support@adjust.com

Adjust's Anonymous IP filter maintains the integrity of your app's data by protecting it from fraudulent activity coming from VPNs, Tor exit nodes, and data centers. This targets fraudsters using device farms and emulation software to fake installs and post-install activity, and place the conversions in high-value markets.

The filter cross-checks incoming traffic against MaxMind's anonymous IP database. Anonymous IP filtering is controlled by two independent toggles, one for installs and one for post-install activities — see Enable fraud prevention features for how to turn each one on.

  • Installs: any install or reattribution affiliated with an anonymizing service, such as a VPN, Tor exit node, or known data center, is attributed to Untrusted Devices. This helps prevent the majority of fraudulent attributions associated with device farms and emulators before they enter your data set, and reduces the impact of data center manipulation tactics significantly.
  • Post-install activities: sessions, events, and ad revenue affiliated with an anonymizing service are rejected and excluded from your reporting, but they are not reattributed to Untrusted Devices. They remain attributed to the original install source. This filter only applies to post-install activity coming from installs that were not themselves rejected — if an install is already attributed to Untrusted Devices, this toggle has no further effect on its sessions, events, or ad revenue. This protects against cases where an install is legitimate but subsequent activity originates from an anonymized IP.
Growth solution:
The Fraud Prevention Suite is available as an Adjust Growth Solution. To get Fraud Prevention on your account, contact sales@adjust.com.

Anonymous IP filtering data in reports

Installs rejected by the Anonymous IP filter are assigned to Anonymous IP - a sublink of the network-level link Untrusted Devices. Post-install activity rejected by the filter is excluded from your KPIs but stays attributed to its original install source — it does not move to Untrusted Devices. You can use the following KPIs to view rejected traffic by traffic source, broken down by install-level and post-install-level rejections.

In reportsKPI
Rejected installs anonymous IPrejected_installs_anon_ip
Rejected reattributions anonymous IPrejected_reattributions_anon_ip
Rejected events anonymous IPrejected_events_post_install_activity_anonymous_ip_status
Rejected sessions anonymous IPrejected_sessions_post_install_activity_anonymous_ip_status
Rejected ad revenue anonymous IPrejected_ad_revenue_post_install_activity_anonymous_ip_status
Rejected In-app revenue anonymous IPrejected_revenue_post_install_activity_anonymous_ip_status