Overview

This article summarizes specific information for the DSPs connected to Equativ.

AppNexus / Xandr

AppNexus / Xandr deals

• deals have to be created in Equativ without any Deal ID (Equativ automatically pushes the deal into the AppNexus / Xandr platform)
• AppNexus / Xandr does not bid on inventory with the transparency settings "Blind" or "Semitransparent"
• AppNexus / Xandr only supports one buyer per deal
• do not edit AppNexus / Xandr attributes in deals – any modifications there would be ignored by AppNexus / Xandr, and thus not synced. Attributes that cannot be modified are: name, deal ID, buyer, seller, type. You can still change insertions in your deal, but if you want to change the deal's properties you will need to create a new deal.

AppNexus / Xandr open auctions

To buy in open auctions, buyers need to proceed as follows:

• Step #1: find "Smart RTB+" under Inventory Targeting > 3rd Party Inventory > Smart RTB+ (Member ID 3703); see screenshot "Step #1" below)
• Step #2: find the publisher; your publisher name in AppNexus / Xandr consists of your network ID and network name at Equativ; example: "1234 - your network name" (see screenshot "Step #2" below)

Step #1

Step #2

DV360 (Display Video 360)

Equativ not visible as an SSP

As a buyer, if you cannot see Equativ (as an SSP) in the DV360 (Display Video 360) user interface, follow these instructions:

• navigate to Partner
• edit Partner
• go to Exchanges
• find SmartRTB+
• select checkbox
• click Save

Hosting source

Problems may occur if the hosting source of the creative is a third party (e.g. Flashtalking).

Custom affinity targeting / affinity audiences

The buyer should not use custom affinity targeting / affinity audiences: one of the limitations of custom affinity targeting is that it can only be used on adx deals:

"Affinity audiences are currently only targetable on DoubleClick Ad Exchange inventory, so if your line item targets only affinity audiences, it will only buy from Ad Exchange. However, if your targeting includes an affinity segment and one or more first- or third-party audience lists in a logical OR relationship, your line item will still be able to purchase impressions from exchanges other than Ad Exchange."

User cookie lifetime

The lifetime of the user cookie (user matching) is 13 months.

Hawk (Tabmo)

In case of deals with Hawk (Tabmo) for native ads, the connected RTB+ insertion:

• must contain a specified size in the corresponding field (default size: 0x0)
• must have the option "icon required" enabled to have a creative sent in bid responses 

Pocketmath

• through a deal, buyers challenge the network bid floor and the deal bid floor; thus, buyers need to bid higher than both of these bid floors in order to win the deal
• no support of multi-size bid requests

Piximedia

To ensure a 100% bid rate for Programmatic Guaranteed, you need to make sure that Piximedia has allowlisted all domains associated with the site(s) selected for the guaranteed deal in Monetization.   

Bidswitch

In case of Bidswitch, you need to target the whole seat, so for a deal with a Bidswitch connected DSP you need to target the whole Bidswitch DSP as a seat/buyer. For example, for “Yahoo DSP” buyers, you need to target the main seat "Yahoo DSP (Verizon) (74 - Bidswitch (Iponweb))". If you target “Yahoo DSP” buyers instead, the deal will not work.

• You can target: Bidswitch (Partner) > Yahoo DSP (whole DSP as a seat/buyer)
• You cannot target: Bidswitch (Partner) > (Yahoo DSP) > Yahoo DSP internal buyers/seat

Note: the same approach works for StackAdapt, Zeta Global DSP, Verizon, Roku, adelphic, etc.

Adform

In case of native ad delivery with Adform, it is strongly recommended that buyers strictly comply with the standard and refrain from any customizations of the native creative. This is of particular relevance in case of deal creation and deal troubleshooting.

Mediasmart

To avoid geo-targeting related issues for programmatic guaranteed deal delivery, Mediasmart must also apply geo-targeting on their side for their campaign(s).