Update ix.md (#4955)

* Update ix.md Added the version number that supports the Protected Audience API and added a new step 1 to include the opt-in requirement * Update ix.md Added a few more examples for protected audience configuration * Update ix.md added support for fledgeForGpt to the features table at the top of the page * Update ix.md fixed lint errors * Remove fledge support --------- Co-authored-by: Muki Seiler <[email protected]>
prebid · Nov 7, 2023 · 0f8add7 · 0f8add7
1 parent bd6b821
commit 0f8add7
Showing 1 changed file with 22 additions and 3 deletions.
diff --git a/dev-docs/bidders/ix.md b/dev-docs/bidders/ix.md
@@ -392,11 +392,16 @@ pbjs.addAdUnits({
 
 ## Protected Audience API support
 
-**Before you begin:** You must have Google Ad Manager and the [fledgeForGpt](/dev-docs/modules/fledgeForGpt.html) module.
+**Before you begin:**
+
+* You must have Google Ad Manager and the [fledgeForGpt](/dev-docs/modules/fledgeForGpt.html) module.
+* You must be using Prebid.js version 8.18.0 or later.
 
 Follow these steps to configure your Prebid.js to specify that your ad slots are enabled for [Protected Audience](https:/WICG/turtledove/blob/main/FLEDGE.md) auctions:
-1. Build the `fledgeForGpt` module in your Prebid.js configuration by adding `fledgeForGpt` to the list of modules that you are already using. For more information about the module, see Prebid's [Fledge (Protected Audience) for GPT Module](/dev-docs/modules/fledgeForGpt.html) documentation.
-2. Enable all ad units to use the `fledgeForGpt` module in your prebid.js configuration. Index recommends that you do this in the global level configuration by using the `defaultForSlots` parameter with a value of `1`. <br />
+
+1. Confirm that you have opted in to use the Protected Audience API in your Google Ad Manager configuration. For more information about how to opt-in, see Google's documentation on [Protected Audience API and Ad Manager after Chrome GA](https://support.google.com/admanager/answer/13627134?hl=en&ref_topic=12264880&sjid=10591375417866092080-NA).
+2. Build the `fledgeForGpt` module in your Prebid.js configuration by adding `fledgeForGpt` to the list of modules that you are already using. For more information about the module, see Prebid's [Fledge (Protected Audience) for GPT Module](/dev-docs/modules/fledgeForGpt.html) documentation.
+3. Enable all ad units to use the `fledgeForGpt` module in your prebid.js configuration. You can do this in the global-level configuration, bidder level, or ad-unit level. For more information about the configurations, see Prebid's [Fledge (Protected Audience) for GPT Module](/dev-docs/modules/fledgeForGpt.html) documentation. Index recommends that you do this in the global-level configuration by using the `defaultForSlots` parameter with a value of `1`. <br />
 **Note:** If you are using the `fledgeForGpt.bidders[]`, make sure that you add `ix` to the list of bidders.<br />
 The following shows an example of the configuration done at the global level:
 
@@ -411,6 +416,20 @@ pbjs.que.push(function() {
 });
 ```
 
+The following shows an example of the configuration done at the ad-unit level:
+
+```javascript
+pbjs.addAdUnits({
+ code: "my-adunit-div",
+ // other config here
+ ortb2Imp: {
+ ext: {
+ ae: 1
+ }
+ }
+});
+```
+
 <a name="bid-request-parameters"></a>
 
 ## Bid request parameters