zebrix documentation : Presentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Presentation ======

In Zebrix, tags are essential.
They are used to classify and organize your items: hardware, users, media, pages, or playlists.
They also allow you to personalize your content delivery based on a device, a department, a store, a city, a region, or even a national area.

Tags also help define user permissions.
For example, a store manager can only manage the content of their own location, while the marketing team, with national rights, can broadcast content to multiple locations.

Tag Families
A tag family groups tags under the same theme (e.g., locations, store departments, store codes, or hardware features).

Hierarchical Tags
Hierarchical tags allow you to create subgroups within the same family.
This helps target broadcasts at different levels (country, region, city, site…).
Example: a “Location” family may include countries, their regions, cities, and finally the sites where screens are installed.

Tags
Imagine a tag family Departments with the tags Butchery and Fish Counter.
If a page is tagged “Butchery” and a screen is also tagged “Butchery,” the page will play on that screen.
However, a “Butchery” screen will not display content tagged “Fish Counter.”

<WRAP center round tip 60%>
Tag families and their tags are not created automatically on client accounts.
They are configured according to each client’s structure and communication logic.
The examples provided here are common use cases.
</WRAP>

====== 1. Tagging screens and players ======

==== Locating a device ====
You can assign one or more tags to your screens.
For example, in a “Location” family with hierarchical tags, a screen can be tagged Lille, Nord, Hauts-de-France, and France.
This allows you to target content delivery by country, region, or city.

==== Device orientation ====
Create an “Orientation” family and tag your screens as Portrait or Landscape.
This ensures that only content with the same orientation will be displayed on each screen.

==== Placement within the venue ====
You can also tag screens based on their position in the store (e.g., Window, Checkout, Butchery, Fruit & Vegetables…).
This allows you to create dedicated playlists for each zone.
If all your locations are tagged this way, you can, for example, target all Butchery screens to broadcast department-specific content.

==== Specifying a store location ====
You can assign a store code to your devices to target a specific point of sale.

====== 2. Tagging a user ======

Tagging a user allows you to restrict their permissions to their activity area.
For example, the butcher in Lille may be tagged Lille and Butchery.
They will only access screens and content related to their department.
If they upload new content, it automatically inherits their tags, which cannot be removed by that user.

Conversely, a marketing user may have no tags, allowing access to all content and screens.
They can also create untagged content and add tags later if needed.

====== 3. Tagging media ======

Tagging media helps categorize them.
For example, in a supermarket:

Images or videos about meat are tagged Butchery

Those about fish are tagged Fish Counter

Thus, a user tagged Fish Counter will only see media relevant to their area.
They won’t have access to Butchery content.

<WRAP center round tip 60%>
An untagged media file is visible to everyone.
A media item tagged with a family outside of a user’s restrictions is still visible to that user.
(This rule also applies to devices, pages, playlists, and schedules.)
</WRAP>

====== 4. Tagging a page ======

You can tag a page based on:

its orientation (Portrait or Landscape),

its location (Country, Region, City, Store Code, Department…),

or a specific campaign (Halloween, Anniversary Promo…).

This helps limit or target its broadcast.

==== a) Tagged media within pages ====
You can import the following into a page:

photos

videos

data sources

<WRAP center round tip 60%>
Media and page compatibility:
If a Butchery media is placed inside a Fish Counter page:

the page won’t appear on a Butchery screen

it will appear on a Fish Counter screen, but with an empty space instead of the media

</WRAP>

==== b) Data sources within pages ====
Data sources are data tables based on a tag family.
Each row corresponds to a tag, with different fields (text, image, video, URL…).
This allows you to display different content depending on the device’s tag (e.g., a specific image per store).

Data sources must be inserted into the page, with each element placed in a matching content zone (image, text, etc.).
As a result, the page automatically adapts according to the target device’s tags.

====== 5. Tags in playlists ======

Playlists can also be tagged, just like media or pages.

Example: a playlist contains three media items — one untagged, one Butchery, and one Fish Counter.
On a Butchery screen, only the untagged and Butchery items will play.
The Fish Counter media will be skipped.
After the two visible items finish, the loop restarts.

It’s important to manage tag interactions carefully.
Avoid using the same tag families for both a playlist and its items, to prevent hidden or invisible content.

You can also add a custom playlist within a global one.
Example: a promotional playlist with a featured product that varies by store.
You could create a custom playlist using the “Store Code” or “Location” family, and for each tag, assign the appropriate product page.

====== 6. Tags and scheduling ======

There are three types of schedules:

by device

by tag

global (* symbolized by an asterisk *)

They follow a priority order:

Device schedule → highest priority (specific to one screen)

Tag schedule → overrides the global schedule

Global schedule → lowest priority

If multiple schedules overlap, the device schedule plays first, then the tag schedule, and finally the global schedule if no others are active.