DSP Test App

The Digital Turbine Exchange Test App is a self-service test tool that allows you to test your integration and creatives on DT Exchange. This tool enables you to validate components such as the close button, video skip button, countdown timer, video skipability standards, and close button delays.

To validate ads on the DT Demand Test App, you must have access to the DT self-service web dashboard and the DT Demand Web Tool. Once you have the credentials, configure the Web Tool and the Demand Test App. The testing process includes the following steps:

• Step 1: Download the Demand Test App.

• Step 2: Upload Ads using the Creative Tester.

• Step 3: Test the Ad on your device.

The following Ad Formats are available for testing:

• Banner

• Interstitial

• Rewarded

• Native (Android only)

  • Native - Feed

  • Native - Dialog

  • Native - FS

Ad Testing Methods

The Demand Test App supports two testing methods:

• Ad Lifecycle: Tests end-to-end live integrations. DT Exchange sends a bid request to your servers and guarantees the winning of your bid response. The ad you chose to serve is displayed in the test app for you to validate.

• Creative Tester: Tests a mock bid response that you can upload in advance using the web tool. You can test the uploaded ad in the test app.

You can access only the Creative Tester tool if your integration is not yet live. Once your OpenRTB integration goes live, you can use the Ad Lifecycle tool.

The following table describes the features of each testing method.

FEATURE	CREATIVE TESTER	AD LIFECYCLE
Review the bid request parameters, including custom extensions. For more details about the bid request structure, see DT's OpenRTB Specs.
Test specific creatives before launching a new integration or a new creative format.
Check server-to-server notifications, such as nurl, burl, and lurl.
Check ad functionality, including VAST quartile tracking, impression tracking, click tracking, attribution tracking, load-time performance, MRAID actions, VAST waterfall for media files and companion ads, etc.
Confirm proper rendering, resizing, and centering of webview margins.

Step 1: Download the Demand Test App

To download the Demand Test App:

1. Log in to the Demand Web Tool with your user credentials.

2. Click App Links. The iOS and Android links appear.

1. Download and install the required platform on your device.

Step 2: Upload Ads Using the Creative Tester

To test an ad using Ad Lifecycle only, continue to Step 3.

To upload ads and test them on the Demand Test App:

1. In the Demand Web Tool, click CREATIVE TESTER→+ CREATE to add a new creative.

1. In the description field, add a description for your creative.

2. To add openRTB parameters, click the + (plus) icon.

3. In the Key and Value fields, enter DT-supported parameters described in DT's OpenRTB Specs.

4. In the markup field, paste the HTML or VAST ad markup, similar to the content of the adm field in an Open RTB response to your ad markup.

5. Click SAVE. A QR code appears on the Web Tool.

Step 3: Test the Ad on Your Device

To test ads:

1. In the Demand Web Tool, access the QR code for the test ad:

2. To test an Ad Lifecycle, click Ad Lifecycle. The QR Code Appears.

3. To test a Creative, navigate to Creative→Creative Tester and click Show for the required creative. The QR Code Appears.

4. To test the app on your device, open the Demand Test App and follow the instructions in the appropriate tab below.

Android

To test ads on an Android device:

1. Tap the QR code icon, then scan the QR code in the Web Tool.

2. Select the required ad type from the dropdown list.

1. To test Banner ads, tap Load Banner.

2. To test Interstitial ads, tap Load Interstitial, then Show Interstitial.

3. To test Rewarded ads, tap Load Rewarded, then Show Rewarded.

4. To test Native ads, select the required Native Ad, tap Generate Token, tap Load Native Ad, and then tap Show Native Ad.

Native ads are only available through SDK Bidding mediation. In SDK Bidding, DT Exchange must first generate a token for the Mediation SDK to use when identifying the request to the server.

For more information, see Generating a Token.

To inspect and remove devices with Chrome Developer Tools, see Chrome DevTools: Devices for more information.

iOS