Skip to content
All Products
Location & Place Intelligence

Global Mobility/Location Data

Device-level GPS signals and aggregated mobility patterns, with a daily US and Canada feed plus country-specific coverage.

Since 2018

Privacy-safe enterprise data

VOSB & SDVOSB

U.S. Veteran-Owned, Service-Disabled

SCC Transfers

EU/UK/CH per privacy policy

GDPR · CCPA · CPRA

Consent-first data sourcing

Overview

A global mobility dataset capturing device-level movement and visitation patterns from consented app, Wi-Fi, and SDK sources. Includes real-time and historical location events designed for foot traffic measurement, movement analysis, dwell time tracking, origin-destination modeling, and cross-border travel intelligence, with a daily US and Canada feed and country-specific coverage.

At a glance

Short, extractable evaluation notes for buyers (what you get, how it’s sourced, and how procurement typically runs).

What you get

  • Mobility signals sized to your exact geography, not deck averages.
  • Filters to reduce low-accuracy artifacts before analysis.
  • Join-ready keys for measurement and research workflows.

How it’s sourced

  • Consent-aware sourcing and exclusion controls for sensitive categories.
  • Audit-ready provenance you can hand to procurement/legal.
  • Change control for refresh deltas and schema stability.

How you buy it

  • Pilot with match-rate targets and accuracy floors.
  • Agree on exclusions + retention up front.
  • Move to production license after pilot acceptance.

Want the buying guide?

If you’re evaluating vendors or writing an RFP, this guide lays out what to ask for (coverage, refresh, governance) and links to the best references.

Location intelligence buying guide

Need an API key + JSON sample?

For technical evaluation, we can provide a sample payload, schema notes, and delivery options (S3/SFTP/Snowflake) aligned to your workflow.

Data Types

  • Lat/long coordinates
  • Timestamp & dwell time
  • Aggregated movement flows
  • Origin-destination matrices
  • Cross-border travel patterns
  • Transportation mode signals

Delivery Formats

CSVJSONParquetAPI

Key Features

  • Daily US and Canada feed
  • Country-specific feeds (for example, LATAM)
  • Daily data freshness
  • Historical data back to 2019
  • Custom geography support

Sample fields

A representative slice of the Global Mobility/Location Data schema. The data dictionary shared during evaluation lists every field with its type, nullability, join keys, and refresh cadence.

FieldWhat it contains
maidPseudonymous mobile advertising identifier for the consented device.
event_timestampUTC timestamp for the location observation.
latitudeLatitude of the quality-filtered location observation.
longitudeLongitude of the quality-filtered location observation.
horizontal_accuracyEstimated horizontal accuracy radius for the observation.
dwell_secondsCalculated duration of a dwell or visit event.
origin_geographyNormalized origin geography for an aggregated movement flow.
destination_geographyNormalized destination geography for an aggregated movement flow.

How Mobility and Location Data Is Sourced

GSDSI collects device-level latitude and longitude signals through a network of SDK-integrated mobile applications, Wi-Fi sources, and consented data partners. Each location observation includes precise GPS coordinates, a timestamp, estimated horizontal accuracy, dwell time calculation, and device type metadata. The data goes through rigorous quality filtering to remove centroid pings, VPN-masked locations, and signals with accuracy radii that exceed acceptable thresholds. Visit attribution algorithms match cleaned location signals against GSDSI's global Points of Interest repository (23M+ U.S. POIs with polygon boundaries, plus coverage in 150+ countries), converting raw GPS pings into structured visit events. For broader mobility analysis, raw signals are also processed into origin-destination flow matrices that quantify how populations move between geographic zones. Transportation mode classification distinguishes between pedestrian, vehicular, rail, and air travel. Cross-border travel detection identifies international movement patterns for tourism and trade corridor monitoring. Historical data goes back to 2019, supporting longitudinal trend analysis and year-over-year comparisons.

Common Applications

Retailers and QSR brands use this data to measure foot traffic trends, benchmark visitation against competitors, and analyze trade areas for site selection. Real estate investment firms evaluate acquisitions by examining foot traffic density, visitor origins, and temporal visitation trends. Tourism boards measure inbound visitor volumes by origin country, track seasonal patterns, and benchmark destination competitiveness. Urban planners use origin-destination matrices to optimize transit routes and model the impact of policy changes on commuter behavior. Financial analysts use location-derived foot traffic as an alternative data input for revenue proxy models, tracking same-store trends at publicly traded companies. Government agencies and public health organizations use aggregated mobility data for transportation planning, pandemic response, and infrastructure investment decisions.

Proof & buyer diligence for mobility data (post-FTC)

  • Ask for daily-unique-devices in your exact geography (DMA/polygon) with documented consent posture, not global panel size.
  • Define sensitive-category exclusions and enforce them in join logic before production activation.
  • Validate accuracy floors and filtering (centroid pings, VPN artifacts, low-accuracy radii) during the pilot.

Vendor comparisons

Use these buyer guides to compare this feed category with adjacent vendor offerings.

How buyers diligence mobility data

Mobility-data diligence should be geography-specific. Buyers need observed daily devices, accuracy filtering, sensitive-location exclusions, dwell logic, and consent documentation for the exact markets or polygons they will analyze.

  • Measure usable device density in the target DMA, polygon, or trade area.
  • Review GPS accuracy filters, centroid suppression, VPN/artifact handling, and dwell rules.
  • Define sensitive-category exclusions and downstream retention limits before production.
  • Confirm delivery latency and whether the feed supports raw events, visits, or aggregates.

Frequently asked questions about Global Mobility/Location Data

What does the Global Mobility & Location Data feed contain?

Daily MAID-level location events across 150+ countries with visit attribution to GSDSI's POI inventory, dwell time, origin-destination pairs, and home/work/frequent-location anchors. Privacy-safe panel-based methodology, no individual identifiers are exposed in the delivered dataset beyond the MAID.

What countries are covered?

150+ countries with the deepest density in the United States, Western Europe, Brazil, Mexico, Argentina, India, Japan, and Australia. A full country-coverage matrix is shared during sample evaluation so buyers can confirm panel size before signing.

How is the data privacy-safe?

Identifiers in the feed are mobile advertising IDs (MAIDs) sourced from consented panels. Cleartext PII is never present. Where buyers operate under regulated frameworks (HIPAA-adjacent, GDPR), GSDSI provides supplemental sourcing documentation and supports clean-room delivery.

What's typical use of the location feed?

Foot-traffic analytics, retail-site selection, OOH measurement, competitive share-of-visit, CRE underwriting, urban-planning origin-destination studies, travel & hospitality demand modeling, and tickerized alpha signals for equity research.

How does GSDSI compare to Foursquare or SafeGraph?

Comparable in core US foot-traffic depth; differentiates on international coverage breadth (150+ countries under one contract), on combined POI + visit + identity-graph delivery, and on delivery flexibility (raw MAIDs, not just aggregated metrics).

✓ Opt-Out Request Honored via Global Privacy Control