> For the complete documentation index, see [llms.txt](https://adagio-io.gitbook.io/adagio-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adagio-io.gitbook.io/adagio-documentation/prebid/prebid.js-getting-started/review-your-technical-integration.md).

# Review your technical integration

This guide gives you handy commands you can use within a Chrome-based browser to validate your technical integration

{% hint style="info" %}
The command inputs must be played in a Chromium-based browser.

By default, we use `pbjs` wrapper as an example for the command inputs. Replace it with your own wrapper. If you don’t know its name, you can find it with this command: `window._pbjsGlobals`.
{% endhint %}

## Check the required Prebid modules

### 1. Adagio bidder adapter

{% hint style="info" %}
**Step failed?** Review the integration documentation: [Adagio bidder adapter module](https://adagio-io.gitbook.io/adagio-documentation/prebid/getting-started-prebid-client-adapter/prebid-adagio-adapter)
{% endhint %}

**Console input command:**

```javascript
window.ADAGIO
```

**Expected console output**:

```javascript
// Should not be 'undefined'
{pageviewId: '4682f2c2-4d09-44ba-8766-5bf4e1ec35ec', adUnits: {…}, pbjsAdUnits: Array(3), queue: Array(0), versions: {…}, …}
```

### 2. RTD module and Adagio RTD provider

{% hint style="info" %}
**Step failed?** Review the integration documentation: [RTD module and Adagio RTD Provider](https://adagio-io.gitbook.io/adagio-documentation/prebid/getting-started-prebid-client-adapter/rtd-module)
{% endhint %}

**Console input command:**

```javascript
window.ADAGIO.hasRtd
```

**Expected console output**:

```javascript
// If false, means your missing rtd module, or adagio provider, or both
true
```

## Check the required wrapper configuration

### **1. Adagio required bidder parameters**

{% hint style="info" %}
**Step failed?** Review the integration documentation: [Adagio bidder parameters](https://adagio-io.gitbook.io/adagio-documentation/prebid/getting-started-prebid-client-adapter/prebid-adagio-adapter#add-the-necessary-adagio-bidder-parameters-required)
{% endhint %}

**Console input command:**

```javascript
pbjs.getEvents().filter((e) => e.eventType === "bidRequested").filter(e => e?.args?.bidderCode.toLowerCase().includes('adagio')).map(e => e?.args?.bids).flat()
```

**Expected console output**:

```javascript
// Go deep in the bids array to review Adagio setup
params: {
  organizationId: "XXXX",  // Required
  site: "my-site",         // Required
  placement: "my-adg-placement",       // Required
},

...
ortb2Imp: {
  ext: {
    data: {
      divId: "div-gpt-ad-1460505748561-0", // Required

    }
  }
},
```

### **2. RTD Module and Adagio RTD Provider (`since Prebid 9`)**

{% hint style="info" %}
**Step failed?** Review the integration documentation: [RTD Module](https://adagio-io.gitbook.io/adagio-documentation/prebid/getting-started-prebid-client-adapter/rtd-module#configure-the-adagio-rtd-provider-parameters)
{% endhint %}

**Console input command:**

```javascript
pbjs.getConfig('realTimeData')
```

**Expected console output**:

```javascript
dataProviders: [
  {
    name: "adagio",
    params: {
      organizationId: "XXXX", // Your organizationId
      site: "my-site" // Your website name as declared on the Adagio platform
    }
  }
]
```

### 3. Users sync

{% hint style="info" %}
**Step failed?** Review the integration documentation: [Device Access and iframe sync](https://adagio-io.gitbook.io/adagio-documentation/prebid/getting-started-prebid-client-adapter/other-recommended-settings#b.-device-access-and-iframe-sync)
{% endhint %}

**Console input command:**

```javascript
pbjs.getConfig('userSync')
```

**Expected console output**:

```javascript
// We require to be in 'iframe' as 'include'
// filterSettings.all also works
{
  filterSettings: {
    iframe: {
      bidders: ["adagio"],
      filter: "include"
    }
  }
}
```

### 4. Device Access

{% hint style="info" %}
**Step failed?** Review the integration documentation: [Device access](https://www.notion.so/5-Setup-the-Adagio-bidder-adapter-parameters-ba7270714f274a48a01428a0231ba13f?pvs=21)
{% endhint %}

**Console input command:**

```javascript
pbjs.getConfig('deviceAccess')
```

**Expected console output**:

```javascript
// Should not be 'false' or 'undefined'
true
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://adagio-io.gitbook.io/adagio-documentation/prebid/prebid.js-getting-started/review-your-technical-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.