Test your implementation
Last updated
Last updated
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.
Since our algorithm utilizes personalized targeting, you may not see any ads while testing your application. To facilitate testing, Ogury provides a test ad unit ID that ensures you always receive test ads when calling the Ogury SDK.
For testing purposes, simply append _test to your ad unit ID.
For example, if your ad unit ID is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, the corresponding test ad unit ID would be xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx_test.
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.
The Ogury SDK offers logging to help you monitor your integration status and identify any issues. To enable and view logs:
Connect your device to Android Studio
In the Logcat window, filter the logs using the keyword OGURY to easily isolate SDK-related entries from other system logs.
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:
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.
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 techsupport@ogury.co for assistance.
