<aside> 📌 Update your wrapper configuration based on the modules you built previously.

</aside>

Steps to undertake:

⬅️ Previous setup step:

➡️ Next setup step:

A. About the Adagio parameters and configuration


<aside> ⚠️ Our platform is tag-based so there is no need to create any tag ID, zone ID, format ID, placement ID or anything else but the line items.

</aside>

<aside> 👉 You can zoom in each parameters by opening the associated page to get additional informations like example or screenshots.

</aside>

Adagio integration - Parameters explanation

B. Add the necessary Adagio bidder parameters, ortb2Imp and ortb2 params


<aside> 💡 Adagio requires four parameters: organizationId, site, placement and adUnitElementId / divId.

C. Configure the Adagio RTD Provider parameters (since Prebid 9)


<aside> 💡 Since Prebid 9 only: Once built, the Adagio RTD Provider should be configured with the following parameters: organizationId and site (click on links to get more info about parameters)

</aside>

pbjs.que.push(function () {
  pbjs.setConfig({
    realTimeData: {
      dataProviders: [
        {
          name: "adagio",
          params: {
            [organizationId](<https://adagioio.notion.site/organizationId-ec099c6af321493e81fa1233af950bde>): "1000", // Required
            [site](<https://adagioio.notion.site/site-7c536773e44d4ab2a3a0a2d3b97090fe>): "my-site",        // Required
          },
        },
      ],
    },
  });
});

D. Device access and iframe sync


<aside> ⚠️ Enable device access and iframe sync. These options are mostly related to privacy (GDPR, CCPA, COPPA or other privacy scenarios).

</aside>

pbjs.setConfig({ 
  deviceAccess: true,
  userSync: {
    filterSettings: {
      iframe: {
        bidders: ['adagio'], // Required
        filter: 'include'    // Required
      }
    }
  }
});

E. Add the local storage for Adagio (**b**efore **Prebid 9**)