Advanced Ad Events

Overview

Use Ad events to track when the game loads and players interact with each ad type and placement.

This event type can be used to calculate metrics such as how many players watched each ad placement type or how many ad failures they experienced.

Available Events

Reward Video

• reward_video_opportunity

• reward_video_tryshow

• reward_video_show

• reward_video_show_fail

• reward_video_clicked

• reward_video_end

• reward_video_collect

• reward_video_load

• reward_video_load_fail

• reward_video_revenue_paid

Interstitial

• interstitial_tryshow

• interstitial_show

• interstitial_clicked

• interstitial_end

• interstitial_show_fail

• interstitial_load_fail

• interstitial_load

• interstitial_revenue_paid

Banner

• banner_show

• banner_revenue_paid

Critical Parameters

• Required

  • placement: placement of the ad. For interstitials, the value should help identify the timing/stage/state where the ad is triggered

• Optional

  • reward: only applies to the reward_video_collect event. It’s an optional parameter, but we highly recommend including it to inform any sink and source data and analysis.

Example

Games that have any one of the ad types (e.g. interstitial, RV) are applicable.

Implementation

Ad Events Flow Chart

Example: Rewarded Video Event Order

1. reward_video_load —> Ad SDK loaded a video

2. reward_video_load_fail —> Ad SDK failed to load a video

3. reward_video_show —> Ad is requested to be shown to the player

4. reward_video_start —> Ads SDK started the video

5. reward_video_show_fail —> The video failed to display to the player

6. reward_video_clicked —> Player clicked the video

7. reward_video_hide —> Player chose to hide the video

8. reward_video_end —> Video reached the end

9. reward_video_collect —> Player collected a reward for watching the video

10. reward_video_revenue_paid —> The revenue for the ad was received. The position of this in the event order is not guaranteed.

The other ad types follow the same convention. Unless you are troubleshooting, the *_show, *_end, and *_collect events are probably the most important events to add to your game.