Module 2 - Mobile Location Data
Reveal as a provider of Mobility Data
This appendix illustrates the structure and delivery readiness of Module 2 mobile movement data as an input to downstream AMS exposure modeling. The examples below are illustrative and anonymized and do not represent live production data volumes or coverage.
Module 2 does not perform exposure (OTS), likelihood-to-see (LTS), or audience modeling. Its sole responsibility is the delivery of privacy-compliant, exposure-grade mobile movement signals to authorized AMS modeling partners.
Exposure-Grade Mobility Signal Schema
The following schema represents the granular mobile movement signals delivered to downstream AMS exposure engines. Field names, data types, and semantics are representative; the ultimate delivery schema is flexible.
| Field Name | Data Type | Description |
|---|---|---|
hashed_maid | STRING (hashed) | Pseudonymized mobile advertising identifier, hashed prior to delivery |
device_os | STRING (enum) | Device operating system: ANDROID, IOS, or OTHER |
event_timestamp_utc | TIMESTAMP | UTC timestamp of observed movement event |
latitude | FLOAT64 | Decimal latitude (WGS84) |
longitude | FLOAT64 | Decimal longitude (WGS84) |
horizontal_accuracy | FLOAT64 | Estimated positional accuracy in meters |
source_version | STRING | Data source and processing version identifier |
Notes
- Latitude/longitude are provided at full precision suitable for third-party line-of-sight and exposure zone modeling.
hashed_maidvalues are irreversibly hashed and do not contain raw device identifiers.- No PII, household identifiers, or demographic attributes are included.
Synthetic Sample
The table below is a synthetic illustration of the granularity and format provided to AMS exposure vendors.
| hashed_maid | device_os | event_timestamp_utc | latitude | longitude | accuracy_m | source_version |
|---|---|---|---|---|---|---|
| h_8fa3c1 | ANDROID | 2025-03-12T14:02:11Z | 40.7589 | -73.9851 | 8.0 | v2025.03 |
| h_8fa3c1 | ANDROID | 2025-03-12T14:06:54Z | 40.7594 | -73.9846 | 9.0 | v2025.03 |
| h_b72d09 | IOS | 2025-03-12T14:03:32Z | 34.0526 | -118.2441 | 12.0 | v2025.03 |
Disclosures
- Sample records are synthetic and anonymized
- Hashed MAIDs shown are illustrative and non-reversible
- Provided solely to demonstrate data precision and structure
Processing & Governance Overview
All mobile movement signals undergo standardized processing prior to delivery:
Signal Qualification
- Ingested under documented user consent and privacy controls
- Accuracy filtering and signal quality scoring applied
- Invalid, spoofed, or low-confidence events suppressed
Privacy & Security Controls
- MAIDs hashed prior to delivery
- No delivery of raw MAIDs or persistent device identifiers
- Encryption in transit and at rest
- Retention windows and TTL policies enforced
Audit & Versioning
- End-to-end data lineage maintained
- Versioned schemas and transformation logic
- Change logs retained for independent AMS audit and validation
Delivery to Downstream AMS Modules
Module 2 supports delivery of hashed-MAID movement data via governed delivery mechanisms:
- Encrypted cloud file delivery (e.g., S3, GCS)
- Approved clean-room environments
- Secure File Transfer (SFTP) - supported but not ideal
Movement data is delivered exclusively to AMS-authorized exposure modeling partners and is not exposed through dashboards or reporting interfaces.
Updated about 2 hours ago