OpenRTB S2S guide

This guide describes how to connect a demand partner over a server-to-server (S2S) OpenRTB integration.

Getting Started

To start receiving bid requests, you need to supply us with:

1. Endpoints (URLs) for US, EU, and APAC. Include a port only if it is non-standard (HTTPS defaults to 443, HTTP to 80).
2. QPS limit (if needed). Primis can throttle outbound requests to your cap.
3. Sync URL: required for desktop and mobile web so Primis can cookie-sync and later send user.buyeruid.
4. Seat/campaign identifiers used in your protocol (publisher ID, placement ID, tag ID, or equivalent). Primis maps these to the RTB campaign that will be called.
5. Any fields not standard OpenRTB 2.5: Primis can inject partner-specific extensions and custom key paths into the bid request.
6. Targeting: Primis can restrict when your endpoint is called (domain, geo, device, placement, and other campaign targeting).

Bid Request

Primis follows OpenRTB 2.5.
Selected OpenRTB 2.6 fields are also sent when relevant (for example imp.video.plcmt).

The service can support additional variables or partner-specific customization.

Transport:

• Method: HTTP POST
• Content-Type: application/json; charset=UTF-8
• Currency: USD (bidrequest.cur is ["USD"]; imp.bidfloorcur is USD)

Restrictions

• Supported inventory: inline video
• Supported platforms: desktop, mobile web, and mobile apps
• Bid request timeout is 1000ms (bidrequest.tmax)
• First-price auction is applied (bidrequest.at is set to 1)
• TAG pchain is always sent (bidrequest.source.pchain)
• GDPR, GPP, COPPA, or CCPA consent strings are sent if should be applied
• Schain object is sent according to oRTB 2.5 standard (bidrequest.source.ext.schain), but can support other hierarchies as well
• Supported blocking capabilities (bcat, badv)

User ID Syncing

This applies only to desktop and mobile web traffic

The most convenient method for Primis to perform user sync is as follows:

• Sync type: image pixel
• The partner will provide us with a pixel sync URL, which must include a "redirect" parameter
• Primis will add the redirect URL into the "redirect" parameter with the UUID macro
• Upon receiving the sync request, the partner will replace the macro with the UUID and initiate the redirect pixel