You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update Appnexus Bid Parameters for app and Prebid 1.x v.s. legacy (#932)
* Adding addiional info on onEvent handlers, and PBS timeout
* Appnexus adaptor parameters. Added for prebid/Prebid.js#2973, sorted out the prebid 1.x versus the legacy ast/jpt adaptors. Added disclaimer on
* Updating sample native adserver creative to add in click tracking
* made minor changes from review. Also added video params tabel from AST to 1.x version and info about keywords to the upgrade section
* Fix to typos
Copy file name to clipboardExpand all lines: adops/setting-up-prebid-native-in-dfp.md
+9-7Lines changed: 9 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,8 @@ In this example, we're targeting `"prebid_native_adunit"`, so the *Size* is set
44
44
Add the HTML and CSS that define your native ad template. Note that `%%PATTERN%%` macros can be included in either field, and the HTML can contain JavaScript. For more information, see the [DFP native styles docs](https://support.google.com/dfp_premium/answer/6366914).
45
45
46
46
{: .alert.alert-danger :}
47
-
**Native impression tracking requirements**
48
-
You must include the `postMessage`code snippet as shown in the screenshot and example code below so impression trackers will fire.
47
+
**Native impression and click tracking requirements**
48
+
You must include the `postMessage`and `onclick` JavaScript snippets as shown in the example code below so that impression trackers and click trackers will fire.
49
49
50
50
{: .pb-img.pb-lg-img :}
51
51

Advantages of using the `appnexusAst` adapter over the `appnexus`
15
-
adapter include:
16
-
17
-
- Requests all the adUnits at once, which reduces latency on page
18
-
19
-
- Supports additional formats (such as Video)
20
-
21
-
- Will continue to be upgraded as enhancements are made to Prebid.js
22
-
for expanding capabilities
23
-
24
14
{: .alert.alert-warning :}
25
-
As part of the transition to Prebid 1.0, the AppNexus AST adapter will become the standard (and only) AppNexus adapter (and be renamed to "AppNexus"). From a developer's perspective, the primary change from the legacy adapter is that keywords must be passed using the `keywords` parameter documented below.
15
+
Prebid.js 0.x includes two AppNexus Adaptors: `appnexus` and `appnexusAst`. As part of the transition to Prebid 1.0, the AppNexus AST adapter will become the standard (and only) AppNexus adapter (and be renamed to "AppNexus").
26
16
27
-
{: .alert.alert-danger :}
28
-
All AppNexus placements included in a single call to `requestBids` must belong to the same publisher object. If placements from two different publishers are included in the call, the AppNexus bidder may not return any demand for those placements. <br />
29
-
*Note: This requirement does not apply to adapters that are [aliasing]({{site.baseurl}}/dev-docs/publisher-api-reference.html#module_pbjs.aliasBidder) the AppNexus adapter.*
30
17
31
-
### bid params
18
+
### Bid Params
32
19
33
20
{: .table .table-bordered .table-striped }
34
21
| Name | Scope | Description | Example | Type |
@@ -39,13 +26,17 @@ All AppNexus placements included in a single call to `requestBids` must belong t
39
26
|`video`| optional | Video targeting parameters. See the [video section below](#appnexus-ast-video) for details. |`{ playback_method: ['auto_play_sound_off'] }`|`object`|
40
27
|`invCode`| optional | The inventory code from AppNexus. Must be used with `member`. |`'abc123'`|`string`|
41
28
|`member`| optional | The member ID from AppNexus. Must be used with `invCode`. |`'12345'`|`string`|
42
-
|`reserve`| optional | Sets a floor price for the bid that is returned|`0.90`|`float`|
29
+
|`reserve`| optional | Sets a floor price for the bid that is returned. If floors have been configured in the AppNexus Console, those settings will override what is configured here.|`0.90`|`float`|
43
30
44
31
(Sizes set in `adUnit` object will also apply to the AppNexus bid requests.)
45
32
33
+
{: .alert.alert-danger :}
34
+
All AppNexus placements included in a single call to `requestBids` must belong to the same publisher object. If placements from two different publishers are included in the call, the AppNexus bidder may not return any demand for those placements. <br />
35
+
*Note: This requirement does not apply to adapters that are [aliasing]({{site.baseurl}}/dev-docs/publisher-api-reference.html#module_pbjs.aliasBidder) the AppNexus adapter.*
36
+
46
37
<aname="appnexus-ast-video"></a>
47
38
48
-
#### video
39
+
#### video parameters
49
40
50
41
The following video parameters are supported. For more information, see the video parameters in the [OpenRTB specification](http://www.iab.com/wp-content/uploads/2016/01/OpenRTB-API-Specification-Version-2-4-DRAFT.pdf).
51
42
@@ -59,3 +50,11 @@ The following video parameters are supported. For more information, see the vid
59
50
|`skippable`| Boolean which, if `true`, means the user can click a button to skip the video ad. Defaults to `false`. |`boolean`|
60
51
|`playback_method`| Array of strings listing playback methods supported by the publisher. Allowed values: `"auto_play_sound_on"`; `"auto_play_sound_off"`; `"click_to_play"`; `"mouseover"`; `"auto_play_sound_unknown"`. |`Array<string>`|
61
52
|`frameworks`| Array of integers listing API frameworks supported by the publisher. Allowed values: None: `0`; VPAID 1.0: `1`; VPAID 2.0: `2`; MRAID 1.0: `3`; ORMMA: `4`; MRAID 2.0: `5`. |`Array<integer>`|
53
+
54
+
### Advantages of using the Appnexus AST (legacy) Adaptor over the AppNexus (legacy) Adaptor
55
+
56
+
- Requests all the adUnits at once, which reduces latency on page
57
+
58
+
- Supports additional formats (such as Video and Native)
59
+
60
+
- Uses the same endpoints and parameter settings as the Prebid 1.x AppNexus adaptor.
Prebid.js 0.x includes two AppNexus Adaptors: `appnexus` and `appnexusAst`. As part of the transition to Prebid 1.0, the AppNexus AST adapter will become the standard (and only) AppNexus adapter (and be renamed to "AppNexus"). From a developer's perspective, the primary change from the AppNexus (legacy) adapter to either the AppNexus AST (legacy) or Prebid 1.x adaptor is that keywords must be passed using the `keywords` parameter instead of an `"arbitraryKey"`.
|`placementId`| required | The placement ID from AppNexus. You may identify a placement using the `invCode` and `member` instead of a placement ID. |`234234`|`int`|
23
+
|`"arbitraryKey"`| optional | This key can be *any publisher-defined string*. The value (also a string) maps to a querystring segment for enhanced buy-side targeting. Multiple key-value pairs can be added as shown [below](#appnexus-pub-keys). |`'genre': 'rock'`|`keyValue`|
24
+
|`invCode`| optional | The inventory code from AppNexus. Must be used with `member`. |`'abc123'`|`string`|
25
+
|`member`| optional | The member ID from AppNexus. Must be used with `invCode`. |`'12345'`|`string`|
26
+
27
+
<aname="appnexus-pub-keys" />
28
+
29
+
#### Support for publisher-defined keys
30
+
31
+
To pass in a publisher-defined key whose value maps to a querystring segment for buy-side targeting, set up your `params` object as shown below. For more information, see the [query string targeting documentation](https://wiki.appnexus.com/x/7oCzAQ) (login required).
0 commit comments