Admira Docs
English
English
  • Welcome to Admira
  • BASIC KNOWLEDGE
    • Introduction
    • Online management portal
    • Quick videoguides
      • Upload content
      • Check screen status
      • Blocks
      • Templates
      • New user
    • Basic concepts
    • Content scheduling
  • Admira Player Installation
    • Windows 10
      • Installing the Admira Player
      • BIOS Setup
      • Windows operating system settings
      • Windows settings
      • Windows Firewall
      • Windows Update
      • Recommended external applications
        • Remote access
        • Scheduled shutdown
        • Unnecessary applications
    • Apple
      • MacOS
      • iOS
    • Linux
      • Debian / Raspberry Pi OS
      • Ubuntu
    • Philips
    • LG
      • LG WebOs 6
      • LG WebOs 4
      • LG WebOS 3
      • LG WebOS 2
    • Samsung
      • Samsung SSSP 4-6 (Tizen)
      • Samsung SSSP 2-3
    • Android
    • Chrome OS
  • CONTENTS
    • Content creation good practices
    • Compatible formats and technical requirements
    • Upload content
    • Content management
    • Deleted Content
    • Fastcontent
    • Smartcontent
    • HTML content
      • File structure
      • Good Practices
      • Admira API HTML5 content
      • File nomenclature
      • Basic HTML structure for template
      • URL contents
    • Interactive content
  • Production
    • Playlists
    • Playlist with criteria
    • Blocks
    • Categories
    • Criteria
    • Ratios
    • Templates
  • Deployment
    • Inventory
    • Schedules
    • Incidences
    • Multiplayer mode
    • Conditional assignment
  • Management
    • Administration
    • Live
    • Users
    • Connectivity
    • Stats
      • Stats by content
      • Stats by player
      • Statistics by campaign
      • FAQs
    • Log
      • Status log
      • Downloads log
      • Screens log
    • Roles
    • Reporting
      • Report Types
      • Project Templates
      • Filter
      • Permissions on Reports
      • Grouped campaign reports
      • Tutorial: Procedure to create and generate reports
      • FAQ
  • Advertising
    • Campaigns
    • Calendar
    • Ocuppation
  • Additional Information
    • Network requirements
  • Admira Suite
    • Admira Helpdesk
Powered by GitBook
On this page
  • Introduction
  • Conditions
  • Condition group
  • Condition Types
  • Conditions priority
  • Actions
  • Triggers
  • How to assign conditions on the platform
  • Configuration example
  • Conditions Library

Was this helpful?

  1. Deployment

Conditional assignment

Introduction

Admira’s conditional digital content playback system allows you to modify the content and/or the way it is displayed on a player, depending on the evaluation of certain external agents and the establishment of a series of conditions that must be met for a content is displayed on the screen.

The conditional system provides the player with greater intelligence, since it will be able to determine at any time, based on a series of predetermined conditions and the evaluation of their fulfillment, what content is going to be reproduced next, beyond the programming that have assigned (content included in a loop or simple playlist).

From the Administration > Management > Conditions Assignment section, you can condition the behavior of the following elements:

  • Contents and/or blocks in a simple playlist

  • Act in real time on external changes (Triggers)

  • Templates both in simple playlists and in advanced mode

The conditional player functionality allows programming to be segmented based on variable external parameters, such as the geolocation of players installed in bus/taxis fleets (geopositioning by quadrants or groups of 4 position marker conditions –latitude and longitude–), number and sex of the people who are looking at a screen (audience measurement) or values provided by temperature sensors.

Conditions

They are the necessary circumstances that must occur at a given time for the player to broadcast content X.

Condition group

Conjunctive grouping (“AND”) of various conditions. It is used to combine multiple conditions that must be fulfilled simultaneously for the player to emit content X.

Condition Types

The condition types are the labels for each reference to a condition, that is, the TOPIC to evaluate. For example, multiple conditions from different topics or from the same topic can be evaluated in a condition pool.

  • Topic A : Number of observers

  • Topic B : Gender of the observers

Condition group 1

Are there more than 5 people watching? (Topic A)

The content of "Group Offer" will be broadcast

Is there 1 person watching? (Topic A) + Is there a woman watching? (Topic B)

The content "Special Woman" will be broadcast

As an example of audience gender conditions, we would do it as follows:

  • If Audience Sex = 1 replace with Male creative

  • If Audience Sex = 2 replace with creative of Woman

Other conditions that we can apply are:

  • Total Audience: Total number of people in front of the screen.

  • Male Audience: Total number of people in front of the screen.

  • Female Audience: Number of women in front of the screen

  • Audience Arrived: Newcomer audience in front of the screen

  • Audience Sex: Sex majority (for example: 0 = equality, 1 = men, 2 = women)

Conditions priority

The same element of the simple playlist can have multiple conditions assigned, in these cases the priority is determined by its order in the list, so that the first condition evaluated will be the one with the lowest priority, and can be modified by the next one. At the first condition that is fulfilled, the action will be carried out (replacement/issuance of the affected content).

Actions

These are the actions that will be applied in the event that a group of conditions is met.

The actions that can be carried out are:

  • Replace a content with another content/block of a playlist (keeping its properties): in this case the content/block that replaces the current one must exist in the playlist (CONTENT_REPLACE)

  • Replace a content with another content/block that does not belong to the playlist, in this case neither broadcast schedules nor number of passes, etc. (FILE_REPLACE) are taken into account

  • Replace a template applied to a playlist element (content / block / block content) or to the same template (TEMPLATE_REPLACE)

Triggers

Triggers are groups of conditions evaluated in real time to modify the substitution or adaptation of a conditioned element.

Triggers have a higher priority over groups of conditions that can be set for a single playlist position.

Example:

TOPIC C: Character detection

Condition grupo TRIGGER

Did a person just stop? (TOPIC C)

“Welcome to the Center” content will be broadcast

Examples of trigger behavior

<interruption = 1 interval = 0>

It is applied when we want the playback to be interrupted at any time that the data of the condition changes and is true

<interruption = 0 interval = 0>

It is applied when we want the reproduction to NOT be interrupted but to be constantly reviewed when the data of the condition changes and is true

<interruption = 0 interval = 60>

It is applied when we want the reproduction NOT to be interrupted when a condition is valid, but it is to do so in the following content.

In addition, we want that in the event that the data does not change, the review of the condition is forced in 60 seconds, interrupting playback again. It is recommended to set intervals greater than 10 seconds or more

<interruption = 1 interval = 60>

The interval time counts from the last time the condition is checked (and returns true) and NOT from the moment the condition is triggered.

How to assign conditions on the platform

We can access the Assignment of Conditions from the Administration > Management > Assignment of Conditions section. From this section, the triggers that will affect one or more players on the circuit are created and added.

Configuration example

Conditions for a simple player.

Conditions in the simple playlist assigned to a player.

The user interface allows:

  • Create / Edit: Types and groups of conditions

  • Add / Edit: Conditions

  • Apply / Modify: Resulting Action

  • Delete: Click on “delete” and then on the “Save triggers” button

Important

To correctly define and save an area of the map in which the condition will be applied, it is necessary to center the circle on a certain point and, once the radius of action is well defined, click on the center before “Save”.

Conditions Library

This new system resource allows you to save the conditions created to add them later or assign them to another player on the circuit. In this way, if the same triggers have to be put into operation on a regular basis, the project conditions can be configured only once and implemented when necessary in an agile and simple way.

If you need to load a previously saved condition, click the “Add from library” button, and choose the desired condition from the project conditions library selector.

PreviousMultiplayer modeNextAdministration

Last updated 1 year ago

Was this helpful?

Players list
Players list
Configuration for a simple player
Edit playlists
Conditions