Assignment conditions

You are here:

Triggers

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

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

Example:

TOPIC C: Person detection
TRIGGER condition group
Has a person just stopped? (TOPIC C) = “Welcome to the center” content will be issued
Example of the trigger option “launch content on click”
It is possible to setup a trigger to launch content during an event by using a wireless mouse.

Examples of triggers behavior:

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

 

Example 2
 
Applies when we want the playback to NOT be interrupted but to be constantly reviewed when the condition data changes and is true.

 

Example 3
 
it is applied when we want the playback to NOT be interrupted when a condition is valid, but to do so in the following content.
We also want that every 60 seconds it forces to review the condition again without interrupting the current playback, if it is true, the condition will be triggered and it will wait another 60 seconds (this option is very useful for programming with blocks).

 

Example 4
 
It is applied when we want the reproduction to be interrupted at any time that the data of the condition changes and is true, we also want that in the case that the data does not change, the condition review in 60 seconds … interrupting playback again. It is recommended to set intervals longer than 10 seconds or more (this is a very rare use case).

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

User Interface

From the “Assignment of conditions” page (Distribution section) of the online management portal (https://new.admira.mobi/admin/deployment/triggers) the triggers that will affect one or more players of the circuit are created and added .

Players list

Example of conditions setup for a simple player

Player List

Example of conditions setup in playlist assigned to a player

Edit Playlist

User interface allows to:

  • Create / Edit: Condition groups and types
  • Add / Edit: Conditions
  • Apply / Modify: Resulting Action
  • Delete: Click on “delete” and then on the button “save triggers”

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 “saving ”.

Add from Library

This system resource allows you to save the created conditions 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 on the “Add from library” button, and choose the desired condition from the project condition library selector.

Conditions
Circuit management panel

Overview

Our Conditional Player system allows the scheduling of digital content to be triggered, depending on the evaluation of certain external agents and the setting of a series of conditions that must be met for a content to be displayed on screen.

The conditional system enhances the player intelligence, since it will be able to determine at all times, based on a series of predetermined conditions and the evaluation of their compliance, which content it is going to reproduce next, beyond the general loop assigned (contents included in simple playlist).

From the Administration > Management > Assignment of Conditions section, you can setup the following player actions:

  • Replacing 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 (2nd phase soon)

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

Conditions

Necessary circumstances that must occur at a certain time for the player to broadcast X content.

Group of conditions

Conjunctive grouping (“Y”) of several conditions. It is used to combine multiple conditions that must be met simultaneously for the player to broadcast X content.

Condition types

Condition types are the labels for each reference to a condition, that is, the TOPIC to be evaluated. Ex: in a group of conditions, multiple conditions of different topics or the same topic can be evaluated. Example:

  • Topic A: Audience Number
  • Topic B: Audience Gender
Group of conditions 1
Are there more than 5 people watching? (Topic A)
The content of “Group Offer” will be issued
Group of conditions 2
Is there 1 person watching? (Topic A) And is there a woman watching? (Topic B)
The content “Special Woman” will be shown on screen

Example of audience gender conditions:

  • If Audience Gender = 1 replace with Man creativity
  • If Audience Gender = 2 replace with Woman creativity

Other conditions:

  • Total Audience: total of people in front of the screen
  • Male Audience: number of men in front of the screen
  • Female Audience: number of women in front of the screen
  • Audience Arrived: newly arrived audience in front of the screen
  • Audience Sex: most sex eg. 0 equality, 1 men, 2 women

Priority of the conditions

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

Actions

The action 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 times nor number of passes, etc. are taken into account (FILE_REPLACE)
  • Replace a template applied to an element of the playlist (content / block / block content) or to the same template (TEMPLATE_REPLACE) will be available soon

Triggers

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

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

Example:

TOPIC C: Person detection
TRIGGER condition group
Has a person just stopped? (TOPIC C)
“Welcome to the center” content will be issued
Example of the trigger option “launch content on click”
It is possible to setup a trigger to launch content during an event by using a wireless mouse

Examples of triggers behavior:

Example 1
<interruption = 1 interval = 0>
It is applied when we want the reproduction to be interrupted at any time that the data of the condition changes and is true
Example 2
<interruption = 0 interval = 0>
Applies when we want the playback to NOT be interrupted but to be constantly reviewed when the condition data changes and is true
Example 3
<interruption = 0 interval = 60>
it is applied when we want the playback to NOT be interrupted when a condition is valid, but to do so in the following content
We also want that every 60 seconds it forces to review the condition again without interrupting the current playback, if it is true, the condition will be triggered and it will wait another 60 seconds (this option is very useful for programming with blocks)
Example 4
<interruption = 1 interval = 60>
It is applied when we want the reproduction to be interrupted at any time that the data of the condition changes and is true, we also want that in the case that the data does not change, the condition review in 60 seconds … interrupting playback again. It is recommended to set intervals longer than 10 seconds or more (this is a very rare use case)

Important

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

User Interface

From the “Assignment of conditions” page (Distribution section) of the online management portal (https://new.admira.mobi/admin/deployment/triggers) the triggers that will affect one or more players of the circuit are created and added .

Players list

Configuration example

Conditions setup for a simple player.

Configuration for s simple player

Conditions setup in playlist assigned to a player.

Edit playlists

User interface allows to:

  • Create / Edit: Condition groups and types
  • Add / Edit: Conditions
  • Apply / Modify : Resulting Action
  • Delete: Click on “delete” and then on the button “save triggers”

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 “saving ”.

Add from Library

This system resource allows you to save the created conditions 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 on the “Add from library” button, and choose the desired condition from the project condition library selector.

Conditions
Print Friendly, PDF & Email
Next Inventory
Table of Contents