Managing evergreen timers by recipient
Create consistent countdown experiences for individuals across multiple messages and browser sessions.
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.
Understanding duration versus end dates
An Evergreen timer assigns a set duration to an identified visitor. A 60-minute campaign provides a single window of up to 60 minutes from the identity's start event. This does not mean that every individual image request triggers a new hour.
Check your start policy within the publishing or timer-behavior settings. A first-request start begins when the first valid request occurs, which does not confirm a user has read your message. Send-time configurations require your workflow to provide the specific deadline.
Using recipient identifiers
The vid value functions as a stable recipient or visitor identifier. Assign a unique value to every recipient and reuse it consistently in your image URL, smart link, and website requests. Use an opaque ID rather than personal information like email addresses or phone numbers in public URLs.
For providers that support contact IDs, use their official merge-tag method. Otherwise, generate and map a countdown_id custom field. Errors such as unexpanded merge tags, missing values, or shared IDs can lead to incorrect identity behavior.
Tracking anonymous visitors
Website delivery utilizes a visitor identity mechanism if no explicit recipient ID is provided. Please note that different browsers, devices, private sessions, or cleared storage are treated as unique anonymous visitors. For cross-device consistency, your application must securely pass a stable identity rather than assuming browser storage links to the user.
Running a validation test
- 1Set up a short-duration test campaign and use two distinct opaque values, such as demo-contact-a and demo-contact-b.
- 2Open the first identity, wait, and open it again to confirm it continues counting toward the initial window.
- 3Open the second identity to verify its unique window, then follow the first identity’s smart link to test channel handoff.
- 4If using a send deadline, test the generated URL via a real provider send; do not rely on dashboard samples to represent a recipient window.