Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Video delivery method: Revive Adserver supports video ads that are delivered be either RTMP (streaming) and HTTP (progressive).
    • Streaming protocols such as RTMP are generally considered to offer users better video playback options (such as fast-forwarding and seeking) compared with non-streaming protocols such as progressive HTTP.
    • However, these video playback options may not be particularly relevant to the display of video ads - for example, is the ability to fast-forward through the ad important?

    • As a result, the primary consideration for the video delivery method is more likely to be the protocols supported by the hosting location of the video ad, which needs to be external to Revive Adserver.
  • RTMP server URL: In the event that the RTMP protocol is selected, the URL of the RTMP server host is required separately from the video ad's filename.
    • (warning) Remember to use https:// as the protocol if the inline video banner needs to be delivered over SSL/TLS.
  • Video filename: In the event that the RTMP protocol is selected, the filename of the video ad is required separately from the URL of the RTMP server host.
  • Video URL: In the event that the HTTP protocol is selected, the URL of the video ad is required (i.e. both the URL of the host, and the filename, in one URL).
    • (warning) Remember to use https:// as the protocol if the inline video banner needs to be delivered over SSL/TLS.
  • Video type: The type of the video ad. Revive Adserver supports FLVMP4 and WEBM videos.
  • Video duration in seconds: The length of the video, in seconds.
  • Destination URL: The complete URL that the user should be redirected to if they click on the video ad during playback.
    • (warning) Remember to include http:// (or https:// if required) at the start of the destination URL.


Info

EXAMPLES OF VIDEO ADS THAT USERS CAN TEST WITH TO BE DOCUMENTED HERE

...