# Android > Custom mediation adapter

Source: https://help-display-sdk.equativ.com/android/custommediationadapters.html

This page is focused on how to create a custom mediation adapter on your own.
For more general information about the mediation and the mediation adapters provided out of the box, please check the [Supported Ad Networks article](https://help-display-sdk.equativ.com/mediation/primarysdk/supportedadnetworks.html.md).

---

## Overview

The **Equativ Display SDK** can not use a third-party SDK directly.

It must instead rely on an intermediate component called an __mediation adapter__ that will be responsible of retrieving an ad from the
third-party SDK. This adapter will then forward the ad to the **Equativ Display SDK** via its __mediation adapter listener__.

## Mediation adapter interfaces

Creating a custom adapter is done by implementing an interface depending on the type of ad you want to deliver:

- [`SASMediationBannerAdapter`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-banner-adapter/index.html) for banner ad format,
- [`SASMediationInterstitialAdapter`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-interstitial-adapter/index.html) for interstitial ad format.

Please follow the API documentation to know which APIs must be implemented for each mediation adapter interface.

## Mediation adapter listener interfaces

When implementing an __mediation adapter__, you will receive an instance of a specific __mediation adapter listener__ interface through the
loading API of your __mediation adapter__.

This listener object acts as a callback that will notify the **Equativ Display SDK** of the third-party SDK lifecycle events.

You __must__ call these methods depending on the event occuring on the third-party SDK side. Failing to do so, therefore failing to notify **Equativ Display SDK**, might break either the mediation
waterfall, the impression counting or any other kind of tracking.

Please check the API documentation to have more information about when to call these __mediation adapter listener__ methods, depending on the ad format of your __mediation adapter__:

- [`SASMediationBannerAdapter.MediationBannerAdapterListener`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-banner-adapter/-mediation-banner-adapter-listener/index.html)
    is the listener to notify when implementing the [`SASMediationBannerAdapter`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-banner-adapter/index.html) interface.
- [`SASMediationInterstitialAdapter.MediationInterstitialAdapterListener`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-interstitial-adapter/-mediation-interstitial-adapter-listener/index.html)
    is the listener to notify when implementing the [`SASMediationInterstitialAdapter`](https://help-display-sdk.equativ.com/android/API/-display%20-s-d-k/com.equativ.displaysdk.mediation/-s-a-s-mediation-interstitial-adapter/index.html) interface.

## Set up your insertion on _Equativ Management Platform (EMP)_

Please check the ["Integrate new ad network"](https://help-display-sdk.equativ.com/mediation/primarysdk/integratenewadnetwork.html.md) article to learn more about this part.

## Implementation samples

__Equativ__ provides open source adapters for some common third-party SDKs. You can use them as implementation samples for your own custom adapter.

[Open source mediation adapters](https://github.com/smartadserver/equativ-display-sdk-mediation-adapters-android)