From 0dd5845f6fabc42399bac7be3887e6d1cc51001e Mon Sep 17 00:00:00 2001
From: Demetrio Girardi <dgirardi@prebid.org>
Date: Wed, 10 Dec 2025 10:01:22 -0800
Subject: [PATCH 1/3] JS: documentation for FPD keywords configuration options

---
 features/firstPartyData.md | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/features/firstPartyData.md b/features/firstPartyData.md
index e4eea093ee..2a6d9ed647 100644
--- a/features/firstPartyData.md
+++ b/features/firstPartyData.md
@@ -55,7 +55,7 @@ If not specified through any of the methods above, Prebid.js attempts to automat
 | `site.page` | Site URL, from `pageUrl` falling back to `location.href` | [`pageUrl` config](/dev-docs/publisher-api-reference/setConfig.html#setConfig-Page-URL) |
 | `site.ref` | `document.referrer` | |
 | `site.domain` | Domain portion of `site.page` | |
-| `site.keywords` | Contents of `<meta name="keywords">`, if such a tag is present on the page | |
+| `site.keywords` | Contents of `<meta name="keywords">` and `<script type="application/json+ld">`, if those tags are present on the page | [keywords config](#keywords) |
 | `site.publisher.domain` | Second level domain portion of `site.domain` | The second-level domain portion of `sub.example.publisher.com` is `publisher.com`|
 | `device.w` | Width of the screen in pixels |
 | `device.h` | Height of the screen in pixels |
@@ -70,18 +70,31 @@ If not specified through any of the methods above, Prebid.js attempts to automat
 | `regs.coppa` | COPPA Regulation flag | [COPPA config](/dev-docs/publisher-api-reference/setConfig.html#setConfig-coppa)
 | `regs.ext.gpc` | Global Privacy Control setting | [Navigator.globalPrivacyControl](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/globalPrivacyControl) |
 
-Publisher-provided first party data always takes precedence for all fields; you can also set `null` to disable them. For example, the following discards the automatically collected `device.keywords`:  
+Publisher-provided first party data always takes precedence for all fields; you can also set `null` to disable them. For example, the following discards the automatically collected `site.keywords`:  
 
 ```javascript
 pbjs.setConfig({
     ortb2: {
-        device: {
+        site: {
             keywords: null
         }
     }
 })
 ```
 
+<a id="config"></a>
+
+## Configuration
+
+{: .table .table-bordered .table-striped }
+| Param | Type | Description |
+| --- | --- | --- | --- |
+| `firstPartyData` |  Object | First party data automatic collection options |
+| `firstPartyData.uaHints`  |   Array of strings | High entropy user agent hints to collect for `device.sua` (see below) |
+| `firstPartyData.keywords` | Object | `site.kewyords` automatic collection options | 
+| `firstPartyData.keywords.meta` |  Boolean | If true (the default), collect keywords from `<meta name="keyword">` tags found on the page |
+| `firstPartyData.keywords.json` |  Boolean | If true (the default), collect keywords from `<script type="application/json+ld">` tags found on the page |
+
 <a id="uaHints"></a>
 
 #### User Agent client hints

From a170fc4f2ec2719a9b72a94b906b95ada5711f57 Mon Sep 17 00:00:00 2001
From: Demetrio Girardi <dgirardi@prebid.org>
Date: Wed, 10 Dec 2025 10:04:08 -0800
Subject: [PATCH 2/3] lint

---
 features/firstPartyData.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/features/firstPartyData.md b/features/firstPartyData.md
index 2a6d9ed647..b30bf3a2b3 100644
--- a/features/firstPartyData.md
+++ b/features/firstPartyData.md
@@ -55,7 +55,7 @@ If not specified through any of the methods above, Prebid.js attempts to automat
 | `site.page` | Site URL, from `pageUrl` falling back to `location.href` | [`pageUrl` config](/dev-docs/publisher-api-reference/setConfig.html#setConfig-Page-URL) |
 | `site.ref` | `document.referrer` | |
 | `site.domain` | Domain portion of `site.page` | |
-| `site.keywords` | Contents of `<meta name="keywords">` and `<script type="application/json+ld">`, if those tags are present on the page | [keywords config](#keywords) |
+| `site.keywords` | Contents of `<meta name="keywords">` and `<script type="application/json+ld">`, if those tags are present on the page | See [configuration options](#config) |
 | `site.publisher.domain` | Second level domain portion of `site.domain` | The second-level domain portion of `sub.example.publisher.com` is `publisher.com`|
 | `device.w` | Width of the screen in pixels |
 | `device.h` | Height of the screen in pixels |
@@ -97,7 +97,7 @@ pbjs.setConfig({
 
 <a id="uaHints"></a>
 
-#### User Agent client hints
+### User Agent client hints
 
 `device.sua` is populated with UA client hints retrieved from [`navigator.userAgentData`](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/userAgentData). You can specify the list of hints using the `uaHints` option with [any available high entropy hint](https://developer.mozilla.org/en-US/docs/Web/API/NavigatorUAData#returning_high_entropy_values):
 

From 062519ee796377405201a020bddeebb51243766d Mon Sep 17 00:00:00 2001
From: Demetrio Girardi <dgirardi@prebid.org>
Date: Wed, 17 Dec 2025 08:55:42 -0800
Subject: [PATCH 3/3] add note on FPD set by modules

---
 features/firstPartyData.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/features/firstPartyData.md b/features/firstPartyData.md
index b30bf3a2b3..0bd0694670 100644
--- a/features/firstPartyData.md
+++ b/features/firstPartyData.md
@@ -70,7 +70,7 @@ If not specified through any of the methods above, Prebid.js attempts to automat
 | `regs.coppa` | COPPA Regulation flag | [COPPA config](/dev-docs/publisher-api-reference/setConfig.html#setConfig-coppa)
 | `regs.ext.gpc` | Global Privacy Control setting | [Navigator.globalPrivacyControl](https://developer.mozilla.org/en-US/docs/Web/API/Navigator/globalPrivacyControl) |
 
-Publisher-provided first party data always takes precedence for all fields; you can also set `null` to disable them. For example, the following discards the automatically collected `site.keywords`:  
+Publisher-provided first party data generally takes precedence for all fields; you can also set `null` to disable them. For example, the following discards the automatically collected `site.keywords`:  
 
 ```javascript
 pbjs.setConfig({
@@ -82,6 +82,8 @@ pbjs.setConfig({
 })
 ```
 
+Note however that this typically not the case for fields populated by optional modules: `consentManagementTcf` will override `regs.gdpr` and `user.consent`, `geolocationRtdProvider` will override `device.geo`, and so on.    
+
 <a id="config"></a>
 
 ## Configuration