Nexx Web tag

The Nexx Web tag is built on the Google Publisher Tag model to simplify integration.

The tag provided below will replace your Google Publisher Tag, which will be embedded into it to establish a connection with your Google Ad Manager account.

The integration, its characteristics and options are described below.

Example of Nexx Web tag

Integrate the following script in the <head>:

<script async src="//"></script>
        var n360Ad = n360Ad || {};
        n360Ad.que = n360Ad.que || [];

                account: 'ENTER YOUR CUSTOMER ID',
                gdpr: 1,
                timeout: 2000,
                ids: {
                    id5: { partnerId: ENTER YOUR CUSTOMER ID },
                targeting: {
                    key1: 'value1',
                    key2: ['value1', 'value2']
                lazyLoading: {
                    isActive: 1,
                    fetchRatio: 2,
                    mobileFetchRatio: 4,
                amazon: {
                    isActive: 1,
                    pubId: 'ENTER YOUR AMAZON PUB ID' 
            n360Ad.setTargeting('key1', 'value1');
            n360Ad.setTargeting('key2', ['value1', 'value2']);
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setTargeting('adunit', 'oop_ad')
              .setTargeting('position', 'atf');
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setTargeting('adunit', 'header_ad')
              .setTargeting('position', 'atf');
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setInjectedStyle('text-align:center; margin-bottom: 20px;')
              .setInjectedLabel('adunit', 'incontent_ad')
              .setTargeting('adunit', 'incontent_ad')
              .setTargeting('position', 'mtf')
              .setTeadsPageId('ENTER YOUR TEADS PAGE ID')
              .setTeadsPlacementId('ENTER YOUR TEADS PLACEMENT ID');

Integrate the following script in the <body>

Then, you need to indicate where the ad unit will appear by integrating the following code in the <body> at the selected location. The corresponding code must be added for each ad slot defined in the <head>.

        <div id="div-2"></div>

Check that your div ID matches the ID indicated during the ad slot definition.

The corresponding code must be added for each ad placement defined in the<head>.

Nexx Web tag configuration

The Nexx Web tag needs to be configured with the fields described below at two levels:


  • account: Nexx360 customer ID indicated at the right top of the console.

  • gdpr: 1 or 0 according to the CMP set up, active or not.

  • timeout: The value can be modified (2000 is the recommended value).

  • ids : Enables to configure User ID modules.

  • targeting: Values enabling the definition of customised attributes for the page. Used for targeting and reporting in Google Ad Manager. Targeting could be also configured via the functionn360Ad.setTargeting (see below).

  • lazyloading : See feature's details and settings here.

n360Ad.defineSlot (or n360Ad.defineOutOfPageSlot and n360Ad.defineInjectedSlot):

  • setNexx360Id : Placement ID indicated for each line of the placements list.

  • setLabel : Value allowing to name the ad slot that will be used for Nexx360 reporting.

The setLabel notion is important and highly recommended because it takes action in monetization. This notion is transferred via the bid request and is used by SSPs to classify inventory.

Typology of ad placements creation

The feature n360Ad.defineSlot incorporates the principles of googletag.defineSlot with the same elements.

There is different variants of n360Ad.defineSlot function:

Each field must be replaced by your own configuration parameters:

  • Ad unit: Fill in the link to the ad unit as defined in the Google Ad Manager inventory.

  • Size: Selection of inventory sizes for the ad placement.

  • Div id: Div name that will be added in the <body> at the location where the ad slot is to be delivered.


n360Ad.setTargeting feature enables the definition of customised attributes for the page and/or the ad slot. They are used for targeting and reporting in Google Ad Manager.

// Targeting at page level

n360Ad.setTargeting('key1', 'value1');

// Targeting at ad placement level

.setTargeting('adunit', 'header_ad')

The Targeting part of the page could be configured with two different ways:

  • Via the n360Ad.setTargeting function described above.

  • Via then360Ad.setConfig functiondescribed here.

Integration options

Different fields are optionals depending on your configuration.

Amazon SSP integration

You can activate the Amazon SSP with those specific lines of code.

amazon: {
    isActive: 1,
  • isActive: 1 or 0 according to the activation or not for Amazon.

  • pubId: Publisher ID Amazon with 36 characters.

Teads SSP integration with client-side connexion

You can activate Teads SSP (while waiting for its server-side adapter) by adding the following code at the ad slot definition level n360Ad.defineSlot (operation to repeat for each relevant placement).

  • setTeadsPageId: Teads Page ID

  • setTeadsPlacementId: Teads Placement ID related to the ad placement

Last updated