Skip to content
C CountdownFlow Help Center Sign in

Configuring complex scheduling and overrides

Control urgency, offer extensions, and per-recipient adjustments within your campaign limits.

2 min read

Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.

Starting with a basic setup

Advanced features require an appropriate workspace plan. Begin by testing basic timing and delivery, then enable one advanced option at a time, saving and testing both the trigger and the end state. Overlapping rules can make it difficult to determine which deadline is active.

Timer behavior configuration with publishing and advanced timing controls
The behavior screen contains the supported destination and advanced timing controls. Review the applicable settings and save before testing your public link. View full-size screenshot (opens in a new tab)

Implementing hard-stop deadlines

A hard stop caps an evergreen window at an absolute time. For example, a 48-hour window might be cut short if an event begins, resulting in a shorter duration for late visitors. Always use an explicit timezone-aware timestamp; do not promise a full duration if a hard stop might truncate it.

Setting up individual overrides

Deadline overrides require specific permissions and must be enabled before using them in your delivery workflow. They are not intended to allow arbitrary URL parameters to redefine your offers. Validate your workflow, maintain stable recipient identities, and use supported generated fields instead of custom query strings.

Adding urgency phases

Phases allow campaigns to present different treatments across stages; ensure the phase list is both enabled and saved to activate the behavior.

Urgency presets and custom rules should clarify approaching deadlines rather than implying false scarcity. Test near-expiry previews and final closed states to ensure the timer remains legible.

Defining extension limits

Extensions require an enabled policy and a valid trigger. Bounds such as thresholds, additional time, and maximum counts must be configured before automation is applied.

Extensions are not unlimited resets. Verify the effective deadline and extension count after testing, and ensure repeat triggers do not exceed configured limits. Always communicate the true terms of any extension to your customers.

Related articles