The purpose of this article is to guide publishers who want to use the DT FairBid SDK to load and display ads from myTarget via DT FairBid Mediation.

This is a six-step process:

  1. Create or login to your myTarget Account
  2. Create an app in myTarget
  3. Create a placement for your app
  4. Retrieve the parameters from the myTarget dashboard
  5. Insert the myTarget parameters into the DT Console
  6. Add the myTarget SDK to your integration

myTarget currently supports the following ad formats:

  • Banner
  • Interstitials
  • Rewarded Videos

Refer to myTarget for updates on supported ad formats.

Step 1: Create or Login to your myTarget Account

Click here, to create your myTarget account.

Step 2: Create an App in myTarget

Click here and follow the instructions to set-up your app in myTarget.

Step 3: Create a Placement for your App

Click here and follow the instructions to create a placement (slot_id) for your app.

myTarget banners configuration

myTarget allows you to configure the Banner placements (slot_ids) by device type: separately for phones and tablets. On the myTarget dashboard, these ad types are called respectively: Banner Ad Unit and Leaderboard Ad Unit. You cannot use the same Banner Ad placement (slot_id) for both phones and tablets because a placement (slot_id) configured for phone will not render on tablet and vice versa. You need to create them separately in myTarget dashboard.

  • Use Banner Ad Unit that has fixed size 320x50 for phone placement (slot_id).

  • Use Leaderboard Ad Unit that has fixed size of 728x90 for tablet (slot_id).

In the DT Console, in order to make a single DT FairBid Banner Placement universal for both phone and tablet we suggest configuring it with two myTarget instances: a Banner and a Leaderboard.

Step 4: Retrieve the Parameters from the myTarget Dashboard

To enable myTarget to work as an Ad Network on the DT FairBid Mediation platform, you must obtain the required parameter from your myTarget account and later insert it into the DT Console.

Set out below are the details of what parameter is required, how and where to obtain it.

myTarget Parameter Description
Access Token Allows you or third party services to access the statistics API of your account.  This token is unified for all apps and ad units.

Alternatively, watch and listen to the video below to find out how to obtain the required parameters:

Retrieving the Access Token

Click here for a short guide to find your personal account token. This token is universal for your entire account, all apps and ad units are included.

  1. Sign-in to your myTarget account with your user name and password here.
  2. From the top menu bar, click Profile
  3. On the left-side of the Profile page, click Access Tokens
  4. Click Show Token and the Access Token is displayed

For more information from myTarget, click here.

Now that you have obtained the required parameter, you can complete the configuration of myTarget in your DT Account. 

Step 5: Insert the myTarget parameters into the DT Console

To enter the parameters obtained from myTarget and insert them into the DT Console, follow these steps.

  1. Sign-in to your DT account
  2. Select your app from the App Management window

  3. On the App Management page, click Mediated Networks

  4. Select myTarget from the list

  5. The myTarget configuration window opens. Enter the myTarget app credentials and set the Instance name. Instance name should be distinguishable in case you have multiple myTarget Instances

  6. Click Save
  7. To complete the set up, you must associate the network instance that you just created to the relevant Placement set up on the DT Console. For a detailed guide click here

Step 6: Adding the myTarget SDK to your Integration

To add the myTarget SDK go to the Supported Networks page and follow the guide while selecting the Configuration for myTarget.

Android: minimum supported API version


Starting on version 5.18.0, myTarget's minimum supported API version is 21

Depending on your build requirements some actions might be required

If your app's minimum supported API version is below 21, you'll see the following compilation error

Manifest merger failed : uses-sdk:minSdkVersion 16 cannot be smaller than version 21 declared in library [] ~/.gradle/caches/transforms-3/510343f8c577f4ba829d8544359f788b/transformed/jetified-mytarget-sdk-5.18.0/AndroidManifest.xml as the library might be using APIs not available in 16
Suggestion: use a compatible library with a minSdk of at most 16,
or increase this project's minSdk version to at least 21,
or use tools:overrideLibrary="" to force usage (may lead to runtime failures)

If raising your applications's minimum supported version is not an option, nor is it removing myTarget from your integration, we suggest the following workaround:


<uses-sdk tools:overrideLibrary=""/>

This AndroidManifest will override any conflicting Manifest configuration coming from myTarget with the ones defined in your application (that includes minimum supported API version).

Despite being the suggested solution (from both DT and Gradle) this comes with potentially side effects and should be used wisely.


When running on devices below API 21, the SDK will proactively not start myTarget SDK and will therefore always return no fills. 

SDK Bidding

myTarget bidding is currently part of a closed beta. If you are interested in enabling it, contact your DT account manger.

To activate SDK Bidding with myTarget, contact your myTarget account manager.

For more details on myTarget In-App Bidding, click here.

Back to Top ⇧