# Add rtc-config object to amp-ad units

Once the placements creation and the GAM connexion are complete, you need to add the rtc-config object in your AMP tags. Real Time Config (RTC) is an AMP feature used for Header Bidding to make request calls to your SSPs.

## RTC setup

Add the rtc-config object in your amp-ad unit, as in the following example:

```
<amp-ad
    width="300"
    height="250"
    type="doubleclick"
    data-slot="/your_GAM_network_ID/your_amp_adunit"
    rtc-config='{"vendors":
            {
                "nexx360": {
                  "ACCOUNT_ID": "ENTER YOUR CUSTOMER ID",
                  "TAG_ID": "ENTER YOUR PLACEMENT ID"
                }
            }
        }'
    >
</amp-ad>
```

{% hint style="warning" %}
Replace “ACCOUNT\_ID” and “TAG\_ID” with your unique IDs, which can be found in the “Sites management” tab:

* ACCOUNT\_ID => Customer ID present at the top right of the UI.
* TAG\_ID => Placement ID available on each line of the placements list.
  {% endhint %}

{% hint style="warning" %}
If you have configured a CMP, ensure to link the call to `amp-ad`unit to the user consent by adding the attribute `data-block-on-consent` in the ad unit.

Integrate the following script in the`<head>` :

```
<script async custom-element="amp-consent" src="https://cdn.ampproject.org/v0/amp-consent-0.1.js"></script>
```

{% endhint %}

{% hint style="info" %}
The rtc-config code can be directly copied from the button on the top right of the website page "View rtc-config".
{% endhint %}

## Cookie-sync setup

You can add the cookie-sync functionality to help bidders identify the user and bid accordingly. While this step is optional, it is recommended to improve attractiveness to bidders.

{% hint style="info" %}
This process is GDPR compliant, as it will not be executed if a user doesn't provide consent.
{% endhint %}

Here is the script to add to your page:

```
<amp-iframe
    width="1"
    height="1"
    sandbox="allow-scripts"
    frameborder="0"
    src="//cdn.nexx360-static.io/load-cookie.html">
</amp-iframe>
```

{% hint style="warning" %}
**Implementation recommendations:**

* The iframe must be either 600 px away from the top or not within the first 75% of the viewport when scrolled to the top.
* To display a valid iframe, please add the `amp-iframe` component on your AMP page (if not already present). See required script below:

```
<script async custom-element="amp-iframe" src="https://cdn.ampproject.org/v0/amp-iframe-0.1.js"></script>
```

:point\_right: See additional documentation here: <https://amp.dev/documentation/components/amp-iframe/>.
{% endhint %}


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://developer.nexx360.io/integration-methods/amp/add-rtc-config-object-to-amp-ad-units.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
