| Contact Magnite (Formerly Rubicon Project) support at [globalsupport@mangite.com](mailto:globalsupport@magnite.com) to use Magnite as a floor provider. |
+| pubx.ai | Reach out to PubX at [hello@pubx.ai](mailto:hello@pubx.ai) to learn more about our AI-powered dynamic floor optimization. |
\ No newline at end of file
diff --git a/dev-docs/modules/index.md b/dev-docs/modules/index.md
index c7731e994a..dd5b4bf164 100644
--- a/dev-docs/modules/index.md
+++ b/dev-docs/modules/index.md
@@ -31,7 +31,7 @@ If you are looking for bidder adapter parameters, see [Bidders' Params]({{site.b
| Module | Description |
|---------------------+--------------|
| [**Currency**](/dev-docs/modules/currency.html) | Converts bid currency into ad server currency based on data in a supplied exchange rate file. |
-| **ConsentManagement** | Collecting and passing consent information in support of privacy regulations:{::nomarkdown}- EU GDPR with optional GDPR Enforcement module
- US Privacy (CCPA)
- EU GDPR with optional GDPR Enforcement module
- US Privacy (CCPA)
Select Bidder Adapters
-{% for page in bidder_pages %}
- {% if page.s2s_only == true %}
- {% continue %}
- {% endif %}
+{% for page in bidder_pages %}{% if page.pbjs == true %}
-{% endfor %}
+{% endif %}{% endfor %}
@@ -517,13 +512,13 @@ Prebid.js is open source software that is offered for free as a convenience. Whi
-
+
-
+
-
+
-
+
@@ -535,19 +530,34 @@ Prebid.js is open source software that is offered for free as a convenience. Whi
+
+
+
+
+
+
+
+
+
+
-
+
+
+## Step 2. Add a line item
+In the *Add a Line Item* section:
+1. For the *Type and Priority* settings, select *Non-Guaranteed* as the type and set the priority to *12*. This ensures the line item will compete with all other demand.
+2. Set the Rate to the price you want to target.
+
+3. In the *Advanced Targeting* section, set the target for *Keywords* to `hb_pb:0.50`
+
+
+For each level of pricing granularity required, one line item/creative pairing will need to be set up.
+
+Line items must be set up to target custom keywords that include bid price information. The bid price keywords will contain how much the buyer bid on the impression.
+
+Prebid Mobile, by default, will send the highest bid price to MoPub using the keyword `hb_pb` but will also submit the key `hb_pb_BIDDERCODE` for each bidder. You can decide to create one set of line items for all bidders or one set of line items for each bidder.
+
+## Step 3. Add creatives to your line item
+Full-screen video creatives must have a *VAST tag* with the *Format* set to *Fullscreen* that includes the code below:
+```
++
+
+The `hb_uuid` variable value is the cache id that will load the ad markup from the bid stored in Prebid Cache. Within each line item, for each ad unit size, there should be one creative with this content.
+
+The XML can be constructed by providing the VAST tag URL as:
+`https://%%KEYWORD:hb_cache_host%%%%KEYWORD:hb_cache_path%%?uuid=%%KEYWORD:hb_uuid%%`
+
+## Step 4. Duplicate line items
+Duplicate your line items according to your [price granularity](/prebid-mobile/adops-price-granularity.html) setting.
diff --git a/prebid-mobile/adops-setup-rewarded-video-mopub.md b/prebid-mobile/adops-setup-rewarded-video-mopub.md
new file mode 100644
index 0000000000..839a8593e7
--- /dev/null
+++ b/prebid-mobile/adops-setup-rewarded-video-mopub.md
@@ -0,0 +1,55 @@
+---
+layout: page_v2
+title: Setup Rewarded Video for MoPub
+description: Setup Rewarded Video for MoPub
+pid: 1
+top_nav_section: prebid-mobile
+nav_section: prebid-mobile-adops
+sidebarType: 3
+---
+
+# Step-by-Step Line Item Setup for Rewarded Video on MoPub
+
+* TOC
+{:toc }
+
+This page provides step-by-step instructions to set up rewarded-video line items on MoPub to be used with the Prebid Mobile SDK.
+
+## Step 1. Add a line item
+
+ In the *Add a Line Item* section:
+ 1. For the *Type and Priority* settings, select *Non-Guaranteed* as the type and set the priority to *12*. This ensures the line item will compete with all other demand.
+ 2. Set the Rate to the price you want to target.
+
+ 3. In the *Advanced Targeting* section, set the target for *Keywords* to `hb_pb:0.50`
+
+
+For each level of pricing granularity required, one line item/creative pairing will need to be set up.
+
+Line items must be set up to target custom keywords that include bid price information. The bid price keywords will contain how much the buyer bid on the impression.
+
+Prebid Mobile, by default, will send the highest bid price to MoPub using the keyword `hb_pb` but will also submit the key `hb_pb_BIDDERCODE` for each bidder. You can decide to create one set of line items for all bidders or one set of line items for each bidder.
+
+## Step 2. Add creatives to your line item
+Rewarded video creatives must have a *VAST tag* with the *Format* set to *Rewarded Video* that includes the code below:
+
+```
++
+The `hb_uuid` variable value is the cache id that will load the ad markup from the bid stored in Prebid Cache. Within each line item, for each ad unit size, there should be one creative with this content.
+
+The XML can be constructed by providing the VAST tag URL as:
+`https://%%KEYWORD:hb_cache_host%%%%KEYWORD:hb_cache_path%%?uuid=%%KEYWORD:hb_uuid%%`
+
+## Step 3. Duplicate line items
+Duplicate your line items according to your [price granularity](/prebid-mobile/adops-price-granularity.html) setting.
diff --git a/prebid-mobile/dr-prebid.md b/prebid-mobile/dr-prebid.md
index d672e5b846..799f8dab86 100644
--- a/prebid-mobile/dr-prebid.md
+++ b/prebid-mobile/dr-prebid.md
@@ -55,6 +55,8 @@ The type of ad you want to test. This will be the ad type that is associated wit
Select from:
- *Banner*
- *Interstitial*
+- *Native*
+- *Video*
**Ad Size**
@@ -94,6 +96,10 @@ Select your Prebid Server host:
- *AppNexus*
- *Rubicon*
+- *Custom*
+
+**Custom Server Host**
+Provide the url of the custom hosted prebid server
**Account ID**
diff --git a/prebid-mobile/pbm-api/android/pbm-adunit-android.md b/prebid-mobile/pbm-api/android/pbm-adunit-android.md
index 5a2acdc87d..5bdddecf88 100755
--- a/prebid-mobile/pbm-api/android/pbm-adunit-android.md
+++ b/prebid-mobile/pbm-api/android/pbm-adunit-android.md
@@ -47,12 +47,62 @@ PB Ad Slot is an identifier tied to the placement the ad will be delivered in. T
Trigger a call to Prebid Server to retrieve demand for this Prebid Mobile ad unit.
+#### Mopub or GAM
+
+By default, Prebid SDK uses inflection to determine the publisher ad server, one of Mopub or Google Ad Manager (GAM), to convert Prebid's targeting keys (PBS bid keys, host and cache key) to trigger targeted line items. To render ads in ad servers other than Mopub or GAM, follow the instructions in the 3rd party ad server below.
+
+
**Parameters**
- `adObj`: This is the ad server request object (for [Google Ad Manager](https://developers.google.com/android/reference/com/google/android/gms/ads/doubleclick/PublisherAdRequest) and for [Mopub](https://developers.mopub.com/publishers/reference/android/MoPubView/)). If you do not wish to add any additional /custom key values to the ad server after the Prebid auction, pass `adObj` to the fetchDemand function, where Prebid SDK will set all the Prebid targeting keys as well as any keys added prior to auction
- As of Prebid SDK 1.7, a publisher can optionally pass the Google Ad Manager `builder` object of the [Google Ad Manager Mobile Ads SDK](https://developers.google.com/android/reference/com/google/android/gms/ads/doubleclick/PublisherAdRequest.Builder) to pass custom keys to Google Ad Manager after the Prebid Auction
- `onCompleteListener`: listener object
+#### 3rd Party Ad Server
+
+The default ad servers for Prebid's Mobile SDK are MoPub and GAM. The SDK can be expanded to include support for 3rd party ad servers through the fetchDemand function. This function returns the Prebid Server bidder key/values (targeting keys), which can then be passed to the ad server of choice.
+
+In this mode, the publisher will be responsible for the following actions:
+* Call fetchDemand with extended targetingDict callback
+* Retrieve targeting keys from extended fetchDemand function
+* Convert targeting keys into the format for your ad server
+* Pass converted keys to your ad server
+* Render ad with Prebid Universal Creative or custom renderer
+
+
+**Function Callbacks**
+
+* `ResultCode`: enum [result codes](https://docs.prebid.org/prebid-mobile/pbm-api/android/pbm-api-result-codes-android.html)
+* `unmodifiableMap`: [Prebid Server Response targeting keys](https://docs.prebid.org/prebid-server/endpoints/openrtb2/pbs-endpoint-auction.html#targeting)
+
+
+```
+func fetchDemand(completion: @escaping(_ result: ResultCode, _ kvResultDict: [String : String]?) -> Void)
+```
+
+{: .alert.alert-warning :}
+unmodifiableMap is an immutable object. Attempting to modify at runtime will throw an UnsupportedOperationException error. This is to prevent accidental changes to the Prebid targeting keys. If there is a desire to update, create or remove a key, making a copy of unmodifiableMap is recommended before passing to the ad server.
+
+
+Example:
+
+```java
+func loadMPRewardedVideo() {
+private void loadMPRewardedVideo() {
+
+ adUnit.fetchDemand(new OnCompleteListener2() {
+ @Override
+ public void onComplete(ResultCode resultCode, Map
| |
| Stored Responses | Stored Responses | Accepts a stored response ID in the OpenRTB, looks it up against a local data store, and merges with the OpenRTB response record. | | |
| First Party Data | Core | Accepts core first party data attributes and supports ext.prebid.data.bidders. | | |
-| First Party Data | Bidder-specific data | Accepts bidder-specific first party data attributes. | | |
-| First Party Data | AMP first party data | Accepts first party data attributes on an AMP request. | | |
+| First Party Data | Bidder-specific data | Accepts bidder-specific first party data attributes. | | |
+| First Party Data | AMP first party data | Accepts first party data attributes on an AMP request. | | |
| [Supply Chain](/prebid-server/endpoints/openrtb2/pbs-endpoint-auction.html#supply-chain-support) | Bidder-specific schains | Accepts bidder-specific schain | | |
| Publisher Accounts | Core | Ability to enforce that requests coming in have a valid account ID. | | |
| Publisher Accounts | AMP account parameter | Accept the account parameter on the AMP request. | | |
@@ -61,3 +61,4 @@ title: Prebid Server | Features
| Operations | Circuit breaker | Protects system performance during fault scenarios by detecting problems with external and internal endpoints, turning them off temporarily when a problem occurs. | | |
| Operations | [Server default request](/prebid-server/features/pbs-default-request.html) | Support global defaults for incoming requests. | | |
| Operations | IPv6 | Support taking IPv6 addresses and forwarding them to bidders. | | |
+| Operations | [Request Logging Admin Endpoints](/troubleshooting/pbs-troubleshooting.html#request-logging) | Log a limited number of requests to understand the raw data clients are sending. | | |
diff --git a/prebid-server/features/pbs-fpd.md b/prebid-server/features/pbs-fpd.md
new file mode 100644
index 0000000000..a488c46dac
--- /dev/null
+++ b/prebid-server/features/pbs-fpd.md
@@ -0,0 +1,130 @@
+---
+layout: page_v2
+sidebarType: 5
+title: First Party Data - Prebid Server
+---
+
+# First Party Data - Prebid Server
+{: .no_toc}
+
+* TOC
+{:toc}
+
+Prebid allows publishers to supply attributes related to their content
+and users, and to apply permissions so only certain bidders are allowed
+to access those attributes.
+
+{: .alert.alert-warning :}
+For now, this feature is only supported in PBS-Java and these conventions aren't implemented by all adapters. Please
+check with each of your bidders to make sure they're reading first
+party data from the standard Prebid locations.
+
+## How It Works
+
+Each of the three main sources of Prebid Server traffic will place
+First Party Data in the OpenRTB JSON in several places:
+
+{: .table .table-bordered .table-striped }
+| OpenRTB Attribute | Description | PBJS Source | SDK Source | AMP Source |
+| --- | --- | --- | --- | --- |
+| site.ATTR | Only standard OpenRTB attributes should be here: name, domain, cat, sectioncat, pagecat, page, ref, search, keywords. | config.fpd.context.ATTR | n/a | site.ATTR |
+| site.ext.data.ATTR | Any other site-related attributes should go here. | config.fpd.context.data | n/a | site.ext.data.ATTR |
+| app.ext.data.ATTR | Any app-related attributes should go here. | n/a | Targeting addContextData() | n/a |
+| user.ATTR | Only standard OpenRTB attributes should be here: yob, gender, keywords. | config.fpd.user.ATTR | n/a | user.ATTR |
+| user.ext.data.ATTR | Any other user-related attributes should go here. | config.fpd.user.data.ATTR | Targeting addUserData() | user.ext.data.ATTR |
+| imp[].ext.context.data.ATTR | AdUnit-specific attributes should go here. | AdUnit.fpd.context | AdUnit addContextData() | n/a |
+| ext.prebid.data.bidders[] | If specified, only these bidders are allowed to see fields in {site/app/user}.ext.data. | n/a | addBidderToAccessControlList() | bidders |
+| ext.prebid.bidderconfig | Bidder-specific config | [setBidderConfig()](/dev-docs/publisher-api-reference.html#module_pbjs.setBidderConfig) | n/a | n/a |
+
+This diagram summarizes how first party data flows into the OpenRTB JSON:
+
+{: .pb-lg-img :}
+
+{: .alert.alert-info :}
+Note that Prebid.js supports the [`setBidderConfig`](/dev-docs/publisher-api-reference.html#module_pbjs.setBidderConfig) method of defining
+bidder-specific first party data, while SDK and AMP only support the `ext.prebid.data.bidders[]` approach.
+
+## OpenRTB Examples
+
+In this example, only BidderA has access to the global first party data:
+```
+{
+ ext: {
+ prebid: {
+ data: { bidders: [ "bidderA" ] } // limit bidders that receive global data
+ }
+ },
+ site: {
+ keywords: "",
+ search: "",
+ ext: {
+ data: {
+ // only seen by bidderA as named in ext.prebid.data.bidders[]
+ GLOBAL CONTEXT DATA
+ }
+ }
+ },
+ user: {
+ keywords: "",
+ gender: "",
+ yob: 1999,
+ geo: {},
+ ext: {
+ data: {
+ // only seen by bidderA as named in ext.prebid.data.bidders[]
+ GLOBAL USER DATA
+ }
+ }
+ },
+ imp: [
+ ...
+ ext: {
+ context: {
+ keywords: "",
+ search: "",
+ data: {
+ // everyone sees this data
+ ADUNIT SPECIFIC CONTEXT DATA
+ }
+ }
+ }
+ ]
+}
+```
+
+This example shows an array of bidder-specific config:
+```
+{
+ ext: {
+ prebid: {
+ bidderconfig: [ {
+ bidders: [ 'bidderA', 'bidderB' ],
+ config: {
+ fpd: { site: { ... }, user: { ...} }
+ }
+ },{
+ bidders: [ 'bidderC' ],
+ config: {
+ fpd: { site: { ... }, user: { ...} }
+ }
+ }]
+ }
+ }
+}
+```
+
+## How Server-Side Bid Adapters Read First Party Data
+
+Bid adapters don't need to worry about whether the request came from
+Prebid.js, the SDK, or AMP -- everything is merged into the OpenRTB JSON. If a bid adapter receives first party data on any of the fields noted in
+the table above, they can simply pass that data to their endpoint in
+the expected way.
+
+In other words, just be aware of site.ext.data.ATTR, app.ext.data.ATTR, user.ext.data.ATTR,
+and imp[].ext.context.data.ATTR and either pass them straight through or map
+attributes to where your endpoints expect them.
+
+## Further Reading
+
+- [Prebid.js First Party Data](/features/firstPartyData.html)
+- [Prebid Server and AMP](/prebid-server/use-cases/pbs-amp.html)
diff --git a/prebid-server/overview/prebid-server-overview.md b/prebid-server/overview/prebid-server-overview.md
index 388cf8b059..89f1fe8603 100644
--- a/prebid-server/overview/prebid-server-overview.md
+++ b/prebid-server/overview/prebid-server-overview.md
@@ -12,7 +12,7 @@ Prebid Server is an open-source solution for server-to-server header bidding. It
{:class="pb-xlg-img"}
-Prebid Server is an intelligent proxy server with a growing list of features. At a high level, it works like this:
+Prebid Server is a header bidding server with a growing list of features. At a high level, it works like this:
1. Prebid Server completes and validates incoming requests
- Resolves dynamic stored requests
@@ -60,4 +60,4 @@ If you're a demand source, we also have information about [creating your own ser
If you need help with Prebid Server, the best ways to communicate with us are:
- [Post an issue](https://github.com/prebid/prebid-server/issues) in the prebid-server GitHub repo.
-- [Join prebid.org](/partners/partners.html) and get access to our Slack workspace.
+- [Join prebid.org](https://prebid.org/membership/) and get access to our Slack workspace.
diff --git a/prebid-server/use-cases/pbs-amp.md b/prebid-server/use-cases/pbs-amp.md
index 98ae98d184..cfa2db3d5d 100644
--- a/prebid-server/use-cases/pbs-amp.md
+++ b/prebid-server/use-cases/pbs-amp.md
@@ -6,6 +6,10 @@ title: Prebid Server | Use Cases | AMP
---
# Use Case: Prebid Server | AMP
+{: .no_toc}
+
+* TOC
+{:toc}
[Accelerated Mobile Pages (AMP)](https://ampproject.org/) is an alternate web technology that can speed page performance, but
as part of the tradeoff, header bidding wrappers like Prebid.js don't work well. Instead, AMP supports a method of header bidding called Real Time Configuration(RTC), which is implemented by Prebid Server.
@@ -43,11 +47,12 @@ There are two basic ways of invoking AMP RTC:
data-slot="/11111/amp_test"
data-multi-size-validation="false"
rtc-config='{"vendors": {"prebidrubicon": {"REQUEST_ID": "14062-amp-AMP_Test-300x250"}, "ACCOUNT_ID": "1001"}}'
- json='{ "targeting": {"site": {"tags": "autoestima","url": "/amp/familia/materias/33559-princesa-africana-da-disney-lembra-por-que-toda-crianca-precisa-se-sentir-representada"}}}' >
+ json='{ "targeting": {"site":{"keywords":"article, las vegas","cat":{"blah":"1"},"other-attribute":"other-value","ext":{"data":{"entry_group":["front-page","featured-stories"],"page_type":"AMP"}}},"user":{"gender":"m"},"bidders":["bidderA","bidderB"],"keywords":"las vegas hospitality employees","foo":{"bar":"baz"}}' >
```
-**Note:** the `prebidrubicon` and `prebidappnexus` AMP vendors define different parameters. AppNexus uses "PLACEMENT_ID" as the argument to rtc-config while Rubicon uses "REQUEST_ID".
+{: .alert.alert-info :}
+**Note:** the `prebidrubicon` and `prebidappnexus` AMP vendor strings define slightly different parameters; AppNexus uses "PLACEMENT_ID" as the argument to rtc-config while Rubicon uses "REQUEST_ID". They both translate to `tag_id` when passed to Prebid Server.
- The other option is to construct a direct URL from component pieces: w, h, slot, targeting, gdpr_consent, account, page url (purl), etc.
@@ -60,6 +65,9 @@ There are two basic ways of invoking AMP RTC:
```
+{: .alert.alert-info :}
+First party data may be passed in on the "targeting" field. See the [`/openrtb2/amp` endpoint](/prebid-server/endpoints/openrtb2/pbs-endpoint-amp.html) documentation for more details.
+
### Prebid Server Receives the AMP Request
Prebid Server's first job on the [/openrtb2/amp endpoint](/prebid-server/endpoints/openrtb2/pbs-endpoint-amp.html) is to create an OpenRTB block to pass to the adapters.
@@ -158,6 +166,11 @@ So for the /openrtb2/amp URL above, the resulting OpenRTB might be:
Note that most of the above OpenRTB was prepared offline and stored in the Prebid Server database indexed by the `tag_id`.
Only a few dynamic parameters on the query string are integrated into the results from the database.
+#### First Party Data Support
+
+Any targeting data passed in through the [`/openrtb2/amp`](/prebid-server/endpoints/openrtb2/pbs-endpoint-amp.html) endpoint is merged
+into the OpenRTB JSON and permissions, if defined, are applied to each bidder.
+
#### Auction and Response
From here, the header bidding auction is mostly the same as it is for Prebid.js:
diff --git a/prebid-server/use-cases/pbs-lfv.md b/prebid-server/use-cases/pbs-lfv.md
index 164dd35ed8..f61c5e085e 100644
--- a/prebid-server/use-cases/pbs-lfv.md
+++ b/prebid-server/use-cases/pbs-lfv.md
@@ -6,6 +6,10 @@ title: Prebid Server | Use Cases | Long Form Video
---
# Use Case: Prebid Server | Long Form Video
+{: .no_toc}
+
+* TOC
+{:toc}
Prebid Server (PBS) supports filling _pods_ of multiple video advertisements, including support for competitve separation.
diff --git a/prebid-server/use-cases/pbs-pbjs.md b/prebid-server/use-cases/pbs-pbjs.md
index da9b6a888c..414d745f3c 100644
--- a/prebid-server/use-cases/pbs-pbjs.md
+++ b/prebid-server/use-cases/pbs-pbjs.md
@@ -6,6 +6,10 @@ title: Prebid Server | Use Cases | Prebid.js
---
# Use Case: Prebid Server | Prebid.js
+{: .no_toc}
+
+* TOC
+{:toc}
When publishers specify bidders in [Prebid.js `s2sConfig`](/dev-docs/publisher-api-reference.html#setConfig-Server-to-Server), the browser connects to Prebid Server to coordinate the header bidding auction for those bidders.
diff --git a/prebid-server/use-cases/pbs-sdk.md b/prebid-server/use-cases/pbs-sdk.md
index 37daa28bdb..f1500f8b2e 100644
--- a/prebid-server/use-cases/pbs-sdk.md
+++ b/prebid-server/use-cases/pbs-sdk.md
@@ -6,6 +6,10 @@ title: Prebid Server | Use Cases | Mobile SDK
---
# Use Case: Prebid Server | Prebid Mobile SDK
+{: .no_toc}
+
+* TOC
+{:toc}
Unlike Prebid.js, the [Prebid Mobile SDK](/prebid-mobile/prebid-mobile.html) doesn't make requests to demand sources directly. Instead, it relies entirely on Prebid Server to handle the bidder communication.
diff --git a/prebid/prebidjsReleases.md b/prebid/prebidjsReleases.md
index 9ec879476c..068e50e609 100644
--- a/prebid/prebidjsReleases.md
+++ b/prebid/prebidjsReleases.md
@@ -16,6 +16,15 @@ The table below is a summary of feature changes and important bug fixes in core
{: .table .table-bordered .table-striped }
| Release | Feature |
| --- | --- |
+| 4.8 | GDPR updates around modules and storage manager. |
+| 4.6 | Removed cmpuishown event for TCF2 logic |
+| 4.5 | Price Floors: Add bid object into cpmAdjustment function |
+| 4.4 | DFP Video Module supports VAST 4 |
+| 4.3 | DFP Video Module bug fixed |
+| 4.1.1 | Release of the [GPT Pre-Auction Module](https://docs.prebid.org/dev-docs/modules/gpt-pre-auction.html). Price Floors: new signals (location: noData + floorProvider) |
+| 4.0 | TCF Purpose 1 and Purpose 2 enforced by default when GDPR enforcement module turned on. Removed Digitrust userId module. Removed audienceNetworkBidAdapter. |
+| 3.27.1 | DFP Video Module bug fixed |
+| 3.27 | An important bug in the DFP Video Module was introduced with this release and fixed in 4.3 and 3.27.1. The dfpVideoModule only looked in adunit.sizes but adunit.sizes was stripped. Unfortunately there's not a workaround - if you use that video module, you shouldn't use Prebid.js 3.27 through 4.2 inclusive. |
| 3.24 | PBS Bid Adapter allows setting site params |
| 3.23 | If a server-side bid contains imp.ext.prebid.event.win, pbsBidAdapter listens to BidsWon events and hits the URL. |
| 3.22 | Secure creatives use event.origin rather than a hard coded adServerDomain |
diff --git a/troubleshooting/pbs-troubleshooting.md b/troubleshooting/pbs-troubleshooting.md
index 0a1abab007..4175cd2f47 100644
--- a/troubleshooting/pbs-troubleshooting.md
+++ b/troubleshooting/pbs-troubleshooting.md
@@ -121,6 +121,22 @@ Could result in this response, assuming that the IDs exist in the database table
}
{% endhighlight %}
+## Request Logging
+
+(PBS-Java only)
+
+Sometimes you want to see what's coming into the server before being processed by PBS.
+If the admin endpoints are enabled and you have the admin endpoint password, you can
+hit these two URLs with the desired parameter values:
+
+- https://HOST/logging/[changelevel](/prebid-server/endpoints/pbs-endpoint-admin.html#loggingchangelevel)?level=debug&duration=10000
+- https://HOST/logging/[httpinteraction](/prebid-server/endpoints/pbs-endpoint-admin.html#logginghttpinteraction)?limit=100&endpoint=auction&account=1111
+
+Then you can check server logs for output like:
+```
+http-interaction : Requested URL: "/openrtb2/auction?debug=1", request body: "{ ... }"
+```
+
## Related Topics
{:.no_toc}
diff --git a/wrapper_code_of_conduct.md b/wrapper_code_of_conduct.md
index 81c4bf654a..608521d72b 100644
--- a/wrapper_code_of_conduct.md
+++ b/wrapper_code_of_conduct.md
@@ -57,3 +57,4 @@ This Wrapper Code of Conduct establishes the principles by which we believe head
+ [Project Principles]({{site.baseurl}}/principles.html)
+ [Getting Started]({{site.baseurl}}/overview/getting-started.html)
++ [Prebid.org Community Code of Conduct](https://prebid.org/code-of-conduct/)