Figuring out user location while using user ip – help center
Contents
Every time a user performs an action that will reach AppsFlyer, that’s an install or perhaps in-application event, AppsFlyer extracts the Ip from the user’s device during the time of the experience.
Appsflyer converts the Ip into location information utilizing a third-party global provider, Digital Element. AppsFlyer periodically fetches the worldwide IP addresses list from Digital Element, which is often used to transform IP addresses of users into accurate Geo locations.
Example: Raw location data
Every entry in AppsFlyer raw data provides the following location-related fields, in line with the Ip:
- Region
- Country Code
- Condition
- City
- Postal Code
- DMA (where relevant)
Where’s the place information obtainable in AppsFlyer?
AppsFlyer’s various pages and aggregated reports make use of the location data to segment geographically distributed cohorts of users.
These include:
- Grouping your data by Geo (country code) around the overview page, Retention report or Cohorts report.
- Geo Performance Report
- Geo by Date Report
- Master API and Pivot table
Causes of location discrepancy
In some instances there might be variations within the derived location of users between AppsFlyer along with other platforms, whether or not the other platform also uses Digital Element to solve IP addresses.
This is a summary of possible causes of such variations:
- Periodic updates – to allow fast attribution, AppsFlyer resolves the IP addresses into location data internally. Which means that AppsFlyer fetches the worldwide map from Digital Element periodically and never instantly. If AppsFlyer and yet another platform have fetched Digital Element data on several dates, changes might be present.
- ISP Changes – Digital Element’s databases are quickly altering as ISPs are often altering their IP mappings.
- Different Plans – Digital Element offers different package plans in line with the needed degree of precision. Other platforms might be using other Digital Element package plans than AppsFlyer’s, which might give different Ip resolving.
Every time a user performs an action that will reach AppsFlyer, that’s an install or perhaps in-application event, AppsFlyer extracts the Ip from the user’s device during the time of the experience.
Appsflyer converts the Ip into location information utilizing a third-party global provider, Digital Element. AppsFlyer periodically fetches the worldwide IP addresses list from Digital Element, which is often used to transform IP addresses of users into accurate Geo locations.
Example: Raw location data
Every entry in AppsFlyer raw data provides the following location-related fields, in line with the Ip:
- Region
- Country Code
- Condition
- City
- Postal Code
- DMA (where relevant)
Where’s the place information obtainable in AppsFlyer?
AppsFlyer’s various pages and aggregated reports make use of the location data to segment geographically distributed cohorts of users.
These include:
- Grouping your data by Geo (country code) around the overview page, Retention report or Cohorts report.
- Geo Performance Report
- Geo by Date Report
- Master API and Pivot table
Causes of location discrepancy
In some instances there might be variations within the derived location of users between AppsFlyer along with other platforms, whether or not the other platform also uses Digital Element to solve IP addresses.
This is a summary of possible causes of such variations:
- Periodic updates – to allow fast attribution, AppsFlyer resolves the IP addresses into location data internally. Which means that AppsFlyer fetches the worldwide map from Digital Element periodically and never instantly. If AppsFlyer and yet another platform have fetched Digital Element data on several dates, changes might be present.
- ISP Changes – Digital Element’s databases are quickly altering as ISPs are often altering their IP mappings.
- Different Plans – Digital Element offers different package plans in line with the needed degree of precision. Other platforms might be using other Digital Element package plans than AppsFlyer’s, which might give different Ip resolving.
Resourse: https://support.appsflyer.com/hc/en-us/articles/
