Ad LTV Integration


Kochava’s True LTV solution enables marketers to visualize True LTV for their users by collecting all the necessary ad-serving meta data and passing it to our servers via your SDK integration or S2S integration. Data is passed to Kochava as a named event of “Ad View” in the SDK/S2S, along with app credentials supplied by the marketer, which allows Kochava to collide the real-time ad revenue associated to the impression for each integrated mediation/ad network.

All Ad LTV events use the “Ad View” event type and calculations are based only on ad views (impressions). Clicks and other activity are not used and should not be sent using the “Ad View” event type. Other ad activity can be measured using your own custom events.


Integrations

The integration samples make use of the callback delegates provided by the specific Ad Network and include parameters that are readily available. Some implementations of an Ad Network may have additional data that is not listed by the integration document that could improve LTV accuracy. If you wish to send additional parameters beyond what is listed contact your Client Success Team.

Once you are aware an ad has been served (either from having initiated it, or having been notified that it was served), construct and send an “Ad View” type event as described in the samples below.

If a Mediation or Ad Network that Kochava does not have an existing integration listed is desired to be utilized, please contact with your information Integrations@kochava.com.


AdColony Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “AdColony”.

 

  • Interstitial —

     

    Rewarded Video —

     

    Native —

  • Interstitial —

     

    Rewarded Video —

     

    Native —


AdMob Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “AdMob”.

 

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Native Express —

     

    Native Advanced —

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Native Express —

     

    Native Advanced —

     


AppLovin Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “AppLovin”.

 

  • Banner —

    Both Banner and MRec formats are considered banner ads of different sizes. Ensure the size is set to the defined value for each variant.

     

    MRec —

    Both Banner and MRec formats are considered banner ads of different sizes. Ensure the size is set to the defined value for each variant.

     

    Interstitial —

     

    Rewarded Video —

     

    Native —

  • Banner —

    Both Banner and MRec formats are considered banner ads of different sizes. Ensure the size is set to the defined value for each variant.

    NOTE: AppLovin has deprecated Banners and MRecs, indicating in code-level warnings that they will be removed in a future version of the SDK.

     

    MRec —

    Both Banner and MRec formats are considered banner ads of different sizes. Ensure the size is set to the defined value for each variant.

    NOTE: AppLovin has deprecated Banners and MRecs, indicating in code-level warnings that they will be removed in a future version of the SDK.

     

    Interstitial —

     

    Rewarded Video —

     

    Native —


Appodeal Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “Appodeal”.

Ad Placements can optionally be passed when showing an ad and will increase the accuracy of impression tracking. If you are passing in a placement when showing an ad also include it with the Kochava Event.

  • Banner —

     

    Banner (MREC) —

    MRec is a specific size of banner ad. Specify the size when using an MRec style ad to distinguish it from other banner ads.

     

    Native Ad —

     

    Interstitial —

    This includes all formats of Interstitial ads including static, rich, and video.

     

    Rewarded Video —

    This also includes NON_SKIPPABLE_VIDEO as Appodeal defines it as an alias of the Rewarded Video format.

  • Banner —

     

    Banner (MREC) —

    MRec is a specific size of banner ad. Specify the size when using an MRec style ad to distinguish it from other banner ads.

     

    Native Ad —

     

    Interstitial —

    This includes all formats of Interstitial ads including static, rich, and video.

     

    Rewarded Video —

    This also includes NON_SKIPPABLE_VIDEO as Appodeal defines it as an alias of the Rewarded Video format.


Chartboost Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “Chartboost”.

 

  • Interstitial and Video Interstitial —

    Chartboost does not break out video interstitial from a static interstitial with its callbacks. Both are sent under the same type. If you know for sure that an ad is a video interstitial you may send the type as “Video Interstitial” to improve calculation accuracy.

     

    Rewarded Video —

     

    In Play —

    In Play ads are managed by you. It is your responsibility to send this event after calling show on the inPlay ad.

  • Interstitial and Video Interstitial —

    Chartboost does not break out video interstitial from a static interstitial with its callbacks. Both are sent under the same type. If you know for sure that an ad is a video interstitial you may send the type as “Video Interstitial” to improve calculation accuracy.

     

    Rewarded Video —

     

    In Play —

    In Play ads are managed by you. It is your responsibility to send this event after calling show on the inPlay ad.


Facebook Audience Network Ad LTV Integration

The “ad_network_name” parameter must be provided with every event with the value of “FacebookAN”.

 

  • Banner —

     

    Interstitial —

     

    Native —

     

    Rewarded Video —

     

    Instream —

  • Banner —

     

    Interstitial —

     

    Native —

     

    Rewarded Video —

     

    Instream —


ironSource Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “ironSource”.

 

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Offerwall —

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Offerwall —


MoPub Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “MoPub”.

 

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Native —

    Includes both static and video native ads.

  • Banner —

     

    Interstitial —

     

    Rewarded Video —

     

    Native —

    Includes both static and video native ads.


Tapjoy Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “Tapjoy”.

 

  • Interstitial, Rewarded Video, and Offerwall —

    All ad types occur with a single delegate callback. It is up to you to keep track of what type of ad is being shown and to set the type correctly. Supported ad types are “Interstitial”, “Rewarded Video”, and “Offerwall”.

  • Interstitial, Rewarded Video, and Offerwall —

    All ad types occur with a single delegate callback. It is up to you to keep track of what type of ad is being shown and to set the type correctly. Supported ad types are “Interstitial”, “Rewarded Video”, and “Offerwall”.


UnityAds Ad LTV Integration:

The “ad_network_name” parameter must be provided with every event with the value of “UnityAds”.

 

  • Interstitial and Rewarded Video —

    Both types of ads use the same callback. You must keep track of what ad was called to be shown to ensure the correct type is sent to Kochava.

  • Interstitial and Rewarded Video —

    Both types of ads use the same callback. You must keep track of what ad was called to be shown to ensure the correct type is sent to Kochava.

 
 

Last Modified: Jul 3, 2018 at 3:24 pm