Yahooinc

Receipt-derived purchase-intent corpus parsed from consumer e-mail inboxes: structured purchase-confirmation records extracted from Yahoo Mail, classified into nine event types (FLIGHT, CAR, HOTEL, MOVIE_TICKETS, LIVE_EVENTS, INVOICES, PRODUCTS, SOCIAL_EVENTS, STOCKS_AND_INVESTMENTS) and exposed through the DSP as anonymized audiences. Attribute depth includes product-level fields (item name, item price in USD, order date) and invoice fields (payment status, payment due date), with a configurable per-consumer receipt-frequency threshold of 1-5. The licensable asset is inbox-parsed, structured, item-level proof of actual purchase — an attested transaction signal that ad panels and survey panels can only infer.

Open buyer room →

Sample

Brickroad customers

Sample this dataset before you buy it.

Your sourcing agent asks Yahooinc and files the sample in your catalog — private to you.

Start 7-day trialNothing is charged until the trial ends.

Coverage

Universe, instruments and categories.

Industry: Interactive Advertising & Marketing ServicesApplication Software
Instruments: equities
Categories

Dataset card

Type: not stated
Format: Tabular JSON served through a REST endpoint (/traffic/audiences/mail_event) with GET/POST/PUT methods; records carry an audience id, eventType, frequency, accountId and nested textAttributes / numericAttributes arrays. Sold as addressable audience segments inside the DSP rather than as an exportable file.
Volume: Receipt-scale: with hundreds of millions of mail users each receiving many transactional e-mails per year, the parsed receipt corpus is plausibly in the tens of billions of structured purchase events annually. The commercially relevant figure, however, is audience size per eventType, which the DSP reports at query time and is not published in the documentation.
Users: Yahoo Mail's user base is the population — historically reported at ~900M-1B monthly active users across Yahoo properties, with Mail the largest single surface. Request further research for the current Mail-only MAU and for the subset who have granted mail-parsing consent, since only that subset is in the audience.
History: 20 years
Update frequency: not stated
Growth: Active — the receipt-audience capability is documented in the current DSP API with full CRUD semantics and vertical attribute depth, indicating an actively maintained commercial product rather than a legacy feature
Launched: Mail-based purchase-receipt targeting has existed in the Yahoo DSP since roughly the mid-2010s (mail-event audiences were an early DSP differentiator); this documentation reflects the current-generation API, so the capability is mature rather than new
Delivery: not stated
Entity mapping: not stated
Sample: not stated
Point-in-time: not stated
Licence: not stated

supplier index read from their site