Advertising and Ad Networks

See Monetization - Configuring the Player Advertising Settings in the Universal Studio for information about advertising using the Universal Studio players.

Overview of Advertising with Kaltura

Kaltura’s monetization features contain a comprehensive set of advertising tools, pay-per–view, subscription models, and built-in reports that let you optimize your strategy based on viewer behavior.

You can target viewers with ads on live videos or VOD, and across multiple devices such as mobile, PC and set-top-box. With support for a wide range of video ad formats (including all major IAB standards), and integrated plugins for video ad networks, such as Google DoubleClick DART, FreeWheel,  and others, managing you can optimize your monetization.

The Kaltura Player supports HTML video ads and overlay ads. The Kaltura Player is VAST-compliant, supports custom SWFs, and has plugins for FreeWheel and Doubleclick.

Player Branding

Players can be designed and skinned to match any brand and used for your own brand or for advertisers on your site. See Configure the Player Features.

Connecting with an Ad Server

Integrating your Ad Server with the KMC is a one-time activity performed when you initially set up video advertising. The ad server must be VAST compliant or available as a Kaltura plugin. You may also create a custom swf for the Kaltura Player to support.

After you have selected an ad server and set up an account with that ad server, you integrate the ad server with the KMC by establishing a connection between that ad server and KMC. After the connection is established, all ad requests generated by the Kaltura Dynamic Player are in a format which the ad server expects, allowing seamless communication between the Kaltura Player and the ad server.

The Digital Video Ad Serving Template (VAST) is an industry standard for the XML response from an ad server. Most of the leading Ad Servers and Ad Networks are VAST compliant, and support IAB standard (VAST 1.0 / VAST 2.0 and VAST 3.0).

Popular ad servers include DoubleClick, Dart For Publisher (DFP), Microsoft Atlas, OpenX, ScanScout.  To see the full list of servers and networks that comply with VAST, refer to the IAB website:

In general, ads, tracking, scheduling, and other parameters, are configured on the ad server side. With VAST, other parameters need to be configured through the KMC or Kaltura Player. Ad parameters are configured through the Studio tab in the KMC. 

Kaltura Player and Ad Plugins

Kaltura partners can create a custom .swf file to stream ads from their own ad server to the Kaltura Player. The.swf file acts as an ad plugin. The configured key-value pairs must be defined to play the relevant ads.

You must subscribe to an ad server and configure the ads on the ad server side.

Supported Ad Servers

All VAST compliant ad servers are supported. For more information see Kaltura’s Generic Ads Player Plugin for VAST.pdf.

The Kaltura Player supports all VAST compliant ad servers and the following ad plugins:

Ad Terminology

Ad tracking – the ability to define which/if ads play based on specific metadata.

Overlay – an ad that appears as an image (usually with text) over a video, while the video is playing.

Video ad– a banner ad that accompanies the ad that plays over the video player – this can either be in the list area of the playlist or somewhere else on the HTML page.

Ad Tag URL – a URL that is XML that contains all the information about the ad(s) that should be displayed. VAST works with an ad tag URL system. The XML needs to conform to VAST standard to be considered “VAST-compatible” and must contain the proper tags.

The following is an example of a VAST ad tag URL:

To see the example, insert the following URL into your browser.

Ad Cue Points – time-based points on an entry that can be used to view advertisements on the Kaltura Video Editing Tools Timeline.

Creating Kaltura Video Ads

The following types of ads may be configured:

Configuring VAST Ads

  • Add the VAST tag to an entry
  • Configure the Player

To configure VAST Ads on an entry

  1. Go to the Content tab and click on the Entries tab.
  2. Click on the entry and select the 'Advertisements' tab.
  3. Click Manage Advertisements'
  4. Click the '+' button in the player
  5. Select 'Video Ad'.
  6. Select. Add Name and enter the name for your ad.
  7. Add the ad URL: for example:
  8. Click 'Add'.
  9. Click Save'.

If you want to add an additional URL, you will need to change the number in 'correlator=' (in the end of the link)

To configure a player to display an ad

  1. Go to the Studio tab (near Content tab)
  2. Click 'Add New Player'
  3. Enter the player name.
  4. Go to the Monetization section $.
  5. Check the 'DoubleClick' checkbox and expand the 'DoubleClick' option.
  6. Click on the 'Vast Trafficking' tab (towards the bottom of the available Double Click options).
  7. Check the 'Track cue points' checkbox.
  8. Click 'Save Player Settings'.

To playback the video with the ads

  1. Go to the Content tab and select Entries.
  2. Select Share and Embed from the Actions menu of the entry you set ads for.
  3. In the 'Select Player' dropdown, choose the player you created to display ads.
  4. Click Play.
    The ads you set at the configured cue points in the editor are played at their sets times.


Here are a few helpful steps to configure advertising:

For VAST Ads

Check that you have a working ad tag URL. Be certain that VAST 3.0, 2.0., 1.0 are also supported for the media file content.

<VAST xmlns:xsi="" xsi:noNamespaceSchemaLocation="vast.xsd" version="2.0">


<MediaFile id="GDFP" delivery="progressive" width="1280" height="720" type="video/mp4" bitrate="450" scalable="true" maintainAspectRatio="true">
  • If the URL is not a VAST XML or if the media file does not play properly, create a working VAST XML with a working media file on your ad server.
  • If the VAST ad tag URL looks valid and the media file plays properly, the next step is to go to Fiddler or Inspect Element. (Debugger) The first important thing to look for here is to make sure that the crossdomain is working properly. Here is a working Fiddler response:
  • If the Crossdomain request/response is red or has some abnormal result like 404, you will need to enable your domain’s crossdomain to allow Kaltura to access it. Here is Kaltura’s crossdomain.xml, which can be provided as an example of a proper crossdomain.xml : .
  • The next steps are to make sure that the ad is properly being called via Fiddler:




In This Article
Was this article helpful?
Thank you for your feedback!