Advertisements

How to setup ads?

Ads works based on JW Ad schedules. Once you have setup, the client just needs to use the ad schedule ID, which will be entered in the feed during setting up the playlists.

Note that ads, for now, are only attached at the playlist level, unlike JWplayer platform, where it is attached at the player level.

Below is a step by step walkthrough:

  1. Setup ads as by selecting GoogleIMA as ad client.
  2. Add your adtags in there as preroll, midroll or Vmap, whatever applicable. VMAP is recommended over VAST.
  3. Save the ad schedule and grab the adid from there.
  4. Go to Zapp (Applicaster) platform and in the playlist data feed that you want to show ads, add the schedule id: ?adId=«ad_scheduled_id»
  5. Make sure you add the Google IMA plugin from the plugin gallery, if it wasn’t added before you’ll need to build the version again for the plugin to be enabled.

Notes

  • It’s not possible to have ad schedules on media level.

Ad Macros - General support

Many VAST servers use tag variables to optimize fill and provide more information on how ads are being viewed. Applicaster supports several variables that can be added to your VAST tag URL. Once an ad call is made by Applicaster, the variables will be replaced accordingly.

Applicaster uses Google Ad Manager SDKs.

  JW Macros Supported
General __player-height__ Yes
  __player-width__ Yes
  __timestamp__ Yes
  __random-number__ Yes
App __device-id__ Yes
  __platform__ Yes
  __app-bundle__ Yes
  __app-name__ Yes
Content __item-title__ Yes
  __item-mediaid__ Yes
  __item-file__ Yes
  __item-duration__ Yes
  __item-tags__ Yes
  __item-{custom}__ Yes

Please note that Applicaster supports other ad macros then JW Player player

Ad Macros - FreeWheel

Below are the ad macros supported for Freewheel ad server:

FW macros Type Supported
pvrn=(page_view_random) Dynamic No
vprn=(video_player_random) Dynamic No
vip=(end_user_ip_address) Dynamic No
(custom_video_asset_id) Dynamic __item-mediaid__
vrdu=(video_request_duration) Dynamic __item-duration__
_fw_did=(device_id) Dynamic __device-id__
_fw_vcid2=(unique_customer_id) Dynamic No
csid=(Platform) Dynamic Yes
slid=(slot_custom_id) Static Value Entered by publisher
mind=(slot_minimum_duration) Static Value Entered by publishttps://developer.roku.com/en-gb/docs/developer-program/advertising/roku-advertising-framework.md)her
maxd=(slot_maximum_duration) Static Value Entered by publisher

Does Applicaster integrate with Roku Advertising Framework (RAF)?

Applicaster uses RAF to serve advertisements on Roku.

Customers can have custom agreements with Roku, allowing them to serve their own VAST. Applicaster support both custom VMAP and VAST on Roku. Customers need to reach out to Roku for a custom agreement.