Getting Started with Demand Hub

Getting started with Demand Hub requires a series of precise configurations within your header bidding environment to ensure accurate targeting, compliance, and optimal bidding. Whether you are using a Client-Side (C2S) or Server-to-Server (S2S) architecture, this guide outlines the mandatory deployment steps you need to complete to properly integrate the adapter and unlock incremental revenue.

1. Prerequisite: Relevant Ad Unit Selection

Demand Hub displays a story-like format that relies on high on-screen view time to deliver strong performance.

Before beginning technical implementation, ensure you are mapping Opti Digital to highly viewable placements, such as sticky right-hand side rectangles on desktop or sticky bottom banners on mobile.

2. Core Deployment Steps (All Integrations)

Regardless of your integration mode, all publishers must complete the following standard steps:

CMP Configuration: You must update your Consent Management Platform (CMP) vendor list to include Opti Digital (Vendor ID 915) and its SSP partners. Once updated, you must resubmit audience consent via your CMP interface so users are prompted to consent to the new list. Without proper CMP integration, you will receive no bid responses.
Ads.txt / App-ads.txt Update: Add Opti Digital and its relevant demand partners to your web ads.txt or mobile app-ads.txt files. Your Opti Digital Account Manager will provide the specific lines containing your unique Publisher ID.
User Synchronization (Web Only): To ensure optimal match rates, you must enable iframe-based cookie syncing. This requires explicitly adding optidigital to the list of bidders in your pbjs.setConfig (unless you are using the * wildcard to represent all bidders). Without this, performance will be seriously impacted.
Ad Unit Configuration: When mapping Opti Digital to an ad slot, two variables are strictly mandatory:
- publisherId: The unique ID provided by your Account Manager.
- placementId: A value you define, which influences bidding decisions and performance analysis. It is highly recommended to use a clear, granular naming convention. Requests missing these parameters will be ignored.
Prebid Wrapper Requirements:
- For Web (C2S): Your Prebid.js build must include the Opti Digital bid adapter module. You can verify this in the browser console by checking for optidigitalBidAdapter in the installed modules list.
- For Apps: You must integrate the Prebid SDK.

3. S2S Specific Configuration

If you are running a Server-to-Server setup (either self-hosted or via a third party like Nexx360), a few additional steps apply:

Prebid Server Upgrade: Ensure your Prebid Server environment includes the Opti Digital Adapter. It is supported on Go (Golang) minimum version v3.18.0 and Java minimum version v3.29.0.
Prebid.js Update (Web): You must declare Opti Digital as an S2S bidder by adding optidigital to the list of bidders within the s2sConfig of your Prebid.js setup.

4. Troubleshooting & Verification

Once setup is complete, you can verify and debug your integration using Professor Prebid, a browser extension designed for header bidding analysis.

Specifically, you should use Professor Prebid to:

Confirm that Opti Digital appears in your list of active bidders.
Check that bid requests are being triggered correctly from the browser (or sent to the Prebid Server for S2S).
Inspect the returned bid responses to verify CPM values, targeting keys, and creative IDs.
Confirm that user sync (iframe mode) is active.

Getting Started with Demand Hub

A step-by-step guide for publishers on how to set up and configure Opti Digital's Demand Hub for both client-side and server-to-server header bidding environments.