Skip to main content

User Location Determination

Learn how Apptrove determines user location using IP-based data, its limitations, and why location discrepancies can occur across platforms.

Updated yesterday

Overview

User location attribution is the process of identifying a user’s approximate geographic location, such as country, region, or city, at the time of attribution. In Apptrove, this information is used for reporting, segmentation, and high-level geographic analysis.

Apptrove does not directly determine a user’s location. Location data is inferred using IP information provided by third-party global IP location database providers, and therefore, accuracy depends on external data sources.

How Apptrove Determines User Location

  • IP Geolocation

    The primary source of location data is the IP address captured during an ad interaction, install, or in-app event.

    This IP address is mapped to a location using third-party global IP location databases, which return an estimated:

  1. Country

  2. Region or state

  3. City (approximate)

Apptrove relies on these external providers and does not control how IPs are resolved to locations.

  • Device Metadata (When Available)

    In some cases, additional device-level signals, such as system locale or network country indicators, may be used to support IP-based location. These signals are supplementary and may not always be available or consistent.

  • Fallback Handling

    If the IP address cannot be reliably mapped by third-party location providers, Apptrove may populate only high-level fields (such as country) or mark the location as Unknown.

Why Location Discrepancies Occur

Differences in user location data between Apptrove and other platforms (ad networks, analytics tools, or dashboards) are expected and can occur due to factors outside Apptrove’s control:

  • Masked or Obscured IP Addresses

    Users may use VPNs, proxy servers, or privacy features like iOS Private Relay. These tools change or hide the original IP address, causing third-party IP databases to resolve a different or approximate location.

  • Differences in IP Location Databases

    Platforms use different third-party IP location providers, each with its own update frequency and mapping logic. The same IP address may resolve to different locations depending on the provider used.

  • Timing of Location Capture

    Location may be determined at different points—such as click time, install time, or event time. If a user’s network changes between these moments, the resolved IP location may also change.

  • Device and Network Variability

    Some networks or devices provide limited or inconsistent metadata, which can affect how accurately third-party databases resolve location.

Location Fields in Apptrove Reports

Depending on availability from third-party IP databases, Apptrove may display:

  • Country

  • Region / State

  • City

  • Derived regional groupings (when granular data is unavailable)

These values represent estimated locations, not exact physical positions.

How to Use Location Data Effectively

Location data in Apptrove is best used for:

  • Country- and region-level performance analysis

  • Geographic segmentation and reporting

  • Identifying high-level market trends

It should not be used for precise, user-level geolocation decisions, as accuracy depends on IP data supplied by third-party providers.

Summary

Apptrove estimates user location primarily using IP addresses mapped through third-party global IP location databases, along with limited device metadata when available. Since IP data and mapping logic are controlled externally, Apptrove cannot guarantee exact accuracy, and location discrepancies across platforms are normal and expected.


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!

Did this answer your question?