The DT FairBid Test Suite allows you to check that your app is set up correctly and ready to mediate using DT FairBid mediation. The Test Suite enables you to verify that the mediated networks associated with the app are fully integrated, that Placements and Instances are set up as expected and that ads are served successfully.

Launching the Test Suite

Upon launching, the Test Suite offers the following diagnostic tests:

• Mediated Networks Integration Status: Determines whether mediated networks are properly integrated and ready to serve ads.
• Placements: Determines whether all configured Placements and Instances in the Console are properly set up and run as expected by DT FairBid's auction on a real-time ad request to your test device.

Launching the Test Suite via SDK

Complete the following steps to launch the Test Suite via SDK or start the app in debug mode.

FairBid.showTestSuite(activity);

FairBid.presentTestSuite()

[FairBid presentTestSuite];

FairBid.ShowTestSuite();

Launch the Test Suite from Your App

Launching the Test Suite from your app is only available when your app is in Debug mode (signed with a Debug certificate) and contains integration errors. No explicit SDK call is required.

Complete the following steps to launch the Test Suite from your app:

1. Sign your app with a Debug certificate, and start your app.
   If the FairBid SDK detects integration errors, a pop-up that summarizes the errors found automatically appears.

2. Tap Test Suite.
   The Test Suite opens with additional diagnostic details.

Mediated Networks Integration Status

The main screen of the Test Suite gives you an immediate idea of your mediated network's integration status. The associated mediated networks are connected and enabled when the screen is green and Successful Integration appears. Refer to Testing Mediation Placements, which describes how to test the instances in your app.

If the screen is red, and an Unsuccessful Integration appears, the Test Suite encountered errors while attempting to connect to your mediated networks. DT recommends correcting the identified issues before going live with your app. Tap the red square for more information about the mediation errors.

SUCCESSFUL INTEGRATION	UNSUCCESSFUL INTEGRATION

Troubleshooting Integration Errors

Integrating a mediated network can be tricky, and many issues might occur. Not all of your mediated networks are successfully integrated if a red screen is shown. Tap the red square to see more details of the errors encountered. Here is the list of issues the Test Suite can help you identify and how to fix them.

Missing SDK

Android iOS Unity

ISSUE DESCRIPTION	SUGGESTED FIX
The DT FairBid SDK requires the mediated ad network's SDK to work. If the Test Suite mentions that a network is missing its SDK, then it might mean you forgot to insert the network's SDK into your project.	Refer to the documentation on integrating that specific network into your project to resolve this problem.
If the AdMob SDK is not implemented or configured in the Console but the Google Play Services API is still used in the project, the following error occurs when you integrate AdMob.	This message only applies to AdMob integrations. If you are not planning to integrate AdMob, you can ignore this error message.

ISSUE DESCRIPTION	SUGGESTED FIX
The DT FairBid SDK requires the mediated ad network's SDK to work. If the Test Suite mentions that a network is missing its SDK, then it might mean you forgot to insert the network's SDK into your project.	Refer to the documentation on integrating that specific network into your project to resolve this problem.
To allow attribution using SKAdNetwork, demand partners must register with Apple. Developers must configure their apps to work with ad networks by specifying SKAdNetwork IDs. Per Apple's SKAdNetwork documentation, you must include these IDs in the app's Info.plist file.	The Supported Networks Table allows you to select each network that you have integrated and produces the snippet for you to insert into the Info.plist You can also use the SKAdNetwork ID Auto Updater tool to manage SKAdNetwork IDs directly from XCode or Unity Editor -ensuring the list you have is always automatically updated.

ISSUE DESCRIPTION	SUGGESTED FIX
The DT FairBid SDK requires the mediated ad network's SDK to work. If the Test Suite mentions that a network is missing its SDK, then it might mean you forgot to insert the network's SDK into your project.	Refer to the documentation on integrating that specific network into your project to resolve this problem.

Not Configured in the Console

ISSUE DESCRIPTION	SUGGESTED FIX
DT FairBid SDK requires the mediated ad networks to be enabled in the console. If the Test Suite mentions that a network is not configured in the console, it means you might have forgotten to enable it and configure it for your application in the console.	Refer to the documentation on integrating that specific network into your project to resolve this problem.

Missing Credentials

ISSUE DESCRIPTION	SUGGESTED FIX
For the mediation stack of the DT FairBid SDK to work, the SDK needs to have access to your credentials for the different networks you integrate. If the Test Suite mentions that a network is missing credentials, it means the network was not configured with credentials in the Console.	Access the Console and verify that credentials are correctly configured for the relevant network to resolve this issue.

Missing Activities

Android iOS Unity

Not applicable.

Not applicable.

Android Only

ISSUE DESCRIPTION	SUGGESTED FIX
Some SDKs require activities to be added to the manifest.xml file to run.	To fix this issue, refer to the integration documentation specific to the faulty network and make sure all its required activities are added to the manifest.xml file.

Missing Permissions

Android iOS Unity

Not applicable.

Not applicable.

Android Only

ISSUE DESCRIPTION	SUGGESTED FIX
Some SDKs require activities to be added to the manifest.xml file to run.	To fix this issue, refer to the integration documentation specific to the faulty network and make sure all its required activities are added to the manifest.xml file.

Testing Mediated Networks Instances

Your mediated networks are now successfully integrated and ready to work with the DT FairBid SDK. You can use the Test Suite to ensure you can request and show ads from them using the Instances configured in the Console, as described in the following procedure:

1. Tap the green square on the main screen.
2. Select the network you want to interact with from the list of networks.
3. Find the list of Instances that are used throughout your app:

• • Mediation Placements (waterfall Instances).
  • Programmatic Mediation Placements (bidding Instances). 

Waterfall Instances

This section lists all the waterfall Instances configured in the Console and used throughout your app.  Click Request and Show to request and show ads for these Instances.

Bidding Instances

This section lists all the bidding Instances configured in the Console and used throughout your app.

Placements

The Placements section of the Test Suite provides you with advanced capabilities. You can test that the placements you set up for the app in the Console perform as expected on the Placements section of the main screen to:

• Verify that the Placements Instances setup is applied correctly according to the setup in the Console.
• See the actual order of a Placement's Waterfall Instances, considering the CPM predicted values by the DT FairBid algorithm for Instances you chose to set Auto CPM in the Console.
• Request an ad for a Placement and see in real-time how the DT FairBid auction runs through the waterfall and bidding Instances and chooses a winner.

Verify Placement Instance Setup

To see the configured Placements for your app and verify each Placement setup:

• Tap the Placement section of the main screen (the blue square).
  The Placements configured for your app, including the Placement name, ID, and Type appears.

To see Placement and Instance setup:

1. Tap on a Placement.
2. Scroll down to see the bidding Instances set for the Placement.

For each Instance, the following information appears:

• Mediated Network name.
• The instance ID was received when creating the Instance on the mediated network's dashboard and set in the Console.
• Predicted CPM Value: If the Instance is set with an Auto CPM, the predicted value by DT FairBid's algorithm appears. If the Instance is set with Manual CPM, the Manual CPM value appears in bold, alongside the predicted value by FairBid's algorithm if this method was chosen. The Instance is positioned in the waterfall by the CPM values in bold.

Running the DT FairBid Auction

To run the DT FairBid auction and verify that the Placement delivers ads successfully and instances are being called as expected, tap the Request (Show for banner placements) button.

Once you tap the Request button, the DT FairBid auction starts running. First, look for an available ad from the Waterfall instances and then proceed to the bidders' auction, looking for a bid higher than the Placement floor price or the winning Waterfall instance price.

The Auction status appears at the bottom of the screen while the auction is running. Once the auction ends, the winning Instance appears. To view the winning ad, tap Show.

Waterfall Instance Responses

RESPONSE	DESCRIPTION
Requesting	Requesting an ad for the Instance.
Fill	Instance replied that an ad was available to display.
No Fill	The instance replied that no ad was available to display.
Instance Timeout	The Instance did not respond within the allotted time, but the SDK is still awaiting a response.
Failure	Any failure related to this Instance request: adapter failure, error, or capped.

Troubleshooting

Requesting an ad can sometimes fail for many reasons. Below is a list of possible problems to check that can help you get an ad: