This article describes two types of implementing the Relevant Yield Header HB Manager wrapper with managed and unmanaged ad server
Understanding manageAdserver
in Prebid
The manageAdserver setting is a fundamental decision that defines how Prebid via Relevant Yield HB Manager integrates with your ad server. It dictates who manages ad slots, key-values, and overall ad delivery logic.
If the Publisher Wants... | Then Choose... | Why? |
Operational Simplicity & All Relevant Yield Optimisation Capabilities | manageAdserver: true |
Leverages Relevant Yield for making faster changes without developers and easy optimisation & testing capabilities. |
Absolute Control & Custom Logic | manageAdserver: false |
Offers maximum independence and flexibility for complex, custom or established in-house setups. |
Option 1: manageAdserver: true
(Managed Ad Server)
Choosing true
means programmatic and advertising teams are able to use actively and easily make changes in ad server configuration and delivery without the need of developers. This approach centralises much of the logic outside of the site code and into Relevant Yield user interface.
Key Considerations for Managed Approach
-
Configuration Hub: Most configuration changes are handled through Relevant Yield's interface, rather than directly in the site's codebase.
-
Reduced Direct Control Through Site Codebase: The site has less immediate, direct control over the ad server's internal behavior and scripts because the handling is done in Relevant Yield.
-
Custom Setups: Highly custom or experimental ad server logic may require adjustments to integrate properly.
Detailed Description of Managed Ad Server Functionality
-
Streamlined Operations: Less ad server-specific scripting is required on your site, reducing complexity.
-
Automated Targeting: Relevant Yield automatically pushes targeting key-values directly to the ad server—minimal manual setup required.
-
Agile Updates: You can adjust ad sizes and formats quickly within Relevant Yield without frequently changing site code.
-
Optimisation Features: Access to built-in Relevant Yield capabilities like ad refresh and lazy loading.
-
Flexible Placements: Easier handling of dynamic or responsive ad placements and div IDs.
Option 2: manageAdserver: false
(Unmanaged Ad Server)
Setting manageAdserver
to false
is ideal when the publisher site retains full control and responsibility for all ad server scripts, slots and targeting logic. The site manages the integration and Prebid only handles the auction.
Key Considerations for Unmanaged Approach
-
Resource Demand: Requires more dedicated hands-on management from the publisher's internal ad operations team.
-
Manual Key-Values: All ad server scripts and key-value targeting must be implemented and maintained manually by the site team.
Detailed Description of Unmanaged Ad Server Functionality
-
Maximum Independence: The site team maintains full, direct control over all ad server scripts, logic, and behavior.
-
Unrestricted Customisation: Best for sites with highly custom, complex or unique ad server setups.
-
In-House Troubleshooting: Updates and troubleshooting can be managed entirely in-house, without reliance on a third-party interface.
Summary
If the site prefers simplicity, faster changes, and use of Yield’s built-in optimisation features, choose manageAdserver: true.
If the site requires full control of the ad server and already has robust in-house ad management, manageAdserver: false may be preferable.
Setting |
Managed by |
Site Ad Server Code |
Key-Values |
Flexibility |
Maintenance |
---|---|---|---|---|---|
true |
Yield / Prebid | Minimal | Automatic | High (dynamic divs, sizes) | Low |
false |
Site / Publisher | Full | Manual | Full ad server control | Higher |