Scheduled Deployments
If your agreement has a fixed time window — a seasonal promotion, a policy update going live on a specific date, or a consent banner that should expire — you can schedule a deployment to activate and deactivate automatically without any manual intervention.
Setting a schedule
When creating or editing a deployment, you can set:
- Start date — the date and time the deployment should go live.
- End date — the date and time it should stop serving users.
You can set one or both:
| Configuration | What happens |
|---|---|
| Start date only | Goes live at the set time, stays active until you manually deactivate it |
| End date only | Active immediately, expires automatically at the set time |
| Start and end date | Fully automated window — activates and deactivates on its own |
How to set up a scheduled deployment
- Go to Click → Deployments → + New Deployment (or open an existing one).
- Configure your domain and path and environment as usual.
- Set a Start Date, End Date, or both.
- Create the deployment.
- Toggle the deployment Active — this is what arms the schedule. Without it turned on, the schedule has no effect.
Screenshot: click-scheduling-fields, screenshot of the deployment form with the Start Date and End Date datetime pickers expanded, and the Active toggle in the on position
Transitions and overlapping windows
Only one deployment can be active on the same page at a time. If you're scheduling a transition — for example, replacing version 1 of your Terms with version 2 — make sure the schedule windows don't overlap. Activating a second deployment on the same page will automatically deactivate the first.
If you're scheduling a new policy version, align the start date with when the updated template takes effect. Template versioning is currently in development — see Version Management (coming soon) for updates.
Viewing scheduled deployments
The Deployments list shows the start and end dates on any deployment where they've been set, so you can see at a glance what's scheduled to go live or expire.
Screenshot: click-scheduled-filter, screenshot of the Deployments list showing deployments with start and end date badges
Screenshot: click-scheduled-expired, screenshot of a deployment that has passed its end date, showing it in a deactivated state with the past end date badge still visible on the row
Next steps:
- A/B Testing — combine scheduled windows with variant testing
- Click Analytics — measure acceptance rates over your scheduled window
- Evidence Collection — understand how scheduling is recorded in the audit trail