Device-level app usage events with daily refresh, delivered raw or aggregated, for audience, competitive, and market analysis.
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
GSDSI's App Usage dataset is a device-level record of which apps are in use, drawn from SDK partnerships, direct integrations, and server-to-server data sharing agreements. Each event carries an anonymized device identifier, a timestamp, the app identifier, and the country, so the same device can be followed through a consistent time series. It is refreshed and aggregated daily, with about three years of history available and more on request. Buyers can take the raw events or aggregated measures such as sessions and active users by app, category, or brand.
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.
A representative slice of the App Usage Data schema. The data dictionary shared during evaluation lists every field with its type, nullability, join keys, and refresh cadence.
Field
What it contains
device_id
Anonymized mobile advertising identifier for the device.
event_timestamp
UTC timestamp of the app usage event.
platform
Identifier type for the device, AAID on Android or IDFA on iOS.
ip
IP address observed with the event.
country_iso2
Two-letter ISO country code for the event.
app_id
Application identifier, a package name on Android or a numeric store ID on iOS.
How App Usage Data Is Collected
App usage signals are collected through SDK partnerships, direct integrations, and server-to-server data sharing agreements. Each data point carries an anonymized device identifier, the app, and engagement context tied to a consistent time series. The collection layer observes events throughout the day, and GSDSI refreshes and aggregates the dataset daily. Because the identifiers are the same mobile advertising IDs used across GSDSI's MAID and location feeds, app usage can be joined to those feeds for a fuller view of a device.
Common Applications for App Usage Data
Marketing teams use app usage to build audiences around the apps people actually open, and to size the reach of a publisher or category. Strategy and research teams track how usage of an app or an app category moves over time. Analysts working with public companies can map app usage to publishers and service providers through app ownership and domain matching. App usage also supports measurement: pair exposure data with the apps a device uses to understand context around a campaign.
Delivery and Licensing
Delivery is server-to-server, to a cloud bucket, or through an API, in the file format the buyer prefers. Pricing is a subscription that depends on the feed and the countries in scope. Country-level counts are in the data dictionary available from the GSDSI team, and a sample is available on request so a buyer can test the feed against their own device or app list before licensing.
App usage buyers should test device and app coverage on their own target list, how events are timestamped and deduplicated, and how consent is carried, before sizing a license from headline counts.
Match the app identifiers you care about against the sample to measure coverage by app and country.
Confirm how events are deduplicated, how the time series is kept consistent, and how late events are handled.
Ask how consent and opt-out signals are carried with each device and honored on delivery.
Decide up front whether you need raw events, aggregated measures, or both, and set the delivery format in the order form.
Device-level app usage events. Each event carries an anonymized device identifier, a timestamp, the device platform, the country, and the app identifier, so a device can be followed through a consistent time series.
How is app usage data collected?▾
Through SDK partnerships, direct integrations, and server-to-server data sharing agreements. Identifiers are anonymized mobile advertising IDs, the same kind used across GSDSI's MAID and location feeds.
How often is it refreshed and how far back does it go?▾
The dataset is refreshed and aggregated daily. About three years of history is available, and more can be provided on request.
Can I get raw events or only aggregates?▾
Both. Raw events with device ID, timestamp, and app are available, along with aggregated measures such as sessions and active users by app, category, or brand.
How is it delivered?▾
Server-to-server, to a cloud bucket, or through an API, in the file format the buyer prefers. Contact GSDSI for a sample and for country-level counts.
✓ Opt-Out Request Honored via Global Privacy Control
We use cookies and similar technologies to improve your experience. No marketing cookies are pre-selected. Learn more in our Privacy Policy. Your Privacy Choices.
