Prerequisites
Requirements to use Ogury Exclusive Demand
Consent Management
If your website will be trafficked in a country where GDPR applies, you must have implemented a consent management platform (CMP) which is compliant with TCF v2.2 and includes the Ogury vendor ID (31). The user consent must be given for purposes 1, 2, 7, 9 and 10.
Supported Environments
Ogury supports mobile web and desktop traffic, but is restricted to the following Browsers:
Mobile
Android
Chrome v83 and above
Samsung browser
Facebook browser
iOS
Chrome v83 and above
Safari v12.5 and above
Facebook browser
Desktop
Chrome 83 and above
Edge 83 and above
Safari v12.5 and above
Webviews and AMP Traffic are currently not supported.
If you want to monetize on mobile web and desktop, you'll need to create one ad unit per platform. Desktop ad unit ids start with wd and Mobile ad unit ids start with mw to facilitate the association 🙂
Placement Creation
To use the any for monetization, you have to register your websites (= assets) and the placements (= ad units) in the Ogury Platform. Please contact your publisher manager to create the necessary assets and ad units, optionally with different pricings to increase fill. Alternatively, you can create the placements by yourself. After this registration, you will receive the Asset IDs and Ad Unit IDs to start the integration.
Integration
At the moment you cannot monetize sticky formats, namely Thumbnail, Header Ad or Footer Ad simultaneously on the same page!
Thumbnail, Header Ad, Footer Ad & In-Article Formats are not compatible with SafeFrame and non friendly iFrames.
If you want to use the different sticky ad formats that Ogury offers, you can split them between your inventory or make sure, that they're never called on the same page view. Alternatively, you can use the passback functionality to call different formats after each other.
Ads.txt
To increase your fill rate and revenue, make sure you have implemented the ads.txt IDs on your websites.
Last updated