Equativ bidder contract

Equativ, formerly Smart AdServer, runs a sell-side platform whose SSP sends OpenRTB requests to connected bidders. Its bidder field page points to the same request and response tables used for supplier integrations and leaves bidder-specific fields to account managers.

Direction and version

Equativ's SSP sends bid requests to DSP bidders, and bidders return bid responses to Equativ.

The bidder pages say fields follow OpenRTB 2.6, while the setup guide describes 2.2 to 2.5 compliance with 2.6 used for SSAI, CTV, and rewarded inventory. The version travels in an x-openrtb-version header, and Native 1.0 and 1.2 requests are JSON strings.

The RTBlint profile equativ checks requests and responses against the published contract.

Rules beyond the OpenRTB spec

imp.video.plcmt may use values 1 to 9, beyond the four values the specification defines.
Legacy regs.ext.gdpr, user.ext.consent, user.ext.eids, and source.ext.schain are accepted. When both forms are sent, the 2.6 field wins.
imp.video.ext.rewarded is marked obsolete in favor of imp.rwdd.
When the request's dsarequired is 2 or 3, every bid must carry a DSA object. Advertiser and payer names in bid.ext.dsa are limited to 100 characters.
The response ext.dealtype is one of GuaranteedDeal, AuctionPackage, DirectDeal, or PrivateAuction, and is absent for the open auction.
Banner adm must be text/html, and macros are allowed only in nurl, burl, and adm.
The HTTP timeout is 100 milliseconds. A no-bid may be HTTP 204, or HTTP 200 with an empty object, an empty seatbid, or nbr.
Equativ publishes loss codes 1001 to 1007 on top of part of the OpenRTB 2.5 loss list. Loss notices stay off until Equativ enables them for the seat.

Documented extensions

Path	Meaning
`imp.pmp.deals[].ext.smart.guaranteed`	1 marks a programmatic guaranteed deal.
`regs.ext.dsa`	DSA requirements: `dsarequired` 0 to 3, `pubrender` and `datatopub` 0 to 2.
`bid.ext.dsa`	DSA transparency with `behalf`, `paid`, `adrender`, and `transparency`.
`ext.dealtype`	Response-level deal type of the winning bid.
`device.ext.atts`	App Tracking Transparency status.
`site.ext.amp`	AMP page flag.
`imp.video.ext.orientation`	Video orientation.

What the validator checks for this profile

openrtb.profile.equativ.deal_type Equativ dealtype must be one of its four documented strings.
openrtb.profile.equativ.dsa_name_length Equativ DSA advertiser and payer names have a maximum of 100 Unicode characters.
openrtb.profile.equativ.mainline_precedence Equativ prioritizes the mainline field when both mainline and legacy values are present.
openrtb.profile.equativ.obsolete_rewarded The Equativ guide marks video.ext.rewarded obsolete and recommends imp.rwdd. Current 2.6 acceptance is not promised.

Loss and status codes

Equativ loss reason codes

Validate against this contract

Open the tester with the Equativ bidder contract profile, or run:

rtblint validate --profile equativ request.json