Skip to content

Schedule

The Schedule card on the Overview tab limits the stage to a specific date-time range. Outside that range the stage is filtered out at the resolve step — visitors don’t see it, no impression events are recorded.

Two optional datetime fields:

  • Active from — the stage becomes active at this moment. Leave empty for “no lower bound”.
  • Active to — the stage stops being active at this moment. Leave empty for “no upper bound”.

Both stored as DATETIME columns in UTC. The picker in the admin shows them in your browser’s local timezone but writes UTC.

Combinations:

Active fromActive toBehaviour
emptyemptyAlways active (subject to the Active toggle on the General card).
setemptyActivates at from, never deactivates by schedule.
emptysetActive until to, then deactivates.
setsetActive during [from, to].

The General card has a separate Active boolean. Schedule and Active compose with AND:

  • Active = off → never visible, regardless of schedule.
  • Active = on + schedule out of range → not visible.
  • Active = on + schedule in range (or empty) → eligible (subject to targeting + frequency).

The Active toggle is the kill switch; the schedule is the timer.

On every storefront page load, when /p2lab-stage/resolve filters stages, it compares the current server time against active_from and active_to. Stages outside the window are not returned to the client.

This means activation / deactivation is server-time-precise — visitors in different timezones see the same activation moment.

  • Time-boxed campaign — set both ends to bracket the promo (from = 2026-06-01 00:00, to = 2026-06-08 23:59). The stage activates automatically, no manual flip needed.
  • Pre-announcement — set from only. The stage is ready to publish ahead of time, will go live at from.
  • Stop date with manual start — set to only, flip Active manually when you want it live. Once to passes, it auto-stops.
  • Always on — leave both empty. Manage on/off solely via Active.