Nexx360 Documentation
  • Nexx360 solutions
  • Nexx360 account
    • Account creation
    • Account settings
      • Add and manage users
      • Configure bidders
      • Create blocklists
      • Implement throttling
  • General configuration
    • Introduction
    • Add and manage websites
    • Add and manage tagIds
    • Bid reductions
    • Cookie Sync script
    • Available bidders
  • Prebid Adapter
    • Introduction
    • Update Prebid with Nexx360 Adapter
    • Multiformat bids
  • VAST / CTV
    • Introduction
    • Create VAST Config
    • Build VAST ad tag
    • Connect the Google Ad Manager (GAM) account
    • Cookie Sync
    • Sample CTV Tag
  • Native
    • Introduction
    • Native Configs
    • GET
    • POST
    • Sample Response
  • Direct Call
    • Introduction
    • API Reference
    • Microsoft AST Example
    • Google Ad Manager Example
      • Connect the Google Ad Manager (GAM) account
  • AMP Nexx360
    • Introduction
    • Ad Server setup
    • Add rtc-config object to amp-ad units
  • OpenRTB
    • Introduction
    • Video Example
    • Mobile Example
    • Cookie Sync
  • Inapp
    • Introduction
    • Request Exemple
    • Google Ad Manager setup
  • API Management
    • Introduction
    • Connexion
    • Sites
      • Create a new site
      • Update site
      • Get Site
      • List Sites
    • TagIds (Stored requests)
      • Create a new tagId (stored request)
      • Update tagId (stored request)
      • Get tagId (Stored request)
      • List tagIds (Stored requests) by site
  • API Campaign
    • Introduction
    • Connexion
    • Orders
      • Create a new order
      • Update order
      • Get Order
      • List Orders
    • Line Items
      • Create a Line Item
      • Update Line Item
      • Get Line Item
      • List Line Items by Order
    • Creatives
      • Create a Creative
      • Update Creative
      • Get Creative
      • List Creatives by Line Items
  • Legacy - Direct call Nexx360
    • Introduction
    • Nexx Web features
      • Smart autorefresh
      • Incontent injection
        • Automated injection
        • Dynamic injection
      • Lazy Loading
      • Non-consent traffic monetisation
    • Integrate Nexx Web script on your site
      • Integration with GAM adserver
        • Nexx Web tag
        • Connect the Google Ad Manager (GAM) account
      • Integration with Xandr adserver
  • Nexx360 console
  • Nexx360 site
Powered by GitBook
On this page
  • RTC setup
  • Cookie-sync setup

Was this helpful?

  1. AMP Nexx360

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>

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.

If you have configured a CMP, ensure to link the call to amp-adunit 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>

The rtc-config code can be directly copied from the button on the top right of the website page "View rtc-config".

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.

This process is GDPR compliant, as it will not be executed if a user doesn't provide consent.

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>

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>

PreviousAd Server setupNextIntroduction

Last updated 5 months ago

Was this helpful?

See additional documentation here: .

👉
https://amp.dev/documentation/components/amp-iframe/