Back to Bidders



Bidder Code ogury Member no
Prebid.js Adapter yes Prebid Server Adapter no
Media Types display Multi Format Support check with bidder
TCF-EU Support yes IAB GVL ID 31
GPP Support check with bidder DSA Support check with bidder
USP/CCPA Support no COPPA Support no
Supply Chain Support no Demand Chain Support no
Safeframes OK no Supports Deals no
Floors Module Support yes First Party Data Support check with bidder
User IDs none ORTB Blocking Support check with bidder
Privacy Sandbox check with bidder


Before Ogury’s adapter integration, you have to register an account in the Ogury Platform. Please contact if you’re interested in a partnership. If you already have an account you’ll need to register your websites (= assets) and the placements (= ad units) within the Platform. Alternatively reach out to your POC within Ogury to assist you with the placement creation. A detailed overview about the integration process can be found in this documentation.

After this registration, you will receive the Asset IDs and Ad Unit IDs to start the integration.

Mandatory bid Params

The minimal list of bid params is:

Name Scope Description Example Type
assetKey required The asset key provided by Ogury 'OGY-CA41D116484F' string
adUnitId required Your ad unit id configured with Ogury '2c4d61d0-90aa-0139-0cda-0242ac120004' string

Optional bid Params

Depending on your advertising format needs, other optional parameters can be used. Supported parameters are detailed here.

How to contact us

If you have any technical concerns or questions about the adapter, please contact

"Send All Bids" Ad Server Keys

These are the bidder-specific keys that would be targeted within GAM in a Send-All-Bids scenario. GAM truncates keys to 20 characters.
hb_pb_ogury hb_bidder_ogury hb_adid_ogury
hb_size_ogury hb_source_ogury hb_format_ogury
hb_cache_host_ogury hb_cache_id_ogury hb_uuid_ogury
hb_cache_path_ogury hb_deal_ogury

Back to Bidders