Always (every page load)
The countdown bar shows every time the trigger fires on every visit. Appropriate for active sales and persistent promotions.
Once per session
Shows once per browser session. After the visitor sees it, it won't reappear until a new session begins.
💡The most common frequency for countdown bars — present without being repetitive.
Once per visitor (lifetime)
A flag is stored in localStorage so the countdown never shows again to that visitor on that device, even across sessions.
Once per calendar day
Shows once per day, resetting at midnight local time.
Every 24 hours (rolling)
Shows once every 24 hours from when the visitor last saw it — regardless of calendar day boundaries.
Every N days
Shows once, then waits a specified number of days before showing again.
Once per week
Shows once per ISO calendar week (Monday–Sunday).
Once per week (business days)
Shows once per business week (Monday–Friday only).
Once every 2 weeks
Shows once every 14 days.
Once per month
Shows once per calendar month.
Once per year
Shows once per calendar year.
N times per day
Shows up to a set number of times per calendar day.
N times per visit
Shows up to a set number of times per session.
N times per week
Shows up to a set number of times per ISO week.
N times per month
Shows up to a set number of times per calendar month.
N times lifetime
Shows up to a set total number of times across all sessions, stored in localStorage.
Cookie control
The countdown shows when a specific named cookie is present in the visitor's browser, and is suppressed when that cookie is absent.
💡The Adobe Target mbox cookie is always present on Target-enabled pages — a reliable gate to show only to Target visitors. Use any custom cookie for segment-specific targeting.
Profile attribute (AT)
Shows once per visitor — same as 'Once per visitor (lifetime)'. The difference is how the flag is stored: it uses a key prefixed with _at_profile_ so it's easy to find and delete in your browser's storage. Useful when running the same promotion across multiple Adobe Target activities and you need a consistent, identifiable key.
💡To reset during testing: DevTools → Application → Local Storage → delete the key starting with _at_profile_. The countdown will show again on next load.
Step-by-step guideEvent-based reset
Shows once per visitor, but can show again whenever your site fires a named signal. For example: re-show the countdown when a visitor starts checkout, navigates to a sale category, or reaches a loyalty tier. A developer adds one line of JavaScript to your site at the moment you want the reset to happen.
💡Enter your event name in the Cookie/Event Name field (e.g. show-offer-again). Share that name with your developer — they fire it with: document.dispatchEvent(new Event('show-offer-again'))
Step-by-step guideUntil conversion
Shows on every visit, every time the trigger fires — until the visitor converts. Once they purchase, register, or complete whatever action you define, a flag is written to their browser and the countdown permanently stops appearing. Great for lead nurture: keep showing the urgency timer until they act, then stop immediately.
💡If you have Adobe Tags, GTM, or any tag manager, you can do this yourself — no developer needed. See the step-by-step guide.
Step-by-step guide