Connect your own DSPs

Bring a demand-side platform you already work with to your channels, choose who it pays, and track what it clears.

If you have a deal with a demand-side platform (DSP), you can connect it to your channels. LtvAdx then sends it an OpenRTB 2.6 bid request when a break opens on a channel you chose, and it competes in the open auction. LtvAdx reviews every connection before it receives requests.

A connected DSP never displaces your own direct campaigns or your deals. It competes only for the open-auction slot, and its bid must beat the best LtvAdx advertiser bid to win.

Before you start

For a DSP to receive a bid request on a channel, all of these must hold:

• The connection is Active, which means LtvAdx approved it.
• The channel has RTB Enabled ticked on Channels & Apps. A new channel has it off.
• Your account is listed in LtvAdx's public sellers list. That follows a successful check on Authorized Sellers.
• The channel has a store bundle ID, or you have a website on file, so the DSP can identify the inventory.
• The channel is able to take LtvAdx demand. See Authorized Sellers.
• LtvAdx has not restricted open-auction demand on your account.

Steps

1. Open My DSPs and select Connect a DSP.
2. Enter a Name for the DSP.
3. Enter the Bid endpoint (https). LtvAdx posts a video bid request there. A 204 or an empty response is a no-bid. Bids must be in US dollars.
4. If the DSP needs a credential, enter the Auth header name and the Auth value. The value is stored write-only. The list afterwards shows only its last four characters.
5. Choose the OpenRTB version header, the Timeout (ms) (10 to 100) and a Max requests / second (0 = no limit) limit. LtvAdx waits at most 100 ms for any DSP; a bid after that is discarded. The version only sets the version header; the request body is the same for both.
6. Choose Who does this DSP pay? (see below).
7. Tick the channels it may bid on. None ticked means all your channels.
8. Select Submit for approval.

The row then shows Waiting for LtvAdx approval. When LtvAdx approves it, it becomes Active and starts receiving requests shortly. If it is rejected, the row shows Rejected and the reason.

Who does this DSP pay?

For this choice you also give the DSP's billing contact and payment terms in days.

Managing a connection

• The pencil edits it. Changing the endpoint, the credential or who it pays pauses bidding and sends it back for approval.
• Pause stops requests. Resume is offered only for a connection LtvAdx approved before.
• The bin removes it. A removed connection stops bidding and can't be turned back on.
• Owner, admin and manager seats can change connections. Analyst and finance seats can read the page.

What the table shows

For the current month, per DSP: Impressions (month), Cleared (month) (what the DSP paid for them) and LtvAdx fee (month). See Publisher payouts for how amounts reach you.

Good to know

• Your block list goes with every request, and a bid that names a blocked domain or category is dropped.
• With a sensitive category ticked on Brand Safety, or on a children's channel, a DSP's ad also needs a LtvAdx staff review first, and its bid must say what it advertises. See Outside DSPs and sensitive categories.
• A viewer served contextually, for example on a children's channel or without consent, is not identified to the DSP. It gets no advertising ID.
• Your floor is sent to the DSP as the minimum price.
• If a DSP never wins, it may simply be outbid, or bids may be arriving after the timeout. LtvAdx does not show per-request detail to publishers.