Playables, Endcards, and More

The following article contains the overall Creative Requirements that will ensure your content is following Vungle standards depending on your creative type.

Please review how to customise your creative experience with events here prior to this article. 

Building Playables

A playable is usually an ad experience that showcases your app or game. This allows users to preview and play briefly with the ad prior to installing it. They usually contain a CTA (call-to-action) at the end of the playable experience. More info here.

  • Please provide an ad.html

  • "download" event must be present. Usually will be triggered on CTA click or end-screen interaction

  • "complete" event must be present. This event guarantees calling download automatically after a good portion of the ad has been played. This will ensure users engage with the ad prior to take them to the store for download. Usually will be triggered on 3+ interactions automatically

  •  "download" and "complete" events should never trigger together. Avoid "complete" being tied to a click or triggered automatically or any interaction tied to "download" already. This may trigger a double click/double call to the store causing a failed user experience from our internal teams

  • These kind of units will usually be served in any form to adapt to Publisher settings

Building Endcards

An endcard is usually an ad experience that showcases your app or game in a static or shorter manner. They are usually brief visual ads displayed to users at the end of a video ad and contain a short preview of the app. They can be static images or short preview presented with a CTA.

The experience is a non-playable and the only option for the user is to download it to play.

  • Please provide an ad.html
  • "download" event must be present. Usually will be triggered on CTA click or as a fullscreen interaction
  • "complete" event should NOT be present. This event guarantees calling "download" automatically after a good portion of the ad has been played. Since the experience is non-playable, this mechanism is not needed and "download" is the only event required
  • The experience will be categorised as a fullscreen clickable (FSC) based on its functionality
  • These kind of units will be usually served as aggressive units when exposed to Publisher settings

Building fullscreen clickable (FSC)

A FSC is usually an ad experience that showcases your app or game in a static or shorter manner.

They are almost the same as endcards but the experience will take you to the store on the 1st/2nd interaction. They can look like playables but they react as an endcard. The experience is a non-playable and will be categorised as FSC.

  • Please provide an ad.html
  • "download" event must be present. Usually will be triggered on fullscreen interaction on 1st/2nd tap
  • "complete" event should NOT be present. Since the experience is a non-playable, this mechanism is not needed and "download" is the only event required
  • The experience will be categorised as a fullscreen clickable (FSC) based on its functionality
  • These kind of units will usually be served as aggressive units when exposed to Publisher settings
Powered by Creativity Driven by Performance Sign Up Here

Questions?

Need further assistance, feel free to reach out to us, we’re here to help!

Was this article helpful?