- Open Source
- APIs
- Advertising
- Blog
- Events
- Podcasts
- Apps
- DSP API
- Documentation
- Traffic API
- Get Started
- Account Groups
- Ads
- Advertisers
- Audiences
- Beacons
- Bid Multipliers
- Campaigns
- Contextuals
- Creatives
- Bulk Upload Creative Data
- Data Dictionary
- Deals
- Digital Out Of Home
- Exchanges
- Inventory Sets
- Lines
- Packages
- Pixels
- Seats
- App & Site Lists
-
Targeting
- About Targeting
- A/B Testing
- Ad Initiation
- Ad Position
- ads.txt Targeting
- Beacons
- Fraud Avoidance
- Connection
- Contextuals
- Day Parting
- Demographics
- Deals & Exchanges
- DOOH Screen Lists
- DOOH Screen Owners
- DOOH Venue Types
- Frequency Capping
- Multi-Layer Frequency Capping
- Geography
- Inventory Type
- Languages
- Mobile Placement
- Native Lists
- Player Size
- Segments
- Site Lists
- Technology
- Video Ad Placements Targeting
- Video Content Length
- Viewability Targeting
- Weather Conditions
- Weather UV
- Weather Temperatures
- Weather Humidities
- User Groups
- Sign In
- Language:
Yahoo DSP Reporting API¶
This article introduces the DSP Reporting API and describes data retention policies and data recency limitations.
Overview¶
DSP Reporting API can be used to retrieve campaign data programmatically.
Data Retention Policy¶
The Yahoo DSP retains campaign data for the previous two year period.
Using the Reporting API, you can retrieve and report on data that is up to two years old. Data that is older than two years old is purged and cannot be used to create reports.