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
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.
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.
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.
| Field | What it contains |
|---|---|
| maid | Pseudonymous mobile advertising identifier for the consented device. |
| event_timestamp | UTC timestamp for the location observation. |
| latitude | Latitude of the quality-filtered location observation. |
| longitude | Longitude of the quality-filtered location observation. |
| horizontal_accuracy | Estimated horizontal accuracy radius for the observation. |
| dwell_seconds | Calculated duration of a dwell or visit event. |
| origin_geography | Normalized origin geography for an aggregated movement flow. |
| destination_geography | Normalized destination geography for an aggregated movement flow. |
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.
Related pages
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.
