Header Bidding & Cookieless Solutions

Our Teads Cookieless Tag and our Prebid User ID module have the same objective of dropping a 1st party cookie on publisher’s pages. The Teads user ID module is the preferred solution for Prebid users as it will reduce the lift of the integration.

Our Teads cookieless tag remains compatible on header bidding environment and vice versa: 

• Prebid + User module ✅

• JS + Cookieless Tag ✅

• Prebid + Cookieless Tag ✅

• JS + User Module ✅

We now have a complete cookieless solution on header bidding environment: 

• Our Prebid User ID Module allows us to drop a 1st party cookie on publishers’ pages.

• Publishers can also send us their 1st party IDs thanks to sharedID (https://prebid.org/product-suite/sharedid/) 

• We can also retrieve other unique IDs if publishers are using those modules

Prebid - "Teads" User ID module

If you are using Prebid, we want to offer an alternative to our cookieless tag for dropping 1st party Teads cookie IDs.

By building this Teads-specific prebid user ID module, we will reduce the lift required by publishers to enable Teads to generate 1st party cookies

Requirements and how to? 

This project is part of the 7.23.0 (or later) version of Prebid. Prebid documentation and setup can be found here: https://docs.prebid.org/download.html

Select Teads under the list of Bidder Adapters & under the list of User ID modules and the other providers you work with. 



We advise you to leave all the recommended modules by Prebid.js checked. 
To make the Teads user ID module works, you have to select at least the GDPR & US Privacy modules, as well as 1st party data enrichment:

• ☑ Consent management - GDPR

• ☑ Consent management - US Privacy 

• ☑ GDPR enforcement

• ☑ First party data enrichment
  
  
  Setup under prebid
  To use this Teads User Id module correctly, you have to set your publisher Id in the configuration.
  To do that, you can copy that code part and add this Prebid.js configuration to your codebase

  pbjs.setConfig({
  userSync: {
  userIds: [{
  name: 'teadsId',
  params: {
  pubId: [Add your publisher id]
  }
  }]
  }
  });

  
  
  If you already have a configuration in place, you can only add the userSync parameter at the root of the object passed to setConfig

  userSync: {
  userIds: [{
  name: 'teadsId',
  params: {
  pubId: [Add your publisher id]
  }
  }]
  }

  
  Or if you already have a userIds object defined, add an entry for the Teads user ID module :

  {
  name: 'teadsId',
  params: {
  pubId: [Add your publisher id]
  }
  }

  
  
  Prebid - Retrieve Publisher and Unique IDs
  
  For prebid publishers, we want to use the existing modules to retrieve and store publisher 1st party IDs and email-based identifiers (UID2, Universal ID) rather than relying on Teads Cookieless tag.
  
  Requirements and how to: 
  
  This project is part of the 7.23.0 (or later) version of Prebid. Prebid documentation and setup can be found here: https://docs.prebid.org/download.html
  
  Select Teads under the list of Bidder Adapters and the other providers you work with. 
  
  Setup & supported shared viewer ids:
  
  For shared viewer ids, you can follow this documentation and activate the ID Module System they want from our supported list:
  https://docs.prebid.org/dev-docs/modules/userId.html#basic-configuration
  
  Here is the list of supported user ID name and the corresponding module to activate in Prebid :
  
  
  
  Once selected, you need to add the corresponding lines of code
  Example for SharedID: https://docs.prebid.org/dev-docs/modules/userId.html#sharedid