# Integrating the Android SDK
This guide describes how to integrate the DT Exchange SDK into your Android project, which uses Maven Central for dependency management.
### Prerequisites
Android 4.4+ (API Level 19)
## Step 1: Integrating the SDK in your App
You can integrate the DT Exchange SDK using either Maven Central dependencies or a manual download.\
Select one of the following options:
* [Configuring Maven Central](#configuring-maven-central)
* [Manually Downloading the SDK](#manually-downloading-the-sdk)
### **Configuring Maven Central**
To add DT Maven repository and plugins to your Gradle build script:
1. Add the following to your app product-level `build.gradle` inside the repositories section.
2. At the root level `build.gradle` file, there are usually two repository sections - one for `buildscript` and one for `allprojects`. Add the entry in `allprojects`:
{% code title="Groovy" %}
```groovy
allprojects {
repositories {
// add this
mavenCentral()
}
// ...
}
```
{% endcode %}
3. Add the following to the project app-level `gradle` file inside the `dependencies` section.
{% code title="Groovy" %}
```groovy
dependencies {
// ...
implementation "com.fyber:marketplace-sdk:8.4.4"
// ...
}
```
{% endcode %}
### **Manually Downloading the SDK**
To download the DT Exchange Android SDK, click here:
Android DTX SDK 8.4.4
1. Log in to the [DT Console](https://console.fyber.com/).
2. Copy the following files from the `Fyber Marketplace SDK` folder to your `project libs` folder.
* For version 8.4.4:
`fyber-marketplace-8.4.4.aar`
* For version 8.1.0 and above (for Open Measurement support):
`omsdk-android-1.5.4-release.aar`
3. Add the following repositories and dependencies to the project `build.gradle` file:
{% code title="Java" %}
```java
repositories {
// ...
// Add a flat dir repository
flatDir {
dirs 'libs'
}
}
dependencies {
// Add the marketplace AAR libraries
implementation (name:"fyber-marketplace-8.4.4", ext:'aar')
// add open measurement sdk - fyber marketplace 8.1.0 and above
implementation (name:"omsdk-android-1.5.4-release", ext:'aar')
}
```
{% endcode %}
## Step 2: Integrating Google Play Services
DT recommends using Google Play Services to access your Google Advertising ID. This ID tracks your app's daily active users (DAU), and many ad campaigns require it. Without the ID, ad inventory is limited.
1. In the app-level `build.gradle` file, add the following dependencies:
{% code title="Groovy" %}
```groovy
dependencies {
implementation ('com.google.android.gms:play-services-base:Version#')
// use only the ads identifier library
implementation ('com.google.android.gms:play-services-ads-identifier:x.y.z')
// or implementation ('com.google.android.gms:play-services-ads:x.y.z')
}
```
{% endcode %}
2. For apps targeting API Level 31 (Android 12) or higher, declare the Google Play Services permission in the `AndroidManifest.xml` file.\
This step is required unless the app uses a recent Google Mobile Ads SDK version.
{% code title="XML" %}
```xml
```
{% endcode %}
For further information about Google Advertising ID Restrictions, read the following:
### Google Advertising ID Restrictions
Permission Required for Advertising ID
Google Advertising ID (GAID) is a unique string identifier that anonymously identifies a device for advertising purposes. Google Play Services provides this Advertising ID and enables users to opt out of personalized ads in apps or reset their identifier. When a user resets their identifier, it can connect to a previous identifier.
In 2021, Google announced a behavior change for apps targeting [Android 13](https://support.google.com/googleplay/android-developer/answer/6048248) (API Level 33) and higher, a `AD_ID` permission is required. For more information, see [Advertising ID](https://support.google.com/googleplay/android-developer/answer/6048248?hl=en).
To receive the Advertising ID, developers must add a new permission to the manifest file unless the app uses a recent version of the Google Mobile Ads SDK:
**XML**
{% code title="XML" %}
```xml
```
{% endcode %}
Recent versions of the Google Mobile Ads SDK (play-services-ads v20.4.0 and higher, or play-services-ads-identifier v17.1.0 and higher) include this permission. If the app uses these SDKs, the AD\_ID permission from the SDK's library manifest merges with your app's main manifest by default, making the Advertising ID available.
For more information about Google Play Services, see [Set Up Google Play Services](https://developers.google.com/android/guides/setup).
## Step 3: Adding Permissions - Android Manifest File
1. Add the following mandatory permission to your `AndroidManifest.xml` file:
{% code title="Java" %}
```java
```
{% endcode %}
2. To enhance targeting capabilities, add these permissions:
{% code title="Java" %}
```java
```
{% endcode %}
{% hint style="info" %}
The `ACCESS_NETWORK_STATE` permission differentiates WiFi from a cellular network.
{% endhint %}
## Step 4: Initializing the SDK
SDK initialization is mandatory because the DT SDK relies on the Console configuration for functionality. Without it, the SDK won't operate, and no ads will display. DT recommends performing this step during the app's initialization. Follow these steps to initialize the SDK.
### Google Play Families Ads API
To participate in the Google Play Families Ads program, run the following code to indicate if the user is a child:
{% code title="Java" %}
```java
InneractiveAdManager.currentAudienceIsAChild();
```
{% endcode %}
{% hint style="info" %}
Call this API once per app session before initializing the SDK. If the app doesn't contain the API, the user is not considered a child user by default.
{% endhint %}
After configuring your `AndroidManifest` file and preparing to request ads, initialize `InneractiveAdManager.initialize(context, <"appID">)`, and pass on your Activity or application context with the following code:
{% code title="Java" %}
```java
public class MainActivity extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
InneractiveAdManager.initialize(this, "Enter_Your_DT-Exchange_AppID");
}
@Override
protected void onDestroy() {
if (isFinishing()) {
//Optionally destroy the SDK after the activity has been destroyed
InneractiveAdManager.destroy();
}
}
}
```
{% endcode %}
{% hint style="info" %}
Call `InneractiveAdManager.destroy()` when you no longer need the library to display more ads, as this release any resources used by the SDK.
{% endhint %}
{% hint style="success" %}
If you intend to destroy the library from within your activity's `onDestroy` method, ensure that the activity has finished.\
To adjust or debug the logging library level, see [DT Logging on Android](https://docs.digitalturbine.com/dt-exchange/publishers/sdk-configuration/integrating-the-android-sdk/dt-logging-on-android).
{% endhint %}
#### Locating the App ID
To locate the App ID on the DT Console:
1. From the [DT Console](https://console.fyber.com/), go to **Monetization→App Management**.\
The **Apps dashboard** window appears.
2. Navigate to the required app.\
The App ID appears below the app's name.
