Digital Turbine

Use this guide to configure Digital Turbine bidding in CloudX.

Keep using the platform integration guides for SDK installation and ad loading:

• Android integration guide
• iOS integration guide

For platform-specific Digital Turbine adapter requirements, see:

• Android Digital Turbine Adapter page
• iOS Digital Turbine Adapter page

Overview

Use the following values:

• Digital Turbine App ID in CloudX app mapping
• Digital Turbine Placement ID in CloudX ad-unit mapping
• CloudX app_key and CloudX ad unit identifiers in app code

CloudX uses the bidder name Digital Turbine in the dashboard. If you see Fyber Marketplace branding in external network materials or the DT Console, it refers to the same network here.

Supported ad formats:

• Banner
• MREC
• Interstitial
• Rewarded
• Native

Step 1. Complete Digital Turbine-side setup

1. Sign in to the DT Console.
2. Add the app you want to monetize.
3. Copy the Digital Turbine App ID for that app.
4. Create placements for each format you want to use.
5. Copy each Placement ID.
6. Update your app-ads.txt file using Digital Turbine’s current requirements. Add Digital Turbine as a direct seller with your DT Publisher ID, and include Digital Turbine’s official reseller list.
7. Complete Digital Turbine review and payout setup before expecting live demand.

If this is a new Digital Turbine publisher account, your assigned Digital Turbine account manager must approve the account in the DT Console before inventory can go live. Existing Digital Turbine publishers do not need an additional activation step beyond creating the app and placements.

Official Digital Turbine references:

• Setting up your app in the DT Console
• app-ads.txt
• Setting up test devices

Step 2. Enable Digital Turbine in CloudX

Go to Bidders in the dashboard navigation, select Digital Turbine in the bidder list, and click Enable.

If Digital Turbine is disabled, CloudX will not request bids even if your mappings are correct.

After enabling, you can enter Digital Turbine App IDs and Placement IDs from this same page: search for an app, select it, and fill in the App ID plus Placement IDs for each eligible ad unit. You can also configure the same values from the app and ad-unit pages in the next steps.

Step 3. Configure your CloudX app

Go to Inventory -> Apps and create or open the app that matches your mobile application. Enter the Digital Turbine App ID for that app.

From this same app mapping view you can also enter Placement IDs for each of the app’s ad units — the same Placement ID values you can set from Bidders or from an individual ad-unit page.

Also copy the CloudX app_key from the app details page. Use the CloudX app_key in Android or iOS code.

Step 4. Configure CloudX ad units

Go to Inventory -> Ad units and add the mapping below for each eligible ad unit.

• Treat Digital Turbine Placement ID as required on both platforms.
• Match the placement to the correct CloudX ad-unit format.
• Use a separate placement for each CloudX ad unit or format as needed.

Step 5. Add Digital Turbine line items

Go to Line Items and create line items for bidder Digital Turbine on each CloudX ad unit where Digital Turbine should compete.

• Use bidder Digital Turbine
• Match the line item to the correct ad format
• Repeat the setup for each ad unit where Digital Turbine should bid

Step 6. Finish app integration

Use the CloudX platform guides and the Digital Turbine adapter pages:

• Android integration guide
• iOS integration guide
• Android Digital Turbine Adapter page
• iOS Digital Turbine Adapter page

In app code:

• Initialize CloudX with the CloudX app_key
• Load ads using CloudX ad unit identifiers
• Do not pass Digital Turbine App IDs or Placement IDs into app code
• For Interstitial and Rewarded ads, call show() only after the ad is ready

Step 7. Test and validate

1. Register your device as a CloudX test device: open the app page, click the ⋮ menu, select Test devices, add the device, and turn on Test Traffic. CloudX sends test=1 on outgoing Digital Turbine bid requests from registered CloudX test devices.
2. Optionally, register the same device as a test device in the DT Console. Digital Turbine returns test ads for devices registered there even when the bid request has test=0.
3. Build and run the app with the CloudX app_key and the correct CloudX ad unit identifiers.
4. Request an ad from each mapped ad unit.
5. Confirm that the ad loads and that Digital Turbine participates or wins where expected.

Troubleshooting

Digital Turbine is not bidding

Check the following first:

• Digital Turbine is enabled in the Bidders section
• The app has a valid Digital Turbine App ID
• The ad unit has a valid Digital Turbine Placement ID
• A Digital Turbine line item exists for the ad unit
• For new Digital Turbine publisher accounts, your Digital Turbine account manager has approved the account in the DT Console
• Your app-ads.txt file includes Digital Turbine’s required entries with your DT Publisher ID

Digital Turbine bids but the ad does not render

Check the following:

• Your app is using the CloudX app_key, not a Digital Turbine ID
• Your app is loading the intended CloudX ad unit
• The placement belongs to the correct Digital Turbine app and format
• The Digital Turbine adapter is installed and its platform requirements are complete

The placement looks correct but loads still fail

The mobile adapters require a valid Digital Turbine Placement ID at load time. Re-check the ad-unit-level placement mapping in CloudX.

Mapping Reference

The DT Publisher ID is used only for app-ads.txt. It is not a CloudX mapping field.