What is the GSDSI MAID Feed?

Mobile advertising IDs linked to hashed-email addresses (and, where available, IP, postal, and household IDs): the connective tissue of cross-device identity resolution. ~200M+ US MAID-to-HEM linkages and 700M+ international across 150+ countries, refreshed daily.

How are linkages built?

From a mix of deterministic sources (login-confirmed app and web events) and probabilistic signals (shared-IP household inference). Each linkage carries a strength score and a last-seen timestamp; buyers can filter on strength threshold to trade match-rate against precision.

Is the MAID feed affected by ATT, GAID changes, or cookie deprecation?

ATT and GAID restrictions reduce raw-MAID supply across the industry; GSDSI's feed is sized accounting for opt-in panels and consented sources. Where MAIDs are unavailable, the feed cross-walks to HEM, IP, and household ID so downstream activation paths remain intact.

What's the typical use case?

Cross-device identity resolution for adtech and martech, audience activation across DSPs and CTV, attribution and incrementality measurement, CRM enrichment for mobile-first apps, and panel construction for measurement vendors.

How is the feed delivered?

CSV or Parquet via S3 / SFTP, Snowflake direct-share, or live lookup via the GSDSI REST API. Hashed identifiers throughout, cleartext is never required. Clean-room delivery (AWS Clean Rooms, Snowflake Data Clean Rooms, InfoSum) is supported on request.

MAID Data Feed for Identity Resolution (Daily)

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 MAID Feed covers ~200M+ U.S. MAID-to-HEM pairs and 700M+ international devices across 150+ countries, sourced from consent-verified mobile applications and SDK partners. Each Mobile Advertising ID (Apple IDFA / Google GAID) is enriched with app usage patterns, browsing behavior, and IAB-taxonomy-aligned interest signals, built for programmatic activation, audience building, and cross-device identity resolution in privacy-compliant environments.

At a glance

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

What you get

MAID coverage for onboarding and activation workflows.
Cohort sizing and match-rate testing during evaluation.
Join scaffolding for cross-device measurement.

How it’s sourced

Documented privacy envelope, exclusions, and opt-out handling.
Refresh/decay expectations for linkage stability.
Provenance artifacts suitable for enterprise diligence.

How you buy it

Matched sample against your seed to validate value.
Confirm join keys + delivery path for your stack.
License aligned to activation geography and use case.

Identity graph Buyer guide Pilot process

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.

Identity resolution 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.

Request API key + JSON sample Developer hub

Data Types

Mobile Ad IDs (IDFA/GAID)
App usage categories
Browsing behavior signals
Interest & intent taxonomy

Delivery Formats

CSVJSONParquetAPI

Key Features

700M+ global device reach
Daily refresh cadence
IAB taxonomy alignment
Consent-verified sources

Sample fields

A representative slice of the MAID Feed 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 Apple IDFA or Google advertising identifier.
hem	Hashed email linkage when available for permitted identity-resolution use.
country_code	Country associated with the consented device signal.
app_category	Normalized category for observed application activity.
interest_segment	IAB-aligned interest or intent segment assigned to the device.

How Mobile Ad ID Data Is Sourced

GSDSI's MAID Feed collects anonymized Mobile Advertising Identifiers (Apple's IDFA and Google's GAID) from a network of consent-verified mobile applications and SDK partners. Each device signal includes associated app usage patterns, browsing behavior categories, and IAB-taxonomy-aligned interest segments derived from observed in-app activity. The feed covers 700M+ unique devices globally with a daily refresh cadence, so audience segments reflect current consumer behavior. All data collection follows platform-level consent requirements including Apple's App Tracking Transparency (ATT) framework and Google's privacy specifications, with documented opt-in chains for every participating source.

Common Applications for MAID Data

Programmatic media buyers use MAID data to build custom audience segments for activation across DSPs including The Trade Desk, DV360, and Amazon DSP, targeting consumers based on observed behaviors rather than inferred demographics. Location analytics firms enrich MAIDs with GPS-derived visitation history to create place-based audience segments, for example frequent visitors to luxury retailers or gym members in specific metro areas. Identity resolution platforms use MAIDs as a connective key to link mobile behavior with CTV viewership, web activity, and household-level profiles for true cross-device targeting. Measurement companies match exposed MAIDs against foot traffic panels to perform campaign attribution, proving that mobile ad exposure drove subsequent store visits.

Industries Using This Product

Advertising & AdTech

Prove ROI from impression to store visit

Media & Entertainment

Audience intelligence from screen to venue

Vendor comparisons

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

How buyers diligence MAID and identity coverage

Identity buyers test MAID feeds against their own seed data because deck-level coverage does not predict usable match rate. The pilot should measure ATT/GAID availability, HEM linkage quality, decay behavior, and opt-out propagation.

Run a matched sample against known customer seeds to measure reachable MAID and HEM yield.
Ask for refresh and decay expectations by geography, platform, and identifier type.
Validate consent posture, suppression handling, and sensitive-category exclusions.
Confirm join keys, hash formats, and whether delivery supports activation and measurement separately.

Request a Quote Sourcing methodology Request a matched sample

MAID Feed