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
  • Example of Nexx Web tag
  • Integrate the following script in the <head>:
  • Integrate the following script in the <body>
  • Nexx Web tag configuration
  • Typology of ad placements creation
  • Integration options
  • Amazon SSP integration
  • Teads SSP integration with client-side connexion

Was this helpful?

  1. Legacy - Direct call Nexx360
  2. Integrate Nexx Web script on your site
  3. Integration with GAM adserver

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>:

<head>
<script async src="//cdn.nexx360.io/loader.js"></script>
<script>
        var n360Ad = n360Ad || {};
        n360Ad.que = n360Ad.que || [];

        n360Ad.que.push(function(){
            n360Ad.setConfig({
                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']);
            n360Ad.defineOutOfPageSlot('/your_GAM_network_ID/your_GAM_adunit','div-1')
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setLabel('oop')
              .setTargeting('adunit', 'oop_ad')
              .setTargeting('position', 'atf');
            n360Ad.defineSlot('/your_GAM_network_ID/your_GAM_adunit',[[728,90],[970,250]],'div-2')
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setLabel('header')
              .setTargeting('adunit', 'header_ad')
              .setTargeting('position', 'atf');
            n360Ad.defineInjectedSlot('/your_GAM_network_ID/your_GAM_adunit',[[300,250],['fluid']],'div-3')
              .setNexx360TagId('ENTER YOUR PLACEMENT ID')
              .setInjectedSelector('h3')
              .setInjectedPosition('beforebegin')
              .setInjectedMaxRepetition(4)
              .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');
            n360Ad.refresh();
        })
        </script>
        </head>

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>.

 <body>
        <div id="div-2"></div>
        <script>
            n360Ad.que.push(function(){
                n360Ad.display("div-2");
            });
        </script>
        </body>

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:

n360Ad.setConfig:

  • 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).

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:

  • n360Ad.defineOutOfPageSlot: For an out-of-page ad slot.

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.

'/your_GAM_network_ID/your_GAM_adunit'
  • Size: Selection of inventory sizes for the ad placement.

[[728,90],[970,250]]
  • Div id: Div name that will be added in the <body> at the location where the ad slot is to be delivered.

'div-2'

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.

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,
    pubId: 'ENTER YOUR AMAZON PUB ID' 
}
  • 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('ENTER YOUR TEADS PAGE ID')
.setTeadsPlacementId('ENTER YOUR TEADS PLACEMENT ID')
  • setTeadsPageId: Teads Page ID

  • setTeadsPlacementId: Teads Placement ID related to the ad placement

PreviousIntegration with GAM adserverNextConnect the Google Ad Manager (GAM) account

Last updated 1 year ago

Was this helpful?

lazyloading : See feature's details and settings .

n360Ad.defineInjectedSlot: For an injected ad slot.

n360Ad.defineDynamicSlot: For a dynamic ad slot. .

Via then360Ad.setConfig function.

here
Follow this link to see instruction for integration.
Follow this link to see instruction for integration
described here