Versions Compared

Key

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

This article navigates an account administrator through the session rules in Revma.com and explains the different uses.

Table of Contents

Session Rules Overview

The Session Rules refer to an IP-based filtering method, that allows an account administrator to route the listeners through a certain stream or a group of streams, with various actions being applied.

Some examples of how the rules can be applied are:

  • redirecting listeners from different countries to alternative content, different bitrates and even particular advertising serving static media files and/ or on demand vast ads.

  • Allowing specific groups of listeners to reach a station’s broadcast only on specific time-frames.

Via the account's management portal, administrators have access to the “Filtering” administration panel, under which all “Filtering” related tools can be configured. Following a match of stream(s) and rule(s), one of the following actions can apply. 

...

With the Drop action, a listener connection is dropped (access to the stream is restricted), with an optional media injection (media prompt). This media will play before any ad for each listener! a listener will either get dropped or the listener will hear an audio file and then get dropped. there are no vast ads in either scenarios. the text we have there ‘this media will play before any ad…….’ is not valid at all cases (one of them is the drop action) and should be removed from the UI.

...

b. Continue

The Continue action intercepts and allows the connection with an optional media play (used to play a specific media to user before starting the stream). This is widely used in order to serve advertisements or promos before listeners actually tune-in.

...

With the Loop action, a static media file can be broadcasted in a continuous loop don’t know if you would like to include this in a public doc, but fyi loop action does not work if the stream is not active.

...

e. Vast

Using the Vast action, allows media to be served on (a group of) listeners, using a VAST compatible provider’s inventory. This media can be served upon a listener’s connection (preroll) and/or during the listeners connection (midroll).

...

To add a provider you will need to enter a URL from which pre-roll ads will be served, and a Midroll URL from which midroll ads will be served.

It’s advisable that the Append listener ID is ticked at all times, as…

The Delay Report is best kept ticked, as it delays the reports coming through by a few seconds, in order to balance the misbehaviour of different web players.

...