Built for
programmatic.
PeopleAds runs its own programmatic platform, connecting publishers' inventory with demand partners through open industry standards.
Designed for
partnerships.
A platform is only as useful as the connections running through it. Ours does one job: take an ad opportunity from a publisher, make it available to the right demand, and return an ad cleanly and quickly.
Inventory in.
Publishers and supply partners send ad requests through Prebid or OpenRTB. Each request describes the placement, format, environment and the privacy signals attached to it.
Bids out.
Demand partners receive OpenRTB bid requests, evaluate them against their campaigns and respond with bids. The winning ad is returned to the publisher for display.
Integrations.
- Prebid.js
- A PeopleAds bid adapter for client-side header bidding on websites.
- Prebid Server
- A PeopleAds adapter for server-side auctions, used for web, in-app and CTV where client-side code is not practical.
- OpenRTB 2.5 and 2.6
- Direct server-to-server connections for supply and demand partners. OpenRTB 2.6 supports CTV ad pods and the latest video fields.
- Privacy signals
- Consent and privacy signals provided by the publisher, in the standard OpenRTB fields, are passed to demand partners unaltered.
- Specifications
- Endpoints, integration documentation and technical requirements are shared and tested during onboarding.
Supply-chain
transparency.
Buyers should always be able to see who is selling an impression and through whom.
- sellers.json
- PeopleAds publishes a sellers.json file at peopleads.co/sellers.json, listing every seller account on our platform with its seller type. PeopleAds is declared as BOTH: some accounts are publishers we represent directly, others are intermediaries.
- SupplyChain object (schain)
- Every bid request we send carries a complete OpenRTB SupplyChain object. PeopleAds appends its own node, and the chain matches the entries in our sellers.json.
- ads.txt and app-ads.txt
- Publishers authorise PeopleAds by listing us in their ads.txt and app-ads.txt files, as DIRECT or RESELLER depending on the relationship. We only accept traffic from properties where that authorisation is in place.
How a single impression is verified, hop by hop.
Publisher
- ads.txt / app-ads.txt
PeopleAds
- sellers.json
- schain node
Demand partner (DSP)
- Bid request with schain
Three environments. One connection.
Web
Display and video (instream and outstream) on desktop and mobile websites. Connected through Prebid.js, Prebid Server or OpenRTB.
In-app
Banners, interstitials and video inside iOS and Android apps. Connected server-to-server through Prebid Server or OpenRTB.
Connected TV
Video ad breaks in streaming apps on smart TVs and streaming devices, including ad pods through OpenRTB 2.6. Connected server-to-server.
Illustrative mockups, not PeopleAds campaigns. Availability depends on each partner's inventory and integration.
"Partners should always be able to see what is running, and talk to someone who understands it."
Delivery
Requests, bids, impressions and revenue, broken down to the level agreed with each partner.
Reconciliation
Figures that can be matched against partners' own systems, with discrepancies investigated together.
Follow-through
A named contact who reviews performance and raises issues before they become problems.
Technical onboarding.
Start an integration- 1
Introduction
We discuss your inventory or demand, environments, formats and commercial expectations.
- 2
Specification
Integration method, endpoints, documentation and technical requirements are exchanged. For supply, we confirm your ads.txt or app-ads.txt entry.
- 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.