Ad Revenue Integration


Kochava enables marketers to track revenue derived from in-app ad monetization. Using our SDK or S2S integration, an Ad View* event can be sent each time an ad impression is served, along with appropriate meta-data detailed below by monetization partner.

 

BEST PRACTICE: The Ad View event should not be used to send clicks or other ad activity. Other ad activity can be sent using your own custom events.

 

The marketer will also need to enter credentials for their monetization partner within the Partner Configuration dashboard. This allows Kochava to connect with your monetization partner’s API and pull relevant revenue data which is then linked to the ad impressions served in your app.

Depending on your monetization partner, deeper integrations may be available, which support advanced capabilities (i.e. restated ad revenue). Please check with your Client Success Manager or contact support@kochava.com for details.

NOTE: After the Ad Revenue integration process is complete, data associated Ad Revenue may be access through the Kochava Query. For more information, refer to our Query Reference support documentation.


SDK Integrations

The SDK 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 ad revenue 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:

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:

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:

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:

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:

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

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 —


Fyber

The ad_network_name parameter must be provided with every event with the value of Fyber.

 

  • Banner —

     

    Interstitial —

     

    Reward Video —

     

    Offerwall —

  • Banner —

     

    Interstitial —

     

    Reward Video —

     

    Offerwall —


ironSource:

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:

MoPub provides publishers with revenue information associated with each impression, as well as information about which demand source served the ad. Publishers have full flexibility to expand event data with their own data and pass it to Kochava.

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

 

  • Direct JSON Version —

     

    Manually Build Event —

  • Direct JSON Standard Impression —

     

    Direct JSON Rewarded Video —

     

    Manually Built Standard Impression —

     

    Manually Built Rewarded Video —

  • Direct JSON Version —

     

    Manually Build Event —


Tapjoy:

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:

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.


S2S Integrations

The S2S Integration provides an example with all possible values for ad_network_name with additional information to assist customers with the values that should be sent to Kochava.

 

BEST PRACTICE: Event name MUST be ad view. In addition, ad_network_name MUST be present within the event_data key value pairs.


Network Names:

ad_network_name possible values are case insensitive (SELECT ltv_network_name FROM kochava.cpi_networks WHERE ltv_network_name != "";)

  • AdMob
  • Appodeal
  • Chartboost
  • Fyber
  • InMobi
  • ironSource
  • MoPub

Event Data:

The below table provides the mapping of Event data to the corresponding columns in the Query Table.

 

TIP: Populate values in order to find the correct revenue in network_revenue table.

TIP: Search network_revenue table in Kochava Query for examples of what network specific data looks like.

 

Event Data Query Table Columns
device_type device_type
placement placement
ad_type type
ad_campaign_id network_campaign_id
ad_campaign_name network_campaign_name
ad_size ad_size
ad_group_name group_name
ad_group_id group_id
country_code country_code

S2S Event Example: