Testing Guide

Prerequisites

After registering your app, it may take up to 15 minutes before ads are available.

Ogury exclusively serves ads to users who have provided their consent.

Before conducting any tests, it is essential to ensure that your implementation complies with applicable privacy regulations. For more information on the regulations supported by Ogury, please visit the Privacy compliance page.

Test ad units

Because Ogury’s ad delivery relies on personified targeting, you may not consistently see ads while testing your application under normal conditions. To simplify testing, Ogury provides a dedicated test mode that guarantees test ads are always served.

How to use test mode

To enable test mode for a specific ad unit, append _test to your Ogury ad unit ID when initializing the SDK.

Example:

if your ad unit ID is

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Then your test ad unit ID becomes

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_test

Mediation-Specific Note

If you're integrating Ogury via a mediation platform (e.g., MAX AppLovin, Google Ad Manager, etc.), ensure you apply the _test suffix only to the Ogury ad unit ID in your mediation dashboard configuration.

Do not modify the mediation ad unit name or ID.

Be sure to remove the _test suffix from the ad unit ID before publishing your application to any store.

This is the recommended method for testing your implementation if you are using a VPN.

Enable logging

The Ogury SDK offers logging to help you monitor your integration status and identify any issues.

Android

By default, the Ogury SDK’s log level is set to ERROR, capturing only critical errors. To gain more insight into the integration process, you can enable DEBUG level logging by calling the following code:

Kotlin

OguryLog.enable(OguryLog.Level.DEBUG)

Java

OguryLog.enable(OguryLog.Level.DEBUG);

To turn off logging, simply set the log level to NONE.

Be sure to remove this logging code before publishing your application to any store to avoid unnecessary log output in production.

Viewing logs

1. Connect your device to Android Studio.

2. Open the Logcat window.

3. Filter logs using the keyword OGURY to focus on SDK-related entries.

iOS

By default, the Ogury SDK logs only critical errors (error level). To gain more visibility into the SDK behavior, you can enable debug level logging:

Swift

Ogury.setLogLevel(OguryLogLevel.all)

Objective-C

[Ogury setLogLevel:OguryLogLevelAll];b

To turn off logging, simply set the log level to none.

Be sure to remove this logging code before publishing your application to any store to avoid unnecessary log output in production.

Viewing logs

1. Connect your iOS device and run the app via Xcode.

2. Open the Console tab in the Debug area.

3. Use the filter at the bottom of the console to search for OGURY and isolate SDK logs.

Troubleshooting

If you encounter any issues during your integration that you are unable to resolve, please don't hesitate to reach out to the Ogury support team at [email protected] for assistance.