> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-countdown-timer-bar/sale-popups/general-settings.md).
# Sale popup general settings
The timing, sequencing, and display behaviour shared by every sale popup on your store.
Each popup has its own content, design, and schedule. **Popup General Settings** holds the behaviour they share — how they're paced, how many run, and what order they appear in.
Open it from the **Sale Popups** page.
Popup General Settings applies to every popup on your store.
## Display behaviour
| Setting | What it does |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Show / hide time ago** | Whether popups show a relative time. Options are **Show time ago**, **Hide time ago**, and **Smart hide** |
| **Hide time ago after** | With **Smart hide**, the age at which the time stops being shown — paired with a **Time unit** of **Minutes**, **Hours**, or **Days** |
| **Truncate content** | Cuts long content to one line instead of wrapping it. The app's example: "Product na..." |
| **Hide close button** | Removes the ✕ from the popup |
| **Show text right to left** | Renders popup text right-to-left, for RTL languages |
{% hint style="warning" %}
Think twice about **Hide close button**. A popup a shopper can't dismiss is the kind of thing that gets a store's whole site muted. If it's on, make sure **Duration** on each popup is short enough that it goes away on its own — see [Visibility and schedule](/samita-countdown-timer-bar/sale-popups/visibility.md).
{% endhint %}
## Timing
These four settings pace every popup on your store.
| Setting | What it controls |
| ----------------------------- | ------------------------------------------------------------------------ |
| **Display duration** | How long each popup stays on screen, in seconds |
| **Time before the first pop** | How long after the page loads before the first popup appears, in seconds |
| **Gap time between two pops** | The wait between one popup closing and the next opening, in seconds |
| **Maximum of popups** | How many popups can be shown in total |
A few things worth getting right:
**Give the page a moment first.** A popup that appears instantly interrupts a shopper who hasn't yet seen what they came for. A few seconds of delay costs nothing.
**Leave a real gap.** Back-to-back popups read as a stream of notifications rather than a message.
**Keep the maximum low.** This is a ceiling on interruptions per shopper, and a low one is a feature.
## Sales Pop strategy
How the app chooses which popup to show when you have several.
| Setting | What it does |
| ------------------------------ | ------------------------------------------------------------------------ |
| **Display by** | **Display randomly** or **Display in order** |
| **Replay playlist** | Starts again from the beginning once everything has been shown |
| **Continue after page reload** | Picks up at the next popup after a reload instead of restarting the list |
| **Based on product view** | Only shows popups related to the product the shopper is looking at |
**Display in order** is the one to use when your popups tell a sequence — an announcement, then the offer. **Display randomly** suits a set of independent messages.
**Continue after page reload** is usually what you want. Without it, a shopper who browses five pages sees your first popup five times.
{% hint style="info" %}
**Replay playlist** combined with a high **Maximum of popups** means a shopper can keep seeing the same popups round and round. Turn it on only if the popups are genuinely worth repeating.
{% endhint %}
## Font
The page also carries a font setting applied to popup text, so every popup shares a typeface unless one overrides it in its own [Design tab](/samita-countdown-timer-bar/sale-popups/design.md).
## A conservative starting point
If you're not sure, start here and adjust:
* **Time before the first pop** — long enough for the page to be read first
* **Gap time between two pops** — clearly longer than the display duration
* **Maximum of popups** — low, and raise it only if the first one is working
* **Display by** — **Display in order**, with **Continue after page reload** on
## Next steps
* [Visibility and schedule](/samita-countdown-timer-bar/sale-popups/visibility.md)
* [Sale popups overview](/samita-countdown-timer-bar/sale-popups/overview.md)
* [Design and position](/samita-countdown-timer-bar/sale-popups/design.md)
* [Create a sale popup](/samita-countdown-timer-bar/sale-popups/create.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.samita.io/samita-countdown-timer-bar/sale-popups/general-settings.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
