Annex

Overview of all VisxEvents
Setting Keyword Targeting

Overview of VisxViewEmitter Events

The following VisxEvents are available for the React Native Module. For further information, please check the original VisxAdViewDelegates (iOS) and VisxCallbacks (Android) of the underlying native SDKs.

const CALLBACK_AD_SIZES = 'onAdSizeChange';
const CALLBACK_ON_AD_REQUEST_STARTED = 'onAdRequestStarted';
const CALLBACK_ON_AD_RESPONSE_RECEIVED = 'onAdResponseReceived';
const CALLBACK_ON_AD_LOADING_FINISHED = 'onAdLoadingFinished';
const CALLBACK_ON_AD_LOADING_FAILED = 'onAdLoadingFailed';
const CALLBACK_ON_AD_CLICKED = 'onAdClicked';
const CALLBACK_ON_AD_LEFT_APPLICATION = 'onAdLeftApplication';
const CALLBACK_ON_AD_INTERSTITIAL_WILL_BE_CLOSED = 'onInterstitialWillBeClosed';
const CALLBACK_ON_AD_INTERSTITIAL_CLOSED = 'onInterstitialClosed';
const CALLBACK_ON_AD_LANDING_PAGE_OPENED = 'onLandingPageOpened';
const CALLBACK_ON_AD_CLOSED = 'onAdClosed';
const CALLBACK_ON_AD_RESUME_APPLICATION = 'onAdResumeApplication';
const CALLBACK_ON_AD_VIEWABLE = 'onAdViewable';
const CALLBACK_ON_AD_EFFECT_CHANGE = 'onEffectChange';
const CALLBACK_ON_AD_VIDEO_FINISHED = 'onVideoFinished';

export const VISX_EVENT = {
  CALLBACK_AD_SIZES,
  CALLBACK_ON_AD_REQUEST_STARTED,
  CALLBACK_ON_AD_RESPONSE_RECEIVED,
  CALLBACK_ON_AD_LOADING_FINISHED,
  CALLBACK_ON_AD_LOADING_FAILED,
  CALLBACK_ON_AD_CLICKED,
  CALLBACK_ON_AD_LEFT_APPLICATION,
  CALLBACK_ON_AD_INTERSTITIAL_WILL_BE_CLOSED,
  CALLBACK_ON_AD_INTERSTITIAL_CLOSED,
  CALLBACK_ON_AD_LANDING_PAGE_OPENED,
  CALLBACK_ON_AD_CLOSED,
  CALLBACK_ON_AD_RESUME_APPLICATION,
  CALLBACK_ON_AD_VIEWABLE,
  CALLBACK_ON_AD_EFFECT_CHANGE,
  CALLBACK_ON_AD_VIDEO_FINISHED,
};

Setting Keyword Targeting

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

For these targetings to be effective, an individual agreement with the account manager is necessary so that they can also be implemented on the YOC backend configuration.

Key-values are structured as a JSON map. The first parameter represents the key, and the second parameter is the value. You can send the key values using the customParametersMap argument when initializing the visxAdManager.

  let customParametersMap = {
    key1: "value1",
    key2: "value2",
    key3: 3,
    key4: true
  };
//...
  <VisxBannerView
  style={{
    height: data,
    width: '100%',
    alignSelf: 'stretch',
    }}
    visxAdManager={{
      auid: '123456',
      appDomain: 'yoc.com',
      customParametersMap: customParametersMap
    }}
  />