Registered Prebid.js bidder adapter

Adelerate Prebid Adapter

Add Adelerate to an existing Prebid.js stack with bidder code adelerate. Send display, video, and native opportunities into Adelerate while keeping your publisher-side setup familiar.

Up to 1,000,000 impressions free · no credit card · business email required

BIDDER CODEadelerate
PREBID.JSSupported
MEDIA3 formats
MULTI-FORMATWill bid on any
Configure the adapter

Two required IDs. One bidder entry.

Add the adelerate bidder to each eligible Prebid ad unit, then pass the publisher and placement IDs supplied by Adelerate. Floors can be passed directly, although Prebid recommends its Floors Module when available.

Check the live adapter specification →
const adUnits = [{
  code: 'video-slot',
  mediaTypes: {
    video: {
      context: 'instream',
      playerSize: [[640, 360]],
      mimes: ['video/mp4']
    }
  },
  bids: [{
    bidder: 'adelerate',
    params: {
      placementId: 'YOUR_PLACEMENT_ID',
      publisherId: 'YOUR_PUBLISHER_ID',
      floor: 0.50,
      floorCurrency: 'USD'
    }
  }]
}];
ParameterScopePurpose
placementId Required The Adelerate placement identifier connected to the ad unit.
publisherId Required The publisher identifier supplied by Adelerate.
floor Optional A minimum CPM value. The Prebid Floors Module is preferred when available.
floorCurrency Optional Currency for the floor value; defaults to USD.
What happens after requestBids()

Prebid in the browser. Auction intelligence on the server.

Prebid.js calls the Adelerate adapter for an eligible ad unit. The adapter packages the opportunity for the Adelerate endpoint, where server auction demand can compete before a bid response returns to the page.

01

Prebid ad unit

The page defines media type, size, and Adelerate bidder parameters.

02

Adapter request

The registered adapter validates the bid and builds the request.

03

Server auction

Eligible demand is evaluated on the Adelerate side under publisher controls.

04

Bid response

The adapter translates the response back into the Prebid auction.

Important distinction: Adelerate's current official listing documents a Prebid.js adapter, not a Prebid Server adapter. The server auction described here is Adelerate platform behavior behind the Prebid.js integration.

Video workflow

Prebid video joins the same delivery path.

For video, the adapter can pass the player and creative requirements defined on the Prebid ad unit. Built-in Prebid Cache supports video and AMP workflows, so cached bids can be evaluated alongside direct and server-auction demand before the winning VAST creative is delivered and tracked.

01 BIDDER RESPONDS 02 PREBID CACHE COMPANY-LEVEL URL KEY ISSUED 03 AT RENDER RETRIEVED BY CACHE KEY NO REPEATED AUCTION CALL 04 PULSERANK UNIFIED DECISION LAYER VIDEO + DIRECT + AUCTION 05 WINNING VIDEO CREATIVE SERVED + TRACKED
Server-side cookie sync

Coordinate auction identity with consent in the loop.

Adelerate supports server-side cookie sync for eligible auction demand. Instead of building a separate publisher integration for every partner, the server can coordinate bidder ID mappings used in downstream auction requests.

Cookie sync is not a cookieless shortcut. It must follow the publisher's CMP configuration and applicable privacy signals. Where consent is required, requests and sync activity should only proceed when the relevant signal permits them.

Read the Ad-Tech Privacy Policy →
Consent setup

Check your CMP behavior before going live.

The current Prebid.org listing notes that Adelerate does not declare an IAB Europe GVL ID. Under GDPR, Prebid core can withhold bid requests and user syncs unless the publisher's CMP setup explicitly permits the adapter. Review the current listing and validate the behavior for every jurisdiction you serve.

Add Adelerate to your Prebid stack.

Test the full video ad server free for up to 1,000,000 impressions. No credit card.