Skip to main content
Version: 11.x

Scale and deployment

Target groups of screens without selecting each one

A new staff screen can have the right local settings and still miss a campaign because nobody added it to the booking's manual target list. Another screen may change purpose yet remain selected by an old booking. As locations multiply, checking each device by hand becomes difficult.

Store with plant pot promotion screens above the shelves and a portrait pick-up screen behind the service counter
Illustration. Common Goods is a fictional organization; screen content is an example.

Folders and tag rules give publishers selections they can reuse. Use the folder when the audience follows a stable location or responsibility. Use tags when it spans locations or changes as screens take on different roles.

Keep the operating structure in folders​

Screen folders organize displays and can supply inherited Channels & layout, active time, settings, and group access. Targeting a location folder suits a message intended for that area's screens.

That tree should remain understandable to the people maintaining it. Folder planning helps with lasting responsibilities. A temporary campaign name does not need to become part of the permanent hierarchy.

Sometimes the audience cuts across the tree: a retail campaign might need one screen format across several stores, workplace news might belong on staff screens across regions, or wards might contain both visitor and employee screens. Moving those devices into a campaign folder would separate them from the location whose settings they should inherit.

Yellow Common Goods promotion with a red plant pot illustration, headline A good home for your green, and an indoor pot at 9 euros.
Example landscape promotion screen for a retail campaign.

Save the audience as a tag rule​

Tags describe characteristics such as audience, format, or function. A tag folder saves a screen selection using three kinds of rule:

RuleMeaning
ALLMatch every selected tag.
ANYMatch at least one of the selected tags.
NONEExclude screens carrying any selected tag.

The shared-audience example shows the rules working together. Each screen stays in its operational folder and keeps its inherited setup while the tag folder selects the relevant audience.

A central team can use that selection across locations while local publishers continue working with their assigned folders. If units need fully separate resources and administration, use the appropriate site boundary instead; Organize screens by region, department, and location explains that decision.

Connect the rule to a campaign​

Apply consistent tags to the intended screens, prepare the inclusion and exclusion rules, then target the tag folder from a booking. A newly installed screen joins the selection when its tags match; one whose tags no longer match leaves it. Publishers do not need to rebuild an individual list for every recurring booking.

Before relying on the rule, review both matching and non-matching screens. Confirm that the intended devices also receive the booking's channel. Targeting and channel subscription are separate requirements: a tag match alone does not make content play. The booking's published state and schedule, and the screen's active time, still apply.

Publish to screens using tags shows how to select the tag folder when publishing.

Review the selection when its meaning changes​

A shared tag or saved rule may be used by existing bookings. Changing it can add or remove targets from all those uses, so review its impact rather than treating it as a private campaign edit.

Keep names and ownership clear enough that administrators, communications teams, and local publishers can explain why a screen belongs in a selection. After a targeting change, check the resulting audience alongside channel subscription, published state, schedule, and screen active time. The rule reduces manual selection; it does not replace those publishing decisions.