> 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/where-countdowns-appear/overview.md). # Display overview How the app decides which pages a countdown appears on, and where on the page it lands. Every countdown has a **Display** tab, and it answers two separate questions: 1. **Who and where?** — the **Conditions** section narrows the countdown to certain products, pages, customers, languages, or countries. 2. **Where on the page?** — the **Display position** section puts it somewhere, either automatically or at an exact spot you choose. Both have to be satisfied. A countdown with the right conditions but no position has nowhere to render; one with a position but conditions that never match renders nowhere.

The Display tab of a countdown showing the Conditions section above the Display position section — The Display tab: conditions first, then position.

## The four pages to know


Display position	Automatic placement on product pages, and where exactly it lands.	Display position
Display conditions	Target products, collections, pages, customers, languages, countries.	Display conditions
Place a countdown with a shortcode	Put a countdown anywhere the automatic placement doesn't reach.	Place a countdown with a shortcode
Device targeting	Show a countdown on desktop only, mobile only, or both.	Device targeting

## Two ways to place a countdown **Automatic.** Tick **Product page** under **Show countdown on** and the app finds the Add to cart area on each product page and puts the countdown just below it. No theme editing, and it follows your theme's layout. **Exact.** Copy the **Shortcode** from the Display tab and paste it into a **Samita Countdown** app block in your theme editor. The countdown renders precisely where you put that block — a homepage section, a collection banner, above the header. You can use both on the same countdown. Most stores start with automatic placement and reach for the shortcode when they want the countdown somewhere else as well. ## Cart countdowns are different A cart countdown places itself at the top of the cart form, on both the cart page and the cart drawer, whenever the cart has items. Its Display tab carries no position or device options — instead it has **Action after time expired**. See [When the cart timer expires](/samita-countdown-timer-bar/cart-countdown/when-time-expires.md). ## The order things are checked When a shopper loads a page, for each of your active countdowns the app checks: 1. Is the app embed on for this theme? If not, nothing happens at all. 2. Is the countdown **Active**? 3. Do its **Conditions** match this page, this product, this customer? 4. Does its timing say it should be visible right now? 5. Is there somewhere to put it — an Add to cart area on a product page, or a shortcode block? Every one has to pass. When a countdown doesn't appear, working down that list finds the reason — see [Countdown not showing](/samita-countdown-timer-bar/help/countdown-not-showing.md). ## Next steps * [Display position](/samita-countdown-timer-bar/where-countdowns-appear/position.md) * [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md) * [Place a countdown with a shortcode](/samita-countdown-timer-bar/where-countdowns-appear/shortcode.md) * [Countdown not showing](/samita-countdown-timer-bar/help/countdown-not-showing.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/where-countdowns-appear/overview.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.