- Shows how to load active cohorts for a visitor and pass them to Prebid.js via - mergeConfig. - It's assumed in this example that your primary ad server is - Google Ad Manager (GAM) and that you are integrated with it - using the - Google Publisher Tag (GPT), so - we also pass matching active cohorts to GAM. + This demo demonstrates how to integrate Optable's targeting capabilities with Prebid.js using the + OptableRTD module. + The implementation assumes Google Ad Manager (GAM) as the primary ad server, integrated via + Google Publisher Tag (GPT).
+ +
- In this example, we use the prebidORTB2FromCache() API to retrieve any targeting data from browser
- LocalStorage, in order to pass it to Prebid.js via seller defined audiences. We also call the SDK targeting API
- which will fetch the latest targeting data from our DCN and cache it locally for later use. Since these
- two events happen asynchronously, it's possible that the targeting data passed to GAM is slightly outdated.
- To ensure ad targeting accuracy, it is recommended to call targeting to update the local cache on
- page load.
+ The Prebid.js configuration requires minimal setup. Here's the essential configuration:
pbjs.mergeConfig({
+ debug: true,
+ priceGranularity: "low",
+ userSync: {
+ iframeEnabled: true,
+ enabledBidders: ["pubmatic"]
+ },
+ realTimeData: {
+ auctionDelay: 400,
+ dataProviders: [{
+ name: 'optable',
+ waitForIt: true // Required to respect auctionDelay
+ }]
+ }
+});targeting
+ on page load to update the local cache, as the RTD module only uses cached values.
+ localStorage.disableGamTargeting = "true"
+ before page load to prevent the SDK from sending targeting data to GAM.
+