The remote trigger API call is of the following format:
To listen for triggers in an interactive web page it is necessary to have configured a function with the following name:
DigitalSignageTriggerCallback. This function will be called when the remote API call is made.
|Called when the web page starts being displayed.
|Called when the remote trigger API is used. The data will be the data provided to the remote trigger API.
|Called when the web page ends being displayed (after configured duration).
|Delays sequence progression by 30 seconds. This is useful if you know a user is still interacting and do not want to interrupt them.
|Returns the screen ID (MAC address) of the screen displaying the web page.
|Gets data value of the specified name stored in the screen, active item, stack or sequence data.
|Gets data value of the specified name stored in the screen data.
|Puts data value in to the screen data.
|Gets data value from previous (offset=-1) or next (offset=1) positions in main sequence. This can be used to populate HTML sequence frames to display what is on next for example. When offset positive, this function simulates progressing to future items. It will only return items that have a condition that evaluates to true and is fully downloaded.
|Returns the internal player time in milliseconds since epoch. This time is updated based on server time and is typically more accurate than the system clock (especially if NTP is blocked or disabled).
A simple example is available here.