Troubleshooting
Turning on console logs
You may add ogy_log=debug at the end of your page's URL to enable debug logging. For example:
More generally, the ogy_log query parameter supports the following verbosity levels:
debug: this is the most verbose level. It displays debug level messages as well as messages of all other levels.
info: this level displays info messages as well as messages of warning and error levels.
warning: this level displays warning messages as well as messages of error level.
error: default value; this is the least verbose level. It displays only error level messages.
Test Parameters
Ogury offers several URL parameters that can help you to test and verify your integrations. Simply add them via ? or & to your test or live page.
Forcing a test creative
By adding ogy_test_mode=video to your test URL you can force a video ad to be returned and ogy_test_mode=image will return a display test campaign.
Previewing different in-article creatives
Ogury's In-Article Format comes in three different variations: Reveal, MPU and Landscape. If you want to display a particular type you can add the URL parameter ogy_in_article_type and add either reveal, 300x250 or landscape as value. If you're working with prebid and multiple Ogury formats, this will also help to force the in-article ad over the other formats that you're using.
Changing the creative ratio
The In-Article Reveal format exists in different ratios. To preview the different versions, you can use the ogy_creative_ratio with the following supported values: 1.78 | 1.2 | 0.95 | 0.60 | 0.67 | 0.5.
Changing the creative orientation
Some creatives can exist in a horizontal or vertical version. To force a vertical preview ad, you can add ogy_creative_orientation=vertical to your test URL.
Changing the bid price
When you force an ad response in a Header Bidding scenario, the returned bid will have a CPM of 15 USD. You can change the bid price by using ogy_test_bid_price=<CPM> in case you need higher or lower CPMs for testing purposes. The following URL will return a display campaign with a bid of 5 USD CPM:
Impressions of test campaigns are not logged in the interface and won't count towards your revenue.
The test mode is bypassing several checks that would otherwise lead to a delivery block such as missing consent or wrong IDs used. Make sure you've followed the prerequisites and test your integration in the supported environments.
Best Practices
Below you'll find a check list that helps you to optimize and troubleshoot the monetization with Ogury. Some checks are integration specific, but there is also a general list that applies to all integration types. Two icons will indicate if the check list item is mandatory or optional (though still highly recommended)
✳️ mandatory
*️⃣ strongly recommended
General
Make sure that
✳️ | ads.txt is implemented correctly |
*️⃣ | only smartphones are targeted - no apps, nor consoles or smart TVs as those are not yet supported |
✳️ | only Ogury supported browsers are targeted, when using an ad server |
✳️ | you use a CMP with all requirements |
*️⃣ | the inventory is only targeted to non-GDPR territory when no CMP in place |
*️⃣ | Ogury is integrated in actual browser and not webviews or webapps |
*️⃣ | you exclude all AMP traffic - otherwise you'll run into uncomfortable impression rate and revenue situations |
*️⃣ | the Ogury ad formats are called with initial page load, preferably in the beginning of the code and without lazy loading |
*️⃣ | the ad formats are displayed on long article pages (that can guarantee a high VTR and CTR) rather than home pages and short content - better performance leads usually to more revenue 🤑 |
*️⃣ | Ogury formats aren’t already monetized by another marketer on a given website, because the formats can block or interfere with one another |
*️⃣ | there is no video ad unit in place that could overlay Ogury's formats because it can cause low viewability and therewith low revenue 🥲 |
✳️ | the publisher domain matches the one in the Ogury interface for the given placement IDs |
✳️ | the right IDs for the ad unit id and asset key are implemented |
✳️ | Header Thumbnail and Footer Ad aren't placed together on one page independent of the integration types, because it will generate errors and discrepancies |
*️⃣ | there is no aggressive refresh - Ogury isn't accepting format refreshing below 30 seconds |
✳️ | except for Standard Banners format |
Tag Based
Make sure that
✳️ | the custom code or tag isn't placed in the HTML head |
Prebid
Make sure that
*️⃣ | the latest version of Ogury's prebid adapter is used |
✳️ | the formats use the right device type for desktop and mobile integration |
*️⃣ | sticky ad formats aren't called in multiple slots as it will cause discrepancies |
*️⃣ | the the floor prices aren't too high so you'll receive all the demand |
*️⃣ | there is no additional prebid size filtering in place, because Ogury doesn’t have creatives with conventional sizes except for MPU and certain reveal |
*️⃣ | 0gury is only called on pages where the ad server targeting allows Prebid |
✳️ | the consent is submitted in the header bidding request as well - meaning that the Prebid consent module is activated |
*️⃣ | cached bids are only used once - make use of |
✳️ | all GAM line items have been created and the used keywords have been added properly into the GAM account as well |
*️⃣ | all needed key value pairs are submitted to your ad server to ensure that the bid can compete with the direct demand |
TAM
Make sure that
✳️ | the whitelisted slot/tag sizes are setup in the ad server line items as well |
*️⃣ | all AMP traffic is blocked or targeted with separate TAM Tag IDs for differentiation (otherwise it'll create discrepancies 😢) |
Keep Smiling, ALWAYS 😊
Last updated