Following you will find a list of features the VIS.X® SDK is offering and its support for each platform.

1. MRAID 3.0
2. Mediation
3. Prefetching
4. Remote Configuration & Logging
5. In-App Bidding
6. Targeting
7. Alternative Identitifier / First Party IDs
8. Viewability (Open Measurement SDK)

MRAID 3.0

Mobile Rich Media Ad Interface Definitions (MRAID) is the common API for mobile rich-media ads that run in mobile apps. MRAID provides a way for ad developers to design interactive ads that work in MRAID-compliant systems, using common code. The VIS.X® SDK is MRAID 3.0 compliant. However, some features have been limited to avoid unnecessary app permissions, and also to improve security for publishers and app users.

Unsupported Methods

• createCalendarEvent
• storePicture
• initVpaid
• useCustomClose (VIS.X® SDK will enforce its own close button for all interstitials)

Supported Methods, but restricted

• expand, getExpandProperties, setExpandProperties
• resize, getResizeProperties, setResizeProperties
• playVideo
• getLocation

Mediation

The VIS.X® SDK offers general support for mediation, either as a primary SDK or as a secondary SDK along the waterfall. We are offering preconfigured mediation adapters for Google, Equativ and Xandr, as well as open mediation files to freely customize based on your needs and preferred partner. See here for instructions.

Prefetching

Depending on the integration, the VIS.X® SDK supports (limited) prefetch, by splitting the ad call and ad rendering process. Per default, we allow a maximum expiration timeout of 15 minutes for banners and 30 minutes for interstitials. If an ad is rendered after the expiration timeout, the impressions become invalid. In this case, the SDK will actively ask VIS.X® for a new, unexpired ad to rescue the impression.

Remote Configuration & Logging

Remote Configuration was introduced to provide publishers with additional convenience in setting up, commissioning and maintaining the VIS.X® SDK in the published app without requiring another release for every change. It allows ad hoc changes of settings and configurations from the backend, but also A/B testing. Remote Logging, which is enabled via Remote Configuration, allows detailed on-demand troubleshooting and diagnosis, with data scarcity in mind. Remote Configuration is an optional feature and is explained as part of the regular integration.

In-App Bidding

The VIS.X® SDK can be configured to be used in a non-prebid header bidding scenario on demand. This allows you to receive pricing and currency from an ad request and make an educated decision, on if and when to display the ad. Together with prefetching, it can be used to easily optimize your fill rate and in-app monetization. The VIS.X® SDK can also work on a custom Prebid Mobile integration. Reach out to your Account Manager at YOC and we will guide you through the process.

Targeting

VIS.X® SDK allows setting individual key-value targeting for your placements. This can be useful, among other things, if contextually different blocklists or floor prices are used for the same ad unit (e.g. channel targeting).

Alternative Identitifier / First Party IDs

The VIS.X® SDK may use the IDFA (iOS) or GAID (Android) as an advertising identifier. In such cases, the user must consent to the tracking via App Tracking Transparency (ATT) on iOS (opt-in) or Google Advertising settings on Android (opt-out) respectively, and the usage of this data via a certified TCF 2.0 compliant CMP. As an app publisher and data controller, you are in charge to declare the usage of personalized data and ask for consent accordingly.

In cases where the user of the app is not consenting to the usage of IDFA/GAID, but generally to the usage of an identifier via the CF 2.0 consent, the VIS.X® SDK will default to alternative identifiers, such as the IDFV for iOS or App Set ID, which can be shared across all your owned and operated apps.

The VIS.X® SDK also allows you to bring your first-party data to the VIS.X® platform as pseudonymized IDs to be shared within your apps. The identifier must be delivered in UUID format (the SDK will enforce this) to ensure no natural personal data will be brought to the platform in clear tex, alternatively you bring your ID5 data to our platform. The requirement of asking for consent under the TCF 2.0 remains as in such cases.

No personalized data will be processed via the VIS.X® Platform without a valid TCF 2.0 signal.

Viewability (Open Measurement SDK)

The VIS.X® SDK offers viewability tracking under the Media Ratings Council (MRC) definition of a “viewable ad impression”. The tracking of the viewable area itself is aligned with MRAIDs definition of “exposure percentage” and the SDK will also consider obstructing UI elements overlaying the ad, regardless of its opacity.

Also, the VIS.X® SDK is shipped with the IAB Open Measurement SDK (OMSDK), for an independent tracking verification partner to validate our numbers. Our partner name is “Yoc”, the latest version we support is OMSDK 1.4.13.