Targeting model
You target kiosks directly from the campaign.
The UI includes quick-select options for country and location to speed up targeting.
There are no rules-based groups. Selection is explicit.
A device can be targeted by many campaigns over time, but only one campaign is active at a given moment based on schedule and conflict rules.
Choose devices for a campaign
Open your campaign and go to Targets.
Search or browse and select kiosks.
Use quick-select to add all kiosks in a country or a location if needed.
Save your selection.
Editing targets after publish
You can add or remove devices at any time.
Devices apply the campaign on the next online check and reload cycle.
Locale behaviour
Each Location has Translation preferences:
Default language for all kiosks at that location.
Preferred languages used when available in the campaign.
If a preferred language is not provided in the campaign, kiosks fall back to English.
Enterprise option: set a default fallback language at the organisation level.
Working with translations in campaigns
Translations are per field. Switch languages using the tabs at the top of the editor.
Required fields must be completed for any mandatory locales defined by the experience author.
Use Preview to check each locale before publish.
Tips and good practice
Keep campaign names clear, for example: Spring Promo v2 — EN/FR.
Confirm each targeted location has matching translation coverage.
When testing different targeting sets, duplicate the campaign and assign it to a small device list first.
What campaigns do not control
Campaigns manage content and data only.
Brightness, volume, screen timeout and other device settings are configured at the kiosk level and in device actions, not in campaigns.
