Inventory Targeting (Open and Private Exchanges)
Overview
Targeting by Exchanges permits the inclusion or exclusion of Ad Exchange marketplaces. By default, all private exchanges set-up at the network level are targeted by your campaigns.
Targeting Open Exchanges
Select Inventory from the Pre-Bid Targeting pop-up in the DSP.
2. The DSP will display a list of Open Exchanges, along with the Name and corresponding Deal ID. By default, all Open Exchanges set up at the network level are targeted by your campaigns.
3. Deselect the Open Exchange(s) you wish you exclude from your campaign. Additionally, you can filter the list of Open Exchanges displayed by clicking into the search bar under the Open Exchange or Deal ID column headers, and enter the Name or ID of the exchanges you want to target
Targeting Private Exchanges
To capture Deal IDs through reporting and to ensure you are bidding only on the specified private exchanges, enable the Auto-Target Evergreen Deals option above the Private Exchanges grid.
Select the Private Exchanges Tab.
2. The DSP will display a list of Private Exchanges, along with their corresponding Name, Deal ID, Media Property, Exchange ID, Exchange, and Evergreen Status. By default, no Private Exchanges are enabled. You can filter the list of Private Exchanges displayed by clicking into the search bar under the Private Exchange or Deal ID column headers, and enter the Name or ID of the deals you want to target.
Users can also view the Bid Requests column where current day bid requests for each deal listed will be shown - example below:
Including All Open or Private Exchanges
Click the checkbox located in the upper-left corner to select (or deselect) all items in the Open or Private Exchanges list.
Supported Ad Sizes for Each Exchange
Please reference this table when you notice that certain ad sizes are still 'pending' audit. It could very well be the case that the major display ad exchanges for which we provide manual audit status for (AppNexus, AdX & AdX SSL) do not support the ad sizes in question. Table pulled from Placement Size Map and verified with Supply that the table is up to date as of 10/4/2016 (need to connect on VPN to view)
Ad Size | Exchange(s) that support placement size |
320x75 | AppNexus |
640x480 | AppNexus |
120x90 | FLUCT, AOL, GENI |
1000x300 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
768x1024 | Rubicon, FLX, BSW, MPX, OPX, AppNexus, ADXSSL, ADX |
468x60 | Rubicon, PMX, CCI, BSW, RMX, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX |
480x320 | Rubicon, FLX, BSW, MPX, OPX, AppNexus, ADXSSL, ADX |
125x125 | FLUCT, GENI |
250x800 | Rubicon, AppNexus |
800x80 | AppNexus |
970x90 | Rubicon, PMX, BSW, AOL, OPX, AppNexus, CNX, ADXSSL, ADX, CSL |
1024x90 | AOL |
480x80 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
980x400 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
468x400 | Rubicon |
300x300 | AppNexus |
300x100 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
300x1050 | Rubicon, PMX, BSW, OPX, AppNexus, ADXSSL, ADX, CSL |
Ad Size | Exchange(s) that support placement size |
180x150 | PMX, BSW, RMX, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX, CSL |
320x100 | Rubicon, BSW, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX |
980x240 | BSW |
1024x768 | Rubicon, FLX, BSW, MPX, OPX, AppNexus, ADXSSL, ADX |
360x50 | AppNexus |
120x60 | RMX |
300x50 | Rubicon, PMX, SMX, FLX, BSW, AOL, OPX, AppNexus, CNX, ADXSSL, ADX, CSL |
980x120 | Rubicon, PMX, BSW, AppNexus, ADXSSL, ADX |
276x91 | BSW |
120x20 | SMX, FLX |
375x50 | AppNexus |
970x250 | Rubicon, PMX, BSW, RMX, LJX, AOL, OPX, AppNexus, ADXSSL, ADX, CSL |
480x70 | Rubicon, AppNexus, ADXSSL, ADX |
480x75 | AppNexus |
3x3 | BSW |
980x90 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
250x250 | Rubicon, PMX, BSW, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX |
320x50 | Rubicon, PMX, CCI, BSW, FLUCT, MPX, GENI, ADXSSL, SMX, FLX, RMX, AOL, OPX, AppNexus, CNX, ADX, CSL |
930x180 | Rubicon, BSW |
300x250 | Rubicon, PMX, CCI, BSW, LJX, FLUCT, MPX, GENI, ADXSSL, SMX, FLX, RMX, AOL, OPX, AppNexus, CNX, ADX, CSL |
180x500 | Rubicon, BSW, RMX, AOL, AppNexus, ADXSSL, ADX |
728x90 | Rubicon, PMX, CCI, BSW, LJX, FLUCT, MPX, GENI, ADXSSL, SMX, FLX, RMX, AOL, OPX, AppNexus, CNX, ADX, CSL |
980x150 | Rubicon, PMX, BSW, AppNexus, ADXSSL, ADX |
320x160 | AppNexus |
320x480 | Rubicon, SMX, FLX, BSW, RMX, AOL, MPX, OPX, AppNexus, ADXSSL, ADX |
930x600 | Rubicon, BSW, AppNexus |
160x90 | FLUCT, GENI |
211x48 | BSW |
234x60 | Rubicon, BSW, RMX, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX, CSL |
120x240 | Rubicon, BSW, RMX, FLUCT, GENI, OPX, AppNexus, ADXSSL, ADX |
200x200 | Rubicon, RMX, FLUCT, GENI, AppNexus, ADXSSL, ADX |
2x4 | Rubicon, AppNexus |
768x80 | AppNexus |
1280x100 | ADXSSL, ADX |
200x600 | AppNexus |
300x600 | Rubicon, PMX, BSW, LJX, FLUCT, GENI, ADXSSL, RMX, AOL, OPX, AppNexus, CNX, ADX, CSL |
120x600 | Rubicon, PMX, BSW, RMX, FLUCT, AOL, GENI, OPX, AppNexus, ADXSSL, ADX, CSL |
220x105 | AppNexus |
400x300 | PMX |
320x320 | AppNexus |
1800x1000 | Rubicon |
320x400 | AppNexus |
328x72 | OPX |
970x66 | PMX |
120x45 | RMX |
216x36 | SMX, FLX, BSW |
160x600 | Rubicon, PMX, CCI, BSW, LJX, FLUCT, GENI, ADXSSL, RMX, AOL, OPX, AppNexus, CNX, ADX, CSL |
240x400 | Rubicon, BSW, OPX, AppNexus, ADXSSL, ADX |
800x250 | Rubicon, BSW, AppNexus, ADXSSL, ADX |
1x1 | Rubicon, PMX, BSW, DISHX, DMX, SPX, MPX, ATX, ADXSSL, TRMR, STX, AppNexus, LRX, ADX, BRL |
600x80 | AppNexus |
1000x90 | Rubicon |
168x28 | SMX, FLX, AppNexus |
180x90 | FLUCT, GENI |
336x280 | Rubicon, PMX, BSW, AOL, OPX, AppNexus, ADXSSL, ADX, CSL |
Creative Approval for Ads with Location Blocking Tech
My ads that were set up with location blocking* have been rejected by one or more ad exchanges.
Cause
As part of the ad audit process improvements made by Zeta over the summer of 2016, the platform is no longer able to run third-party ad tags that are set up with location blocking* technology. Historically, location block technology created a risk where ad exchanges would not approve ads because they could not see the creative during an audit, most often caused by the given exchange's audit team being located outside of the targeted location; this occurrence was most common for AppNexus auditing.
This risk led to the change in policy where Zeta no longer allows for ads set up with location blocking* that do not also include one of the preview macros detailed below.
*For the purpose of this article, "location blocking" is referring to third-party media verification technology such as DoubleVerify or Integral Ad Science (IAS) that allows the ad to display a PSA or blank creative when impressions are deemed to being served outside of intended location or content. This technology is referred to below as "ad blocking."
Procedure
To comply with Zeta's internal ad audit process and with exchanges' external audits, ad-blocking technology has a built-in Preview mode. Preview mode is enabled dynamically for a single impression during a preview by audit processes, by passing a special parameter value to the third-party location blocking technology. All other impressions served not in preview mode continue to have ad-blocking enabled. The following are vendor-specific instructions, intended for Ad Operations staff trafficking the ads with ad-blocking technology.
FAQ
Question | Answer |
|---|---|
What exchanges are my ads delivering on? | While the DSP can serve Ads across several different Ad Exchanges, we only display audit information for a small handful of them. Zeta is integrated with 56 Ad Exchanges, giving you a wide range of inventory and opportunities to deliver your Ads. Only 11 of these 56 Ad Exchanges provide Video inventory, one of them being Google ADX. Of these 56 Exchanges, we display Audit information from 4:
|
Does Zeta guarantee the delivery of companion banners with Video placements? | Zeta cannot guarantee the delivery of companion banner impressions as exchanges do not guarantee a 1:1 ratio of Video Ad/ companion banner delivery. |