IP-masking

At a glance: IP-masking is used to mask an app user's IP addresses in raw data reports.

IP-masking

  • If enabled: 
    • User IP addresses are not listed in raw data reports.
    • IP address field is populated with the value 1.1.1.1. Installs performed before enabling IP masking aren't masked.
  • Limitation for organic in-app events: IP-masking populates these events with a hashed IP address. 

 Example

  • IP-masking setting follows this path: disabled, enabled, and then enabled. 
  • Three users install the app on different dates as shown in the app install table
  • IP-masking and raw data report table show the status of the IP-masking setting and related raw data on the relevant dates.
App install
Install date User ID

 IP address

January 2 User_A 192.0.2.1 
January 7 User_B 192.0.2.33 
January 14 User_C 203.0.113.1 
IP-masking and raw data
Date IP masking setting status

 Raw data report

January 1 Disabled User A 192.0.2.1
January 2 Enabled User_A 192.0.2.1
January 8 Enabled User_A 192.0.2.1
User_B 1.1.1.1
January 9 Disabled

User_A 192.0.2.1
User_B 1.1.1.1

January 15 Disabled

User_A 192.0.2.1
User_B 1.1.1.1
User_C 203.0.113.1

Enabling IP-masking

IP-masking is set per app and affects installs from all sources.

To enable IP-masking:

  1. Go to Configuration > App Settings.
  2. In the App settings window, scroll down to Advanced.
  3. Select Enable IP Masking in Raw Reports.
    IP-masking is enabled. 

IP-masking in raw data reports

IP-masking is activated:

  • New installs and in-app events show an IP address of 1.1.1.1. 
  • Location-related parameters, like country and city, still appear in raw data reports.

Example raw data report 

ip_masking.png

Was this article helpful?
1 out of 1 found this helpful