Hard stops, overrides, phases, urgency and extensions

Use advanced timer behavior deliberately, with clear limits and consistent offer rules.

2 min read

Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.

Start with a simple working campaign

Advanced behavior is available only when the workspace plan allows it. First test the basic timing rule and delivery channel. Then enable one advanced option at a time, save it, and test both its trigger and its end state. Several overlapping rules make it harder to understand which deadline is effective.

Timer behavior configuration with publishing and advanced timing controls — In the application 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)

Hard-stop deadline

A hard stop caps an evergreen window at an absolute time. For example, a visitor may normally receive 48 hours, but all windows must close when an event begins. A late visitor then gets less than 48 hours. Use a timestamp with an explicit timezone; never promise the full duration if a hard stop may shorten it.

Per-recipient overrides

Deadline overrides must be enabled and permitted before supplying a supported deadline value through the generated delivery workflow. They are not unrestricted permission for any URL parameter to redefine your offer. Validate the workflow, preserve a stable recipient identity and use the supported generated fields rather than inventing query strings.

Phases and urgency

Phases let eligible campaigns present different messages or treatments across configured stages. Review the phase sequence and confirm it is enabled as well as saved. A saved but disabled phase list does not itself turn the behavior on.

Urgency presets or custom rules change the presentation near a deadline. They should make an actual approaching deadline clearer, not imply a new deadline or false scarcity. Test a near-expiry preview and the final closed state; the timer must remain readable.

Bounded extensions

An extension requires an enabled extension policy and a permitted trigger. Its threshold, additional seconds, maximum count and maximum total determine whether another extension is allowed. Configure those bounds before connecting automation.

An extension is not an unlimited reset. Check the effective recipient deadline and extension count after a test trigger, and confirm a repeated trigger cannot exceed the configured limits. Tell customers the real terms of any extension.