Global Mobile Location Data
Summary
First party mobile location GPS data sourced from 800K+ apps cleaned and structured for 150+ countries.
Key Features
- Updated daily
- First party data, directly from source
- Reaching every country on the globe
- GPS signals from 800K+ apps with proprietary SDK
- 1.5B+ unique devices monthly
- 10B+ daily location events
Documentation
Applications
- Location based advertising
- Location based audiences
- POI based targeting
- Geofencing
- Foot traffic analytics
Use Cases
Foot traffic analysis of physical stores
Gain intelligence and make strategic decisions by analyzing mobile location foot traffic data.
Client: Retailer with over 5,000 stores in Europe
Goals: Making strategic decisions in the wake of COVID 19
Process:
- Importing raw location data in the region
- Analyzing historical foot traffic data around stores as well as trends during the pandemic
- Monitoring visits and making real time decisions according to daily consumer trends
Global location based audience product
Import raw mobile location data to expand location based audiences globally.
Client: US based location company
Goals: Expanding location audience product globally
Process:
- Testing samples of Start.io mobile location data globally
- Importing raw location data
- Processing data records and clustering users into profiles and segments
- Expanding the location audience product to trending regions with growing demand
Overview
Start.io (formerly StartApp) is a mobile data provider enables organizations to uncover insights and make data-driven decisions that enhance strategies and drive growth. Start.io's direct integration with one million mobile apps provides access to unprecedented levels of global first-party data, which can be leveraged to understand and predict behaviors, identify new opportunities, and fuel strategic business decisions.
This data product offers mobile location GPS data, sourced from first party proprietary SDK, that is cleaned and structured. It is a location dataset that provides daily updated mobile location data, helping you learn more about your customers, competition, properties, and community's movement behaviour to create accurate insights and make the right decisions in real time.
Coverage
- Mobile locations for 150+ countries
- 1.5B+ unique devices monthly
- 10B+ daily location events
- 20+ data signals providing the building blocks for your data products
Methodology
- Anonymized mobile locations are collected from first party apps with SDK
- Hygienic processes are used to remove duplicates, invalid locations, fraud, centroids and apply COPPA/GDPR compliance
- Machine learning, NLP, and clustering are applied for data enrichment
- Create final data with locations, taxonomy, lookalike, and profiling
Related Data Products
Dictionary
Filter | Column | Title | Data Type | Description |
|---|---|---|---|---|
| user_id | User ID | Bigint | Unique ID of the device | |
 | enriched_country | Enriched Country | Text | Enriched country of the device |
| ts | Timestamp | Timestamp | The time of the event |
| lat | Lat | Float | Geographic coordinate that specifies the north–south position of a point on the Earth's surface | |
| long | Long | Float | Geographic coordinate that specifies the east–west position of a point on the Earth's surface | |
| ip | IP | Text | The IP address the device was connected to when the event was created |
Sample Data
API
ALTADATA provides a powerfull API, compatible with JSON, CSV formats. You can connect, update and analyze our data products with cURL, Python, R, Ruby, Java or Javascript
Authentication
Getting an API key
You need to subscribe to an ALTADATA data product to get an API key. Once you subscribe to the data product you can find your API key on your Account Dashboard.
Auhenticating your requests
`api_key` is your access token. This token must be included on each API call
with either a HTTP Header Authorization, or a query parameter api_key.
Example: https://www.altadata.io/data/api/dm_stapp_01?api_key=YOUR_API_KEY
ALTADATA API Reference Table
| Parameter Type | Parameter | Explanation | Available Values | Default |
|---|---|---|---|---|
| General | size | The number of records will be returned for each page. | 5 - 100 | 20 |
| General | page |
The page number. It starts at 1 and increments one by one. Each page returns records
that row count equals to the size parameter
| 1- ... | 1 |
| General | format | The data return format of API call | json , csv | json |
| General | collapse | The aggregation format of API call |
Examples are monthly, yearly, bystate, bycountry,
etc. Refer to the data product documentation to see available aggregations for it.
| null |
| Select | columns | Column select is how you specify the content of an SQL SELECT c_only, c_certain, c_columns FROM clause. | More detail is in the following sections. | * |
| Order | order_by | Column order is how you specify the content of an SQL ORDER BY clause. | More detail is in the following sections. | null |
| Lookup | vary by column name | Column lookups are how you specify the content of an SQL WHERE clause. | More detail is in the following sections. | * |
Select
Column select is how you specify the content of an SQL SELECT c_only, c_certain, c_columns FROM clause. It specifies as a keyword argument to the query string of API Call URL. Basic usage is a comma-separated list of column names. If not given, the default value is *(asterisk).
Example 1 :
Query : ?columns=C1,C2,C3 SQL Equivalent : Select C1,C2,C3 from DATA_PRODUCT
Example 2 :
Query : Not Given | ?columns= | ?columns=* SQL Equivalent : Select * from DATA_PRODUCT
Order
Column order is how you specify the content of an SQL ORDER BY clause. It specifies as a keyword argument to the query string of API Call URL. Basic usage is a comma-separated list of column names where each column name has an appropriate suffix (asc,desc) after _(underscore) or no suffix (means ascending).
Example :
Query : ?order_by=C1_asc,C2,C3_desc,C4_asc SQL Equivalent : Select * from DATA_PRODUCT order by C1 asc, C2, C4 desc, C4
asc
| Order Type | Suffix |
|---|---|
| Ascending | null |
| Ascending | asc |
| Descending | desc |
Lookup
Column lookups are how you specify the content of an SQL WHERE clause. They’re specifies as keyword arguments to the query string of API Call URL. Basic usage is appending _(underscore) then lookup type as a suffix to name of the column that you want to filter. The query parameter for a column is built like the format {COLUMN_NAME}_{LOOKUP_TYPE}
As a convenience when no lookup type is provided
| Lookup Type | Suffix | Value Type | Example | SQL Equivalent |
|---|---|---|---|---|
| Equal to | null | String | Numeric | Datetime | ?COLUMN=VALUE | Select * from DATA_PRODUCT where COLUMN=VALUE |
| Equal to | eq | String | Numeric | Datetime | ?COLUMN_eq=VALUE | Select * from DATA_PRODUCT where COLUMN=VALUE |
| Not Equal to | neq | String | Numeric | Datetime | ?COLUMN_neq=VALUE | Select * from DATA_PRODUCT where COLUMN<>VALUE |
| Greater Than | gt | Numeric | Datetime | ?COLUMN_gt=VALUE | Select * from DATA_PRODUCT where COLUMN>VALUE |
| Greater Than or Equal to | gte | Numeric | Datetime | ?COLUMN_gte=VALUE | Select * from DATA_PRODUCT where COLUMN>=VALUE |
| Less Than | lt | Numeric | Datetime | ?COLUMN_lt=VALUE | Select * from DATA_PRODUCT where COLUMN,VALUE |
| Less Than or Equal to | lte | Numeric | Datetime | ?COLUMN_lte=VALUE | Select * from DATA_PRODUCT where COLUMN<=VALUE |
| In | in | String | ?COLUMN_in=V1,V2,V3 | Select * from DATA_PRODUCT where COLUMN in ('V1','V2','V3') |
| Not In | notin | String | ?COLUMN_notin=V1,V2,V3 | Select * from DATA_PRODUCT where COLUMN not in ('V1','V2','V3') |