PeopleAds

Built for the programmatic ecosystem.

The standards PeopleAds works with, what each one means for your integration, and what we need from you to get started.

One protocol, both sides.

Ad requests from publishers and supply partners are passed to demand partners as OpenRTB bid requests. Bidders respond with a price and creative markup, and the selected ad is returned for display. Supported OpenRTB versions, formats and endpoint details are confirmed with each partner during integration.

Supply side
Ad requests describing the placement, format, environment, device and the privacy signals attached to the opportunity.
Demand side
Bid requests sent to your bidder endpoint; bid responses returned following the OpenRTB specification.
Server-to-server
Direct connections between systems, typical for app, video and CTV environments.

Header bidding, explained plainly.

Header bidding lets a publisher offer an impression to several demand sources at the same time before the ad server makes its decision. It is commonly run in the browser with Prebid.js, or on a server with Prebid Server.

Prebid.js
Open-source header bidding library running on the publisher's page.
Prebid Server
Server-side counterpart that runs the auction outside the browser, reducing page load.
S2S / OpenRTB
Where header bidding is not the right fit, an OpenRTB server-to-server connection is the alternative.

PeopleAds provides adapters for Prebid.js and Prebid Server, OpenRTB 2.5 and 2.6, sellers.json declared as BOTH, schain with PeopleAds appending its own node, ads.txt DIRECT/RESELLER.

Every hop, accounted for.

The IAB Tech Lab SupplyChain object (schain) is carried inside the OpenRTB request. It lists every company that was paid for the impression, in order, so a buyer can check each one against that company's sellers.json file.

complete
1 if the chain lists every participant back to the original seller, 0 if not.
nodes
The ordered list of participants. Each node describes one hop.
asi
The advertising system domain of that participant (for PeopleAds: peopleads.co).
sid
The seller ID assigned by that system, matching its sellers.json entry.
hp
1 when that participant handles payment for the impression.

How schain is passed and validated for a given connection is confirmed during technical onboarding.

Who we represent, in public.

Sellers.json is a public file listing the sellers an advertising system works with, each with its seller ID and seller type (publisher, intermediary or both). Buyers use it to verify the sellers named in ads.txt and schain.

/sellers.json

The file is published and is updated as seller records are verified. If you are a partner and your entry is missing or incorrect, write to us.

Authorised on your domain.

Ads.txt (websites) and app-ads.txt (apps, hosted on the developer's website) let a publisher declare which companies are allowed to sell its inventory. The records must be published by the publisher on its own domain; PeopleAds cannot publish them for you.

peopleads.co, <seller ID>, <DIRECT | RESELLER>, <certification authority ID (optional)>
Domain
The advertising system domain: peopleads.co.
Seller ID
The account ID PeopleAds assigns to you. It must match your entry in our sellers.json.
DIRECT
You control the account and are paid directly for the inventory.
RESELLER
Another company sells your inventory through its own PeopleAds account.

We send the exact lines for your account during onboarding. Do not copy lines from other publishers.

From first email to live traffic.

  1. 1

    Introduction

    Tell us about your inventory or demand, environments and formats.
  2. 2

    Technical review

    We agree the connection type, specifications and privacy signal handling.
  3. 3

    Authorisation

    Seller IDs, ads.txt / app-ads.txt lines and sellers.json entries are set up.
  4. 4

    Testing and launch

    Requests and responses are checked before traffic is scaled.

Questions about an integration?

Send your documentation, endpoint details or questions to $contact@peopleads.co, or use the contact form.

Let's get
connected.

Supply, demand or technology integrations. Tell us what you are working with.

Let's connectcontact@peopleads.co