Popup scheduling and frequency
Control when the popup appears, how long it stays, and how often it comes back.
The Schedule tab controls timing and frequency. Getting these right is the difference between a helpful nudge and an annoyance.
Timing settings
| Setting | What it controls |
|---|---|
| Delay Time | Seconds before the popup first appears |
| Display Time | Seconds the popup stays on screen |
| Show Again Time | Seconds before it reappears |
| Impressions | How many times a visitor sees it |
| Always Visible | Keeps the popup on screen instead of hiding it |
Set the timing
Open the Schedule tab.
Set Delay Time — how long after page load the popup appears.
Set Display Time — how long it stays before hiding.
Set Show Again Time — the gap before it returns.
Set Impressions — the cap on how many times it shows.
Click Save.
Suggested starting values
| Setting | Value |
|---|---|
| Delay Time | 10–15 seconds |
| Display Time | 6–10 seconds |
| Show Again Time | 60+ seconds |
| Impressions | 3–5 |
Frequency is where popups go wrong
A popup that reappears every 10 seconds with no impression cap will drive visitors off your site. Set an impressions limit and a generous show-again time before you publish.
Run it for a date range
Tick Enable Date Range.
Set the Start Date.
Set the End Date.
Click Save.
The popup only runs between those dates — useful for a campaign that shouldn't outlive its offer.
There are also Enable Visibility Date and Enable Fixed Time options for finer control over when the popup is eligible to show.
Priority
Set a Priority so the app knows which popup wins when more than one qualifies for the same page. The popup list shows each one's priority as High, Medium, or Low.
Tip
Only run one popup per page. If two both qualify, the lower-priority one is competing with your own campaign for the same square of screen.
Advanced triggers
Two advanced fields accept JSON configuration:
- Button Selectors — CSS selectors for buttons the popup should react to, for example
{"addToCart": ".btn-cart", "checkout": ".btn-checkout"} - Added to Cart Items — product and quantity configuration, for example
{"productIds": [123, 456], "quantity": 1}
These fields expect valid JSON and theme-specific CSS selectors. If you aren't sure what your theme's add-to-cart button class is, leave them empty — an invalid selector silently stops the trigger from ever firing.