Back to Bidders

ogury

Features

Registration

Before Ogury’s adapter integration, you have to register an account in the Ogury Platform. Please contact supply-development@ogury.co 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.

Bid Params

This is the minimal list of params for integrating with Ogury:

NOTE: You don’t need these params to integrate with Ogury, see inventory mapping

First Party Data

Publishers can use the ortb2 method of setting First Party Data. The following fields are supported:

• ortb2.site.publisher.id

this will be used with the inventory mapping method of integrating with Ogury.

Bidder config

There are two ways to integrate with Ogury ad server, via the “bid params” i.e. assetKey/adUnitId or via inventory mapping.

With bid params

Use this example configuration for enabling Ogury ad server integration on a specific ad unit:

 pbjs.que.push(function () {
    pbjs.addAdUnits([
        {
            code: 'example-ad-unit-code',
            mediaTypes: {banner: {sizes: [[1, 1]]} // example sizes
            },
            bids: [
                {
                    bidder: 'ogury',
                    params: {
                        assetKey: '$OGURY_ASSET_KEY',
                        adUnitId: '$OGURY_AD_UNIT_ID',
                    },
                }
            ]
            // rest of bidders
        }
        // rest of ad units
    ])
})

Inventory mapping

“Inventory mapping” is only available for request coming from web. For in-app request use the “bid param” integration method.

Note: If you choose inventory mapping, you can skip specifying assetKey and adUnitId per ad unit.

With inventory mapping you don’t need to setup assetKey/adUnitId for every ad unit that you want to integrate. You use a single id and provide Ogury with list of sites and ad_unit_codes that you want to integrate and the mapping will be done on our side. The example configuration for this type of integration looks like this:

pbjs.que.push(function () {
            // setup publisherId for ogury
            pbjs.setBidderConfig({
                bidders: ['ogury'],
                config: {
                    ortb2: {
                        site: {
                            publisher: {
                                id: '$OGURY_PUBLISHER_ID',
                            },
                        }
                    }
                }
            })
})

$OGURY_PUBLISHER_ID is a Ogury provided id.

Optional bid Params

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

Contact information

• For platform registration and partnership questions: supply-development@ogury.co
• For technical or integration issues with the adapter: web.inventory@ogury.co
• For technical issues with Prebid Server: deliveryservices@ogury.co

"Send All Bids" Ad Server Keys

Back to Bidders