Skip to content
  • There are no suggestions because the search field is empty.

Setting up the Relevant Digital (RD) Bid Adapter

This article explain the basics of the Relevant Digital Prebid Adapter, and how to set it up.

What this article covers

What is the RD bid adapter? 

The RD bid adapter is a Prebid-compliant bidder adapter that lets you participate in an existing publisher wrapper auction — without owning the wrapper. A typical use case is a sales house or network that wants to monetise inventory for a publisher who already runs their own Prebid setup. By adding the RD bid adapter to the publisher's wrapper, bid requests flow into a secondary auction where you can run your own SSPs, maximising demand and revenue.

Full technical details from Prebid's side are available at docs.prebid.org/dev-docs/bidders/relevantdigital.html.

 

How it works

RD bid adaper flow (1)

The original wrapper auction runs as normal, with its own set of SSPs and the RD bid adapter as one of the bidders. When the wrapper sends a bid request to the RD bid adapter, it triggers a separate secondary auction on our side — among the SSPs you have configured in Relevant Yield. The winning bid from that secondary auction is returned to the original wrapper, where it competes alongside all other bids.

 

Key considerations

No ad server connection The RD bid adapter does not control ad serving. Set Adserver: None at the placement level in Relevant Yield — the original wrapper handles everything after the auction.

No reloads or ad refresh Refresh logic is owned by the original wrapper. Reload/refresh settings in Relevant Yield will have no effect here.

Dimensions are inherited automatically The RD bid adapter picks up the dimensions defined in the original wrapper's bid request. You still need to select a placement type in Relevant Yield, but the dimension values themselves will be ignored. If you need to force specific dimensions instead, you can use the skip_imp_format override — though this is not recommended as a default.

 

Setup in Relevant Yield

Step 1 — Create the website and placements

Set up the site and placements in Relevant Yield as you would for any normal website. Add the SSP placement IDs for the SSPs you want to run in the secondary auction.

Important: Set Adserver: None at the placement level.

 

Step 2 — Enable Mobile in Prebid Parameters

Go to Prebid Parameters → General Settings → Enable Mobile and turn it on.

Once enabled, a small mobile icon will appear next to each placement.

 

Step 3 — Retrieve your adapter IDs

Click the mobile icon on the relevant placement. This gives you two IDs you will need:

Field in RY Prebid parameter name
Prebid Server Account ID accountId
AdUnit config ID placementId

You will also need your pbsHost. If you are unsure what this is, contact your Customer Success manager.

 

Publisher integration checklist

Once your setup in Relevant Yield is complete, send the following information to whoever manages the publisher's Prebid wrapper.

1. Ads.txt — update required The publisher's ads.txt file must include entries for each SSP you have added in the RD bid adapter auction.

2. CMP consent Relevant Digital must be given consent in the publisher's CMP. Our vendor ID is 1100.

3. Universal IDs Because bidding runs server-side, universal IDs are often required by the SSPs. Ask each SSP which IDs they prefer (e.g. Unified ID, SharedID, ID5).

4. Iframe user sync (recommended) Adding the snippet below to the publisher's Prebid config improves match rates and should increase revenue:


userSync: {
    filterSettings: {
      iframe: {
        bidders: "*",
        filter: "include"
      }
    }
  }
});
 
pbjs.bidderSettings = {
            standard: {
                     storageAllowed: true
            },
    }



If you have any more questions around the Prebid Adapter set up , or would like to know more about how it works in general, feel free to reach out to your Customer Success manager for Relevant Yield.