VIS.X® is Secondary

The secondary SDK is the SDK that the publisher wants to fall back to when there is no own demand provided by their primary ad server. This SDK is added to the app but not fully integrated and set up. Additionally, it provides some “mediation files”, that allow communication between the primary SDK and the secondary SDK.

  1. Adapter Overview
  2. Integration Guide: Google
  3. Integration Guide: Smart (Equativ)
  4. Integration Guide: Xandr
Adapter Overview

VIS.X® SDK delivers high-priced, high-impact ad formats powered by YOC. This works best in case VIS.X® has an exclusive placement in the app or at least can make the first call. In this scenario, VIS.X® SDK can deliver all its features and ad formats.

Using VIS.X® SDK as a secondary SDK requires the VIS.X® Ad Unit to conform with regular IAB banner formats of the primary SDK. Unfortunately, this does not work with all YOC Ad Products in all cases due to the limitation of the primary SDK.

Following the list of available YOC Ad Products per Mediation Partner.

Ad Product Google Xandr Smart
YOC Mystery Ad®
YOC Classic Banner
YOC Inline Video Ad
YOC Understitial Ad®
YOC Mystery Scroller®
YOC Branded Takeover
Integration Guide: Google

Mediation between VIS.X® SDK and Google Mobile Ads SDK is realized using the Google Yield Groups and CustomEvents in your Google Ad Manager UI.

Following the needed steps to integrate VIS.X® SDK with Google Mobile Ads SDK as your primary SDK.

1. Implement VIS.X® SDK in your app

To use mediation, the VIS.X® SDK needs to be added to your app as a dependency. There is no further configuration or activation required.

2. Implement VIS.X® SDK CustomEvents in your app

Next, the mediation class files need to be added to your project, which is require for the communication between Google Mobile Ads SDK and VIS.X® SDK.

For Android, the CustomEvents files are available here.

Make sure they be placed into the package com.yoc.visx.sdk.mediation.

For iOS, the CustomEvents files are available here.

3. Google Ad Manager configuration

Set up YOC as a Yield Partner within your Google Ad Manager and create a new Yield Group using CustomEvents. Please also check the Google documentation for the usage of “Custom Events”:

Following the needed configuration in the Custom Event setup:

Integration Type Field Description
Banner className (Android) com.yoc.visx.sdk.mediation.VISXCustomEventBannerGMA
Banner className (iOS) VISXCustomEventBannerGMA
Interstitial className (Android) com.yoc.visx.sdk.mediation.VISXCustomEventInterstitialGMA
Interstitial className (iOS) VISXCustomEventInterstitialGMA
Both Label Free of choice, depending on your reporting needs
Both Parameter key-value String, separated by semicolon
e.g. auid=123456;size=300x250

auid: Your VIS.X® Ad Unit, as provided by your YOC Account Manager
size: The main size of the Google Ads Container in the format <width>x<height>, e.g. 300x250 for a mobile rectangle
Integration Guide: Smart (Equativ)

Mediation between VIS.X® SDK and Smart Display SDK is realized using an insertion with a mediation template in your Smart Manage UI.

Following the needed steps to integrate VIS.X® SDK with Smart Display SDK as your primary SDK.

1. Implement VIS.X® SDK in your app

To use mediation, the VIS.X® SDK needs to be added to your app as a dependency. There is no further configuration or activation required.

2. Implement VIS.X® SDK CustomEvents in your app

Next, the mediation class files need to be added to your project, which is required for the communication between Google Mobile Ads SDK and VIS.X® SDK.

For Android, the CustomEvents files are available here.

Make sure they be placed into the package com.yoc.visx.sdk.mediation.

For iOS, the CustomEvents files are available here.

3. Smart Manage configuration

You can find instructions for Mediation in Smart in their documentation.

Following the needed configuration for a Smart insertion using the In-App Mediation Custom Adapter

Integration Type Field Description
Banner Adapter Class (Android) com.yoc.visx.sdk.mediation.VISXCustomEventBannerSAS
Baner Adapter Class (iOS) VISXCustomEventBannerSAS
Interstitial Adapter Class (Android) com.yoc.visx.sdk.mediation.VISXCustomEventInterstitialSAS
Interstitial Adapter Class (iOS) VISXCustomEventInterstitialSAS
Both Placement Info key-value String, separated by semicolon
e.g. auid=123456;size=300x250

auid: Your VIS.X® Ad Unit, as provided by your YOC Account Manager
size: The main size of the Google Ads Container in the format <width>x<height>, e.g. 300x250 for a mobile rectangle
Both Banner Width Default size in px
Both Banner Height Default size in px
Integration Guide: Xandr

Xandr Mediation is currently in a closed Beta and is not available to all clients. For more information about our mediation capabilities, contact your Xandr representative.

Following the needed steps to integrate VIS.X® SDK with Xandr Open SDK as your primary SDK.

1. Implement VIS.X® SDK in your app

To use mediation, the VIS.X® SDK needs to be added to your app as a dependency. There is no further configuration or activation required.

2. Implement VIS.X® SDK CustomEvents in your app

Next, the mediation class files need to be added to your project, which is required for the communication between Google Mobile Ads SDK and VIS.X® SDK.

For Android, the CustomEvents files are available here.

Make sure they are placed into the package com.yoc.visx.sdk.mediation.

For iOS, the CustomEvents files are available here.

3. Xandr’s UI configuration

Instructions on how to set up Custom Mobile Networks can be found in Xandr’s documentation for Android or iOS.

Following the needed configuration in the Custom Event setup:

Integration Type Field Description
Banner className (Android) com.yoc.visx.sdk.mediation.VISXCustomEventBannerXandr
Banner className (iOS) VISXCustomEventBannerXandr
Interstitial className (Android) com.yoc.visx.sdk.mediation.VISXCustomEventInterstitialXandr
Interstitial className (iOS) VISXCustomEventInterstitialXandr
Both Label Free of choice, depending on your reporting needs
Both Parameter key-value String, separated by semicolon
e.g. auid=123456;size=300x250

auid: Your VIS.X® Ad Unit, as provided by your YOC Account Manager
size: The main size of the Google Ads Container in the format <width>x<height>, e.g. 300x250 for a mobile rectangle