Back to Bidders

Unruly

Features

Bid Params

Protected Audience API (FLEDGE) support

There’s an option to receive demand for Protected Audience API (FLEDGE/PAAPI) ads using Unruly’s (Nexxen) bid adapter. Prebid’s fledgeForGpt module and Google Ad Manager is currently required.

The following steps should be taken to setup Protected Audience for Unruly(Nexxen):

1. Reach out to your account manager to coordinate set up:

2. Build and enable FLEDGE module as described in fledgeForGpt module documentation.

   Make sure to enable Unruly bidder to participate in FLEDGE. If there are any other bidders to be allowed for that, add them to the bidders array:

    pbjs.setBidderConfig({
      bidders: ["unruly"],
      config: {
        fledgeEnabled: true
      }
    });
   

First Party Data

Publishers should use the ortb2 method of setting First Party Data. The following fields are supported:

• ortb2.site.*

AdUnit-specific data is supported using AdUnit.ortb2Imp.ext.*

Example of first party data available only to the Unruly (Nexxen) bidder. Applies across all ad units. We support up to 5 custom keys.

pbjs.setBidderConfig({
  bidders: ["unruly"],
  config: {
    ortb2: {
      site: {
        ext: {
          data: {
            customkey1: "value1",
            customkey2: "value2",
            customkey3: "value3",
            customkey4: "value4",
            customkey5: "value5"
          }
        }
      }
    }
  }
});

"Send All Bids" Ad Server Keys

Back to Bidders