TripleLift supplier ingest

TripleLift runs the TripleLift Exchange and accepts server-to-server supply over OpenRTB. This profile covers the requests supply partners send and TripleLift's responses, not the requests TripleLift sends to DSPs.

Direction and version

Server-to-server supply partners send bid requests to the TripleLift Exchange, and TripleLift returns bid responses.

OpenRTB 2.x JSON with integer flags. Native 1.2 requests are JSON strings in imp.native.request.

The RTBlint profile triplelift-supplier checks requests and responses against the published contract.

Rules beyond the OpenRTB spec

  • Each impression needs imp.tagid, the TripleLift placement name or ID, and at least one media object.
  • imp.banner.format is required and must list a size. Exact w and h are a documented fallback when format is absent.
  • Video and audio need mimes, Native needs request, and deals need id.
  • The App table marks app.bundle required, while the prose says an app ID or bundle is not strictly required.
  • site and app must not both appear.
  • Native image assets need type, and an exact or minimum image size is recommended.
  • A Native response may use assetsurl only when the request set aurlsupport to 1. An absent aurlsupport means unsupported.
  • Returned Native event trackers must use an event and method the request offered. IDs are standard values or exchange-specific values of 500 and above.
  • A Native jstracker must be HTML with script tags.

Documented extensions

PathMeaning
regs.extAccepted location for GDPR, CCPA, and GPP signals alongside the regs fields.

What the validator checks for this profile

Validate against this contract

Open the tester with the TripleLift supplier ingest profile, or run:

rtblint validate --profile triplelift-supplier request.json

Similar integrations