Campaigns · How-To
Campaign fields, scheduling, publishing, and delivery
A campaign delivers approved assets to eligible Players only when scope, assignments, schedule, status, and Player health all permit playback.
What this does
A campaign delivers approved assets to eligible Players only when scope, assignments, schedule, status, and Player health all permit playback.
Steps
- Create or open a campaign.
- Set its name, campaign type, group/location scope, and eligible assets.
- Assign Players or the supported location coverage.
- Set start/end dates, days, and time windows.
- Validate, save, and publish.
- Confirm delivery analytics and Player health.
Campaign field reference
Name identifies the campaign; type selects compatible output; scope limits eligible locations; assets provide content; assignments select Players; scheduling gates when content can play; active/published state permits delivery.
Draft, active, scheduled, expired, and failed states
Draft is editable but not live. Active can deliver in its window. Scheduled starts later. Expired has passed its end. Failed requires the displayed validation or delivery issue to be resolved.
Takeovers
A takeover is a high-priority scheduled window. Ending or expiring it returns eligible Players to normal scheduling.
Settings reference
| Setting | What it does | Default | Scope | Notes |
|---|---|---|---|---|
| Scope | Limits eligible locations | Current scope | group/location | Location access still applies. |
| Player assignment | Selects destinations | None unless shown | campaign | Only compatible Players appear. |
| Schedule | Controls delivery window | As shown in editor | campaign | Uses the displayed local time zone. |
Permissions and scope
- No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.
Mobile
- On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.
Customer-visible states
- draft
- scheduled
- active
- paused
- expired
- failed validation
- no eligible Players
Campaign playback
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /android/campaigns/:deviceId/:groupId/:locationId
Schedule and assignment result
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /android/campaigns/:deviceId/:groupId/:locationId
Offline and no-content states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /android/campaigns/:deviceId/:groupId/:locationId
Scheduled content and conflicts
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/schedule
Open source campaign
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/schedule
Create, schedule, publish, and end takeover
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/take-overs
Priority consequences
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/take-overs
Conflict and validation states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/take-overs
Search, filter, create, edit, archive, and status
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns
Empty and loading states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns
Campaign name, scope, assets, Players, schedule, and publish
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/tv/new
Validation and no-eligible-Player states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/tv/new
Edit assignments, content, schedule, active state, and publish
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/tv/:campaignId
Delivery and conflict states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/tv/:campaignId
Order Board layout, location, schedule, and publish
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/ob/:campaignId
Queue and Player delivery states
This control is covered by the Campaign fields, scheduling, publishing, and delivery workflow.
Applies to /admin/campaigns/ob/:campaignId
What happens next
Your change is available within the scope you selected.
Warnings
- Publishing does not make an offline Player play immediately. Takeovers can supersede normal content during their active window.
Troubleshooting
- No eligible Players means type, location, permission, or entitlement filters exclude the current scope.
- For non-delivery check active/published state, local time zone, schedule, Player assignment, asset approval, and Player health in that order.
- For offline and no-content states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For conflict and validation states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For empty and loading states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For validation and no-eligible-player states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For edit assignments, content, schedule, active state, and publish, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For delivery and conflict states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
- For queue and player delivery states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.