Page Comparison

Intro

Playlists are where you manage the actual content that Browsi’s instream player will serve to your audience.

...

Player tag - when you implement different tags on different groups of domains, this targeting option is a very convenient way to match video content with domain content.
Domain - across a whole domains, article content is usually consistent in language, and often in category as well. This making it a good way to match video content.
Country - when your user base comes from different countries, you can use this targeting dimension to cater to their native languages
URL contains - your sites may separate content categories into different sections, which is usually reflected in URL paths.
For example, a news site may have a sports section with the URL www.site.com/sports/article_id and an entertainment section with the URL www.site.com/entertainment/article_id.
In which case you can maintain a sports playlist targeted to URLs that contain “/sports/” and an entertainment playlist targeted to URLs that contain “/entertainment/”
Meta tags - coming soonthe player will read all meta description and meta keywords on the page, and will serve playlists that match values in these meta tags.

Panel

Playlists can only be activated after at least one video is added to them
The default playlist can’t be paused once active, to ensure content is always available to your instream player. Contact you CSM with any question about this.
Playlist targeting must be unique to ensure a single playlist is served to the player. This means you will not be able to save 2 different playlists with the same targeting settings
When more than one targeted playlist still matches the current session, the playlist with more targeting dimensions will “win”.
For example, playlist #1 targets tag 1 in US and playlist #2 simply targets US. When both playlists are a match, playlist #1 will be served because it is more specific.
When more than one targeted playlist still matches the current session, and both have the same number of targeting dimensions, a set hierarchy will determine which playlist is served, which matches the order of targeting dimensions in the UI - player tag > domain > country > URL.
For example, playlist #1 targets tag 1 and playlist #2 targets US. When both playlists are a match, playlist #1 will be served because tag targeting is “stronger” than country targeting.