From 577fe0fcb715c76ecb37d92fcc601e8f098a4178 Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Wed, 16 Jul 2025 10:42:46 +0200 Subject: [PATCH 1/6] update ogury documentation with inventory mapping --- dev-docs/bidders/ogury.md | 69 +++++++++++++++++++++++++++++++++++++-- 1 file changed, 66 insertions(+), 3 deletions(-) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index 416d44ac71..8f5d3bb18c 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -22,15 +22,15 @@ gpp_sids: tcfeu, usnat, usstate_all --- ### Registration - Before Ogury's adapter integration, you have to register an account in the Ogury Platform. Please contact if you're interested in a partnership. +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](https://ogury-ltd.gitbook.io/mobile-web/header-bidding/ogury-prebid.js-adapter-integration). After this registration, you will receive the Asset IDs and Ad Unit IDs to start the integration. -### Mandatory bid Params +### Bid Params -The minimal list of bid params is: +This is the minimal list of params for integrating with Ogury: {: .table .table-bordered .table-striped } @@ -39,6 +39,69 @@ The minimal list of bid params is: | `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` | +NOTE: You don't need these params to integrate with Ogury, see [inventory mapping](#inventory-mapping) + +#### First Party Data + +Publishers can use the `ortb2` method of setting [First Party Data](https://docs.prebid.org/features/firstPartyData.html). +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: +```javascript + 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 +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_code`s 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: +```javascript +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](https://ogury-ltd.gitbook.io/mobile-web/header-bidding/ogury-prebid.js-adapter-integration#optional-configuration). From 1dac59d39c68dd3d0106a3e0fccad2a0bc9c724d Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Thu, 17 Jul 2025 12:28:09 +0200 Subject: [PATCH 2/6] add note for in-app inventory mapping --- dev-docs/bidders/ogury.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index 8f5d3bb18c..93cf322dd1 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -80,6 +80,9 @@ Use this example configuration for enabling Ogury ad server integration on a spe #### Inventory mapping + +_"Inventory mapping" is only available for request coming from **web**. For **in-app** request use the "bid param" integration method._ + 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_code`s 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: ```javascript From d525f76b6cfc58c2592b87ad01d375daf3ce4e13 Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Thu, 17 Jul 2025 14:39:00 +0200 Subject: [PATCH 3/6] add contact info and note for inventory mapping --- dev-docs/bidders/ogury.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index 93cf322dd1..0e1d6b002e 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -83,6 +83,8 @@ Use this example configuration for enabling Ogury ad server integration on a spe _"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_code`s 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: ```javascript @@ -109,6 +111,8 @@ pbjs.que.push(function () { Depending on your advertising format needs, other optional parameters can be used. Supported parameters are detailed [here](https://ogury-ltd.gitbook.io/mobile-web/header-bidding/ogury-prebid.js-adapter-integration#optional-configuration). -### How to contact us +### Contact information -If you have any technical concerns or questions about the adapter, please contact . +* 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 From f372fb4f2b9c3b0af427f958d2a6dc0a3c336be9 Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Mon, 21 Jul 2025 12:39:17 +0200 Subject: [PATCH 4/6] return links to email doc --- dev-docs/bidders/ogury.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index 0e1d6b002e..1725765bc4 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -113,6 +113,6 @@ Depending on your advertising format needs, other optional parameters can be use ### 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 +* For platform registration and partnership questions: +* For technical or integration issues with the adapter: +* For technical issues with Prebid Server: From 6d5e070553bb098c9b0d00b6079c147f699b40bb Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Mon, 21 Jul 2025 12:42:36 +0200 Subject: [PATCH 5/6] fix formatting --- dev-docs/bidders/ogury.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index 1725765bc4..c848fec7a8 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -55,6 +55,7 @@ There are two ways to integrate with Ogury ad server, via the "bid params" i.e. #### With bid params Use this example configuration for enabling Ogury ad server integration on a specific ad unit: + ```javascript pbjs.que.push(function () { pbjs.addAdUnits([ @@ -76,6 +77,7 @@ Use this example configuration for enabling Ogury ad server integration on a spe // rest of ad units ]) }) + ``` @@ -87,6 +89,7 @@ _Note: If you choose inventory mapping, you can skip specifying assetKey and adU 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_code`s 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: + ```javascript pbjs.que.push(function () { // setup publisherId for ogury @@ -104,8 +107,8 @@ pbjs.que.push(function () { }) }) ```` -`$OGURY_PUBLISHER_ID` is a Ogury provided id. +`$OGURY_PUBLISHER_ID` is a Ogury provided id. ### Optional bid Params From 5f72ece99c734f1d2b9d5e2d475b0e4f65bd05f9 Mon Sep 17 00:00:00 2001 From: Ivan Krdzavac Date: Mon, 21 Jul 2025 12:43:44 +0200 Subject: [PATCH 6/6] missed whitespace --- dev-docs/bidders/ogury.md | 1 - 1 file changed, 1 deletion(-) diff --git a/dev-docs/bidders/ogury.md b/dev-docs/bidders/ogury.md index c848fec7a8..c6407a2a4b 100644 --- a/dev-docs/bidders/ogury.md +++ b/dev-docs/bidders/ogury.md @@ -80,7 +80,6 @@ Use this example configuration for enabling Ogury ad server integration on a spe ``` - #### Inventory mapping _"Inventory mapping" is only available for request coming from **web**. For **in-app** request use the "bid param" integration method._