Contact usContact us

Test Ad Quality SDK

To see if the Ad Quality SDK is integrated and working properly, check the IDE console logs as explained below: 

  1. Turn on the console logs as described in the SDK integration article (step 3)
  2. Set the log configuration to see info logs of all ad-network SDKs that are integrated into your app
  3. Once you open the app and the Ad Quality SDK is initialized, you’ll start seeing Info logs

For example:

IronSource AdQuality: AdQualitySDK: -------------- network connector 4.1.2 --------------
Network A SDK version: 5.6.0
SDK Versions supported: 4.7.0 - 5.6.0
Status: OK

The log will show the detected ad network’s SDK version, and the SDK versions supported by Ad Quality. If the status is ‘OK,’ then the ad-network SDKs are integrated correctly.

Test guidelines

  • Set the setTestMode configuration to true, so impression data is sent to the server immediately instead of using the time and impressions thresholds
  • Make sure your app’s live-build is deployed without the setTestMode configuration
  • The data on the dashboard is being updated every 4 hours

Verifying the integrity of the integration

  • Make sure you see logs for each of the ad-network you’ve integrated
  • Check that each network is working correctly and that its status is ‘OK’
  • In case that ad network is not on ‘OK’ status, fix the issue and rerun the app, then make sure that status has changed to ‘OK’

Example Log Issues

Example 1

IronSource AdQuality: AdQualitySDK: RemoteConfig: Error getting config from server: 403

This means that Ad Quality SDK was initialized with an appKey that does not exist. This is the same error that is shown when the Ad Quality SDK is disabled. Check the app’s settings on the Ad Quality dashboard to see if this is the case.

Example 2

IronSource AdQuality: AdQualitySDK: -------------- network connector 4.1.2 --------------
network SDK version: Not fetched - please make sure your version is supported
SDK Versions supported: 4.25.0 - 5.2.0
Status: OK

This means that Ad Quality couldn’t fetch the right version of the ad network’s SDK and is asking you to manually confirm that you’re using a supported version. Once you manually confirm, you’ll be all set.

Example 3:

IronSource AdQuality: AdQualitySDK: -------------- network connector 1.4.1 --------------
network SDK version: 6.7.0
SDK Versions supported: 4.22.0 - 6.6.0
Status: ERROR
Message: Network A SDK version 6.7.0 is not yet supported by the connector

The status here is ‘ERROR’ because your Ad Quality SDK version does not support the ad network’s SDK. For this type of issue, contact Ad Quality support.

Example 4:

IronSource AdQuality: AdQualitySDK: -------------- network connector 1.1.1 --------------
network SDK version: 12.2.1
SDK Versions supported: 11.8.0 - 12.2.1
Status: ERROR
Message: Tapjoy sdk version 12.2.1 requires Ad Quality sdk version 6.2.0 or newer

Sometimes there’s a dependency between the remote Ad Quality connector version and the Ad Quality SDK version. In this example, the SDK was updated remotely while the Ad Quality SDK was not. To solve this issue, upgrade your Ad Quality SDK to the latest version.

Example 5:

IronSource AdQuality: AdQualitySDK: -------------- network connector 1.1.3 --------------
network SDK version: 11.6.0
SDK Versions supported: 9.0.0 - 11.6.0
Status: ERROR
Message: Failed to initialize connector
IronSource AdQuality: AdQualitySDK: -------------- network connector --------------
Status: ERROR
Message: Failed to create connector

For failure to create or initialize a connector, contact Ad Quality support.

How to check if the Ad Quality SDK is counting impressions

When setting the log level to Debug or Verbose, you’ll be able to see the events that the Ad Quality SDK is trying to send to the server. These are some of the log messages you should look for after viewing an ad:

IronSource AdQuality: Analytics: Trying to send event: ad_displayed and extra info: {...}
IronSource AdQuality: Analytics: Trying to send event: iab_displayed and extra info: {...}
IronSource AdQuality: Analytics: Trying to send event with name: ad_displayed
IronSource AdQuality: Analytics: Trying to send event: imp_extra with extra info: {...}