pull latest master

_data/sidebar.yml

@@ -1795,7 +1795,7 @@
 
 - sbSecId: 5
   title: Privacy Support (GDPR, CCPA, etc)
-  link: /prebid-server/features/privacy/pbs-privacy.html
+  link: /prebid-server/features/pbs-privacy.html
   isHeader: 0
   isSectionHeader: 0
   sectionTitle:

dev-docs/modules/userId.md

@@ -426,9 +426,7 @@ The adapters can be implemented to use the lipibid as the identifier and segment
 
 #### LiveIntent ID Registration
 
-You are not required to register with LiveIntent to start using the LiveIntent ID sub-module. However, we do recommend reaching out to us at [peoplebased@liveintent.com](mailto:peoplebased@liveintent.com) so that we can guide you through the optimal setup and the ways you can benefit from LiveIntent identity solutions:
-1. Providing buyers a stable identifier, which can solve cross-browser and cross-channel frequency capping challenges.
-2. Leveraging your first-party audiences to increase the value of your inventory.
+Please register with us if you’re not a LiveIntent customer already: https://www.liveintent.com/prebid-registration/
 
 When adding LiveIntent’s ID to your Prebid.js package, you disclose or make available Personal Information to LiveIntent.  This information made available to LiveIntent is used to (i) connect with and reference data that already exists in LiveIntent’s graph (the “LiveIntent Graph”), and (ii) authenticate and validate data in aggregate to improve the performance of the services LiveIntent provides. By activating LiveIntent’s module, you hereby confirm that with regard to all individuals to whom Personal Information relates, you have, at or before the point of collecting Personal Information or making Personal Information available to LiveIntent, provided any legally required notices, obtained any legally required consents, and provided individuals with an opportunity to opt-out of the sharing of Personal Information, if such an opt-out is required under applicable laws, such that LiveIntent can provide service to you as described here and in LiveIntent’s privacy policies for the services which can be found at [https://www.liveintent.com/services-privacy-policy/](https://www.liveintent.com/services-privacy-policy/) 
 

dev-docs/show-outstream-video-ads.md

@@ -67,17 +67,16 @@ To display an outstream video, two things are needed:
 
 Prebid.js will select the `renderer` used to display the outstream video in the following way:
 
-1. If a `renderer` is associated with the Prebid adUnit, it will be used to display any outstream demand associated with that adUnit.  Below, we will provide an example of an adUnit with an associated `renderer`. If that renderer is specified as backup only, it will only be used when no other renderer is found. 
+1. If a `renderer` is associated with the Prebid adUnit, it will be used to display any outstream demand associated with that adUnit.  Below, we will provide an example of an adUnit with an associated `renderer`.
 2. If no `renderer` is specified on the Prebid adUnit, Prebid will invoke the renderer associated with the winning (or selected) demand partner video bid.
 
 {: .alert.alert-warning :}
-At this time, since not all demand partners return a renderer with their video bid responses, we recommend that publishers associate a `renderer` with their Prebid video adUnits, if possible.  By doing so, any Prebid adapter that supports video will be able to provide demand for a given outstream slot. Choosing a backup only renderer allows publishers to access demand with or without an attached renderer. 
+At this time, since not all demand partners return a renderer with their video bid responses, we recommend that publishers associate a `renderer` with their Prebid video adUnits, if possible.  By doing so, any Prebid adapter that supports video will be able to provide demand for a given outstream slot.
 
-Renderers are associated with adUnits through the `adUnit.renderer` object.  This object contains three fields:
+Renderers are associated with adUnits through the `adUnit.renderer` object.  This object contains two fields:
 
 1. `url` -- Points to a file containing the renderer script.
 2. `render` -- A function that tells Prebid.js how to invoke the renderer script.
-3. `backupOnly` -- Optional field, if set to 'true', buyer or adapter renderer will be preferred
 
 {% highlight js %}
 
@@ -91,26 +90,14 @@ pbjs.addAdUnit({
     },
     renderer: {
         url: 'https://acdn.adnxs.com/video/outstream/ANOutstreamVideo.js',
-        backupOnly: 'true', // prefer demand renderer
         render: function (bid) {
-            adResponse = {
-                ad: {
-                    video: {
-                        content: bid.vastXml,
-                        player_height: bid.playerHeight,
-                        player_width: bid.playerWidth
-                    }
-                }
-            }
-            // push to render queue because ANOutstreamVideo may not be loaded yet.
-            bid.renderer.push(() => {
-                ANOutstreamVideo.renderAd({
-                    targetId: bid.adUnitCode, // target div id to render video.
-                    adResponse: adResponse
-                });
+            ANOutstreamVideo.renderAd({
+                targetId: bid.adUnitCode,
+                adResponse: bid.adResponse,
             });
         }
-    }
+    },
+    ...
 });
 
 {% endhighlight %}

faq/prebid-server-faq.md

@@ -101,4 +101,4 @@ the hosting company in some scenarios, but it's technically unavoidable and bett
 
 ## How does Prebid Server support privay signals?
 
-See the [Prebid Server Privacy Feature Page](/prebid-server/features/privacy/pbs-privacy.html)
+See the [Prebid Server Privacy Feature Page](/prebid-server/features/pbs-privacy.html)

prebid-server/features/pbs-feature-idx.md

@@ -18,15 +18,15 @@ title: Prebid Server | Features
 | Targeting | Format | Request can specify `includeformat`, which causes PBS to emit hb_format along with other targeting values like hb_pb, etc. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | |
 | [Price Granularity](/prebid-server/endpoints/openrtb2/pbs-endpoint-auction.html#targeting) | Core | Request can define quantization rules. Bids are quantized before being added to ad server targeting. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | Price Granularity | Mediatype pricegranularity | Request can define different quantization rules for different mediatypes. Bids are quantized before being added to ad server targeting. | | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
-| [GDPR](/prebid-server/features/privacy/pbs-privacy.html) | TCF 1.1 core | Able to: read the TCF1.1 global vendor list, parse incoming TCF1.1 consent strings, and [take appropriate enforcement action](https://docs.google.com/document/d/1g0zAYc_EfqyilKD8N2qQ47uz0hdahY-t8vfb-vxZL5w/edit). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
+| [GDPR](/prebid-server/features/pbs-privacy.html) | TCF 1.1 core | Able to: read the TCF1.1 global vendor list, parse incoming TCF1.1 consent strings, and [take appropriate enforcement action](https://docs.google.com/document/d/1g0zAYc_EfqyilKD8N2qQ47uz0hdahY-t8vfb-vxZL5w/edit). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 1.1 Account Config | Able to turn on and off TCF1 enforcement per account. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 1.1 Geo-lookup | Can use a geographic lookup service to help determine whether the incoming request is in-scope for GDPR. | | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 1.1 GVL Fallback | Allow the host company to optionally add a default TCF1 GVL file. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 2 core | Able to: read the TCF2 global vendor list, parse incoming TCF2 consent strings, and [take appropriate enforcement action](https://docs.google.com/document/d/1fBRaodKifv1pYsWY3ia-9K96VHUjd8kKvxZlOsozm8E/edit). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 2 Account Config | Able to turn on and off TCF2 enforcement per account. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 2 Geo-lookup | Can use a geographic lookup service to help determine whether the incoming request is in-scope for GDPR. | | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | GDPR | TCF 2 Integration type exception | Can be configured to turn off GDPR checks for a specific account and a specific integration type. e.g. Account 123 has a different legal basis for AMP. | | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
-| [US Privacy](/prebid-server/features/privacy/pbs-privacy.html) | USP core | Able to: read the US Privacy consent string (CCPA) and [take appropriate enforcement action](https://github.com/prebid/prebid-server/issues/1129). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
+| [US Privacy](/prebid-server/features/pbs-privacy.html) | USP core | Able to: read the US Privacy consent string (CCPA) and [take appropriate enforcement action](https://github.com/prebid/prebid-server/issues/1129). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | US Privacy | USP AMP support | Able to: read the US Privacy consent string from AMP requests and [take appropriate enforcement action](https://github.com/prebid/prebid-server/issues/1176). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | COPPA | Core | Able to read the COPPA flag and [take appropriate enforcement action](https://github.com/prebid/prebid-server/issues/929). | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |
 | [Cache](/prebid-server/features/pbs-caching.html) | Bids core | Accepts the ext.prebid.cache.bids parameter, storing bid objects in PBC. | <img src="/assets/images/icons/icon-check-green.png" width="30"> | <img src="/assets/images/icons/icon-check-green.png" width="30"> |

prebid-server/features/privacy/pbs-privacy.md → prebid-server/features/pbs-privacy.md

@@ -66,8 +66,8 @@ More details are available in the [Prebid Support for TCF2](https://docs.google.
 There are a number of configuration settings that PBS Host Companies need
 to consider:
 
-- Host company GVL ID
-- Default expiration time of the uids cookie set in the host company domain
+- Host company GVL ID. Currently PBS requires the host company to have a GVL-ID or the setting of the `uids` cookie in GDPR scope will fail.
+- The default expiration time of the uids cookie set in the host company domain should be defined to match what's in the TCF 2.1 `maxCookieAgeSeconds` GVL field.
 - GDPR enforcement flags for each Purpose and Vendor
 
 The specific details vary slightly between PBS-Go and PBS-Java, so check the