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
- Run `markdownlint` on any edited Markdown files using the repository configuration with `markdownlint --config .markdownlint.json README.md`. Replace `README.md` with each file you change.
4
+
- If lint errors occur, fix them before creating a pull request.
5
+
- Verify the site builds with `bundle exec jekyll build` when possible.
6
+
- Please name your branch to include codex or agent in the branch name
7
+
- If you cannot run markdownlint please warn your user to setup their environment using the instructions in README.md and document your failure in your pr description
**Important:** Google Ad Manager has a key-value key character [limit](https://support.google.com/dfp_premium/answer/1628457?hl=en#Key-values) of up to **20 characters**. Some of the keys without truncation will exceed 20 chars. Prebid.js automatically truncates the key length to 20 characters. For example, `hb_adid_longBidderName` is truncated to `hb_adid_longBidderNa` (`me` is truncated). Note that the key is case-sensitive. To get the exact key-value keys for each bidder, find them at [Bidder Params](/dev-docs/bidders.html).
2
4
3
5
{: .table .table-bordered .table-striped }
4
-
| Default Key | Scope | Description | Example |
5
-
| :---- |:---- | :---- | :---- |
6
-
|`hb_pb_BIDDERCODE`| Required | The price bucket. Used by the line item to target. Case sensitive and truncated to 20 chars. The `BIDDERCODE` is documented at [Bidder Params](/dev-docs/bidders.html). |`hb_pb_rubicon` = `2.10`|
7
-
|`hb_adid_BIDDERCODE`| Required | The ad Id. Used by the ad server creative to render ad. Case sensitive and truncated to 20 chars. The `BIDDERCODE` is documented at [Bidder Params](/dev-docs/bidders.html). |`hb_adid_longBidderNa` = `234234`|
6
+
7
+
| Default Key | Scope | Description | Example |
8
+
| :---- | :---- | :---- | :---- |
9
+
|`hb_pb_BIDDERCODE`| Required | The price bucket. Used by the line item to target. Case sensitive and truncated to 20 chars. The `BIDDERCODE` is documented at [Bidder Params](/dev-docs/bidders.html). |`hb_pb_rubicon` = `2.10`|
10
+
|`hb_adid_BIDDERCODE`| Required | The ad Id. Used by the ad server creative to render ad. Case sensitive and truncated to 20 chars. The `BIDDERCODE` is documented at [Bidder Params](/dev-docs/bidders.html). |`hb_adid_longBidderNa` = `234234`|
8
11
|`hb_size_BIDDERCODE`| Optional | This is not required for adops. Case sensitive and truncated to 20 chars. |`hb_size_appnexus` = `300x250`|
Copy file name to clipboardExpand all lines: adops/setting-up-prebidjs-with-Smart-Ad-Server.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,15 +39,15 @@ Proceed as follows:
39
39
- Make sure you specify the timeout; the timeout is the maximum time to wait until the Smart AdServer ad call is executed - even if some partners have not responded yet.
40
40
- Implement the Prebid.js file on the site.
41
41
42
-
This step is also documented [here](https://support.smartadserver.com/s/article/Holistic-Setup#implement-wrapper).
42
+
This step is also documented [Smart AdServer setup documentation](https://support.smartadserver.com/s/article/Holistic-Setup#implement-wrapper).
43
43
44
44
### Step 2 - Implement Smart AdServer’s tag
45
45
46
46
Smart AdServer’s OneCall tagging is strongly recommended. With OneCall, you can set header bidding data per `tagId`. The `tagId` is the Id of the container (`<div>`), where the ad will be displayed. The `tagId` format is `sas_<formatId>`. e.g. `sas_1234`.
47
47
48
48
Make sure you use Smart AdServer’s **new OneCall tagging**, which uses POST requests with all the necessary information in the request body; simply check if you see the `formats` array in your tag. If you see `formatId`, you are still dealing with an old tag - in this case, get back to your service contact at Smart AdServer.
49
49
50
-
For samples of both the new and legacy OneCall as well as a full implementation example, read [here](https://support.smartadserver.com/s/article/Holistic-Setup#onecall).
50
+
For samples of both the new and legacy OneCall as well as a full implementation example, read [OneCall documentation](https://support.smartadserver.com/s/article/Holistic-Setup#onecall).
51
51
52
52
**Additional resources**:
53
53
@@ -63,7 +63,7 @@ Things to keep in mind for the Setup in [Smart AdServer’s UI](https://manage.s
63
63
- The Holistic+ feature must be enabled on the network.
64
64
- You must use the official and Holistic RTB+ script templates in the insertions.
65
65
66
-
For more details, read [here](https://support.smartadserver.com/s/article/Holistic-Setup#setup-ui).
66
+
For more details, read [setup instructions](https://support.smartadserver.com/s/article/Holistic-Setup#setup-ui).
Copy file name to clipboardExpand all lines: dev-docs/activity-controls.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -235,7 +235,7 @@ If `allow` is not defined, the rule is assumed to assert **true** (i.e. allow th
235
235
236
236
#### Always include a particular bidder in auctions
237
237
238
-
This is similiar to the 'vendor exception' feature of the [TCF Control Module](/dev-docs/modules/tcfControl.html). This would always allow bidderA to participate in the auction, even without explicit consent in GDPR scenarios. It might indicate, for instance, that this is a 'first party bidder'.
238
+
This is similar to the 'vendor exception' feature of the [TCF Control Module](/dev-docs/modules/tcfControl.html). This would always allow bidderA to participate in the auction, even without explicit consent in GDPR scenarios. It might indicate, for instance, that this is a 'first party bidder'.
Copy file name to clipboardExpand all lines: dev-docs/bidder-adaptor.md
+19-12Lines changed: 19 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -278,7 +278,7 @@ Prebid.js core now includes support for gzip compression of bidder request paylo
278
278
Prebid will pass compressed payloads if the following criteria are met:
279
279
280
280
* Participating bidders must implement compression support on their server-side endpoint before making a change in their bid adapter in Prebid.js
281
-
* Once server-side support is present, `request.options.endpointCompression = true` needs to be set for a bidder's outgoing requests within their Prebid.js bid adapter (An example of this can be viewed [here](https://github.com/prebid/Prebid.js/blob/master/modules/pubmaticBidAdapter.js#L730))
281
+
* Once server-side support is present, `request.options.endpointCompression = true` needs to be set for a bidder's outgoing requests within their Prebid.js bid adapter (see the [PubMatic adapter example](https://github.com/prebid/Prebid.js/blob/master/modules/pubmaticBidAdapter.js#L730))
282
282
* The browser must support gzip compression (Prebid core has a built-in utility function to check this)
283
283
284
284
If the above criteria is met, Prebid.js core will do the following:
@@ -389,6 +389,7 @@ When disabled, `auctionId`/`transactionId` are set to `null`; `ortb2.source.tid`
389
389
There are a number of important values that a publisher expects to be handled in a standard way across all Prebid.js adapters:
390
390
391
391
{: .table .table-bordered .table-striped }
392
+
392
393
| Parameter | Description | Example |
393
394
| ----- | ------------ | ---------- |
394
395
| Ad Server Currency | If your endpoint supports responding in different currencies, read this value. | config.getConfig('currency.adServerCurrency') |
@@ -423,6 +424,7 @@ You shouldn't call your bid endpoint directly. Rather, the end result of your bu
423
424
ServerRequest objects. These objects have this structure:
424
425
425
426
{: .table .table-bordered .table-striped }
427
+
426
428
| Attribute | Type | Description | Example Value |
|`requestId`| Required | The bid ID that was sent to `spec.buildRequests` as `bidRequests[].bidId`. Used to tie this bid back to the request. | 12345 |
@@ -650,7 +653,7 @@ Sample data received by this function:
650
653
651
654
The `onBidBillable` function will be called when it deems a bid to be billable. When a bid wins, it is by default also billable. That is, by default, onBidWon and onBidBillable will be called one after the other. However, a publisher can flag adUnits as being separately billable: `pbjs.addAdUnits({deferBilling: true, ...})`. Winning bids for adUnits with `deferBilling` set to true, trigger the onBidWon function but not the onBidBillable function. When appropriate (e.g. an interstitial is displayed), the publisher may then call the public API method, `pbjs.triggerBilling(winningBidObjectToBill)` passing the winning bid to be billed, which will trigger onBidBillable.
652
655
653
-
Sample data received by this function (same as what is recieved for onBidWon):
656
+
Sample data received by this function (same as what is received for onBidWon):
654
657
655
658
```javascript
656
659
{
@@ -760,6 +763,7 @@ spec.aliases can be an array of strings or objects.
760
763
If the alias entry is an object, the following attributes are supported:
761
764
762
765
{: .table .table-bordered .table-striped }
766
+
763
767
| Name | Scope | Description | Type |
764
768
|-------|-------|---------------|-----------|
765
769
|`code`| required | shortcode/partner name |`string`|
@@ -814,7 +818,7 @@ If your adapter supports banner and video media types, make sure to include `'ba
814
818
815
819
### Step 2: Accept video parameters and pass them to your server
816
820
817
-
Video parameters are often passed in from the ad unit in a `video` object. As of Prebid 4.0 the following paramters should be read from the ad unit when available; bidders can accept overrides of the ad unit on their bidder configuration parameters but should read from the ad unit configuration when their bidder parameters are not set. Parameters one should expect on the ad unit include:
821
+
Video parameters are often passed in from the ad unit in a `video` object. As of Prebid 4.0 the following parameters should be read from the ad unit when available; bidders can accept overrides of the ad unit on their bidder configuration parameters but should read from the ad unit configuration when their bidder parameters are not set. Parameters one should expect on the ad unit include:
818
822
819
823
* mimes
820
824
* minduration
@@ -962,7 +966,7 @@ Adapter must add following new properties to bid response
962
966
}
963
967
```
964
968
965
-
Appnexus Adapter uses above explained approach. You can refer [here](https://github.com/prebid/Prebid.js/blob/master/modules/appnexusBidAdapter.js)
969
+
Appnexus Adapter uses the approach explained above. You can see an example in the [AppNexus adapter](https://github.com/prebid/Prebid.js/blob/master/modules/appnexusBidAdapter.js)
966
970
967
971
Adapter must return one [IAB accepted subcategories](https://iabtechlab.com/wp-content/uploads/2017/11/IAB_Tech_Lab_Content_Taxonomy_V2_Final_2017-11.xlsx) (links to MS Excel file) if they want to support competitive separation. These IAB sub categories will be converted to Ad server industry/group. If adapter is returning their own proprietary categroy, it is the responsibility of the adapter to convert their categories into [IAB accepted subcategories](https://iabtechlab.com/wp-content/uploads/2017/11/IAB_Tech_Lab_Content_Taxonomy_V2_Final_2017-11.xlsx) (links to MS Excel file).
968
972
@@ -971,6 +975,7 @@ If the demand partner is going to use Prebid API for this process, their adapter
0 commit comments