How scheduling works
One release per campaign
A campaign is tied to a single Experience Release. Scheduling sets when that campaign’s data should go live.London timezone
All schedule times are interpreted in London time.Start and end dates
You can set both, but only the start date is enforced. The end date is informational.States
Draft: editable, not scheduled
Scheduled: has a future start date
Published: live or awaiting pickup by devices
Archived: retained for history and possible manual rollback
What happens at start time
If the device is online
The device pulls the new campaign on the next sync cycle:Experience reload every 15 minutes
Idle invalidation after 60 seconds
Any service worker update from a new build
If the device is offline
When the device reconnects, it checks for pending releases and downloads the campaign, then updates the screen.
Tip: Keep devices online daily so changes apply promptly and analytics stay fresh.
Conflicts and priority
If two scheduled campaigns target the same device and time window, the newest by start date takes priority.
There is no automatic rollback at the end date. To change what is live, publish a new campaign.
You can manually roll back by selecting an older version in the dashboard and publishing it again.
Create or edit a schedule
Open your campaign and choose Schedule.
Set the start date and time (London) and confirm.
Target your devices or locations.
Save to create a Scheduled version.
Editing a schedule
Changing the start time or targets creates a new version.
Devices will apply the campaign according to the updated schedule and the rules above.
Notifications and visibility
The dashboard can notify you on schedule created, publish, failure, or rollback events.
On the campaign list you will see the state, next start time, and the targeted devices count.
Freeze windows
By default there is no freeze window. Updates can apply at any time and do not require downtime.
Enterprise clients can request a publish freeze window through support.
Best practices
Plan ahead: heavy assets increase download time. Keep images under 500 KB and total campaign size under 20 MB unless using video.
Name clearly: include release and date in the campaign name to simplify audits.
Test first: use Preview links and, if needed, create a test campaign on a small set of devices.
Avoid overlaps: stagger starts or use clear cutovers to minimise confusion at sites.
Monitor pickup: after start time, allow one 15 minute reload cycle and check device Last seen in the dashboard.
FAQs
What if I add devices after scheduling?
They will receive the campaign at or after the scheduled start time using the same sync rules. If the start time has passed, they will apply it on next connect.
Can I schedule multiple releases in one campaign?
No. A campaign links to one Experience Release. Create another campaign if you need a different release.
Can I pin a campaign to “latest release”?
Campaigns are tied to a specific release version. Authors manage release code in Git and publish fixed versions.