Better connections.
More opportunities.
For DSPs and programmatic buyers looking for an additional, transparent supply source, and a direct line to the people managing it.
Connect your demand{
"imp": [{
"video": { "w": 640, "h": 480, "mimes": ["video/mp4"] },
"bidfloor": 2.50
}],
"site": { "domain": "example.com", "page": "..." },
"device": { "ua": "...", "ip": "..." },
"source": {
"schain": {
"complete": 1,
"ver": "1.0",
"nodes": [
{ "asi": "peopleads.co", "sid": "example-seller-id", "hp": 1 }
]
}
},
"regs": { "gdpr": 1 }
}What you get.
PeopleAds connects demand partners to supply from publishers and supply partners working with us. You receive standard OpenRTB bid requests with a complete supply chain, bid on what fits your campaigns, and work with a team that answers technical and commercial questions directly.
Environments.
Web
- Formats
- Display, video (instream, outstream)
- Typical connection
- Prebid.js, Prebid Server or OpenRTB
In-app
- Formats
- Banner, interstitial, video
- Typical connection
- Prebid Server or OpenRTB
Connected TV
- Formats
- Video, including ad pods
- Typical connection
- OpenRTB 2.6 or Prebid Server
| Environment | Formats | Typical connection |
|---|---|---|
| Web | Display, video (instream, outstream) | Prebid.js, Prebid Server or OpenRTB |
| In-app | Banner, interstitial, video | Prebid Server or OpenRTB |
| Connected TV | Video, including ad pods | OpenRTB 2.6 or Prebid Server |
All demand connections are OpenRTB, server-to-server. Availability varies by partner. We share details on current supply, formats and geographies on request.
OpenRTB connectivity.
Bid requests
Sent from PeopleAds to your bidder endpoint in OpenRTB 2.5 or 2.6, describing the impression, placement, environment and device.
Bid responses
Returned by your bidder with price and creative markup, following the OpenRTB specification.
Supply chain
Every request carries a complete SupplyChain object (schain). Every node can be verified against the corresponding sellers.json, including ours at peopleads.co/sellers.json.
Privacy signals
Consent and privacy signals supplied by the publisher are passed in the standard OpenRTB fields, for you to act on.
Win and billing
Win and billing notifications are agreed during integration.
Quality and operations.
Traffic quality
Supply is reviewed and monitored for invalid traffic with Pixalate, DoubleVerify and HUMAN. Concerns you raise are investigated.
Transparency
Clear information about where impressions come from, using industry standards such as ads.txt and app-ads.txt.
Reconciliation
Discrepancies are reviewed together against both sides' numbers, with a named contact to talk to.
Technical onboarding.
- 1
Introduction
We discuss your demand, environments, formats and commercial expectations.
- 2
Specification
Integration method, endpoints, documentation and technical requirements are exchanged.
- 3
Testing
Requests and responses, schain and reporting are tested end to end before live traffic is sent.
- 4
Launch
Traffic is enabled gradually and monitored, with adjustments made together.
Connect your demand.
Tell us about your platform, the formats you buy and your geographic focus. We reply to every enquiry.