> 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/device-targeting.md).
# Device targeting
Show a countdown on desktop only, mobile only, or both.
**Device targeting** is the last control in the **Display position** section. It decides which devices a countdown renders on.
Device targeting, at the bottom of the Display position section.
## The three options
| Option | Renders on |
| ----------------------------------------------- | ------------------------------- |
| **Display on both desktop and mobile browsers** | Everything. The default |
| **Display only on desktop browsers** | Desktop browsers only |
| **Display only on mobile browsers** | Phones and mobile browsers only |
## When to narrow it
**Leave it on both** unless you have a reason not to. Most of your traffic is likely mobile, and a countdown that only runs on desktop reaches the smaller half of your audience.
**Desktop only** is worth it when a countdown genuinely doesn't work on a small screen — a wide banner design that wraps badly, or a delivery message long enough to push the Add to cart button off the first screenful. Fixing the design is usually better, but restricting it is a reasonable stopgap.
**Mobile only** suits a countdown built specifically for a phone: a compact bar that would look lost across a desktop layout.
{% hint style="info" %}
Different treatment on each device, rather than none? Build two countdowns of the same type — one set to desktop, one to mobile — with the same conditions and different designs.
{% endhint %}
## Cart countdowns have no device targeting
A cart countdown's Display tab carries **Action after time expired** in place of the position and device controls. A cart countdown always renders on both. See [When the cart timer expires](/samita-countdown-timer-bar/cart-countdown/when-time-expires.md).
## Checking it
The reliable test is a real device. Narrowing your desktop browser window changes the layout but doesn't necessarily change what the app treats as a mobile browser, so a countdown set to mobile only may still not appear in a narrow desktop window — that's expected.
## Next steps
* [Display position](/samita-countdown-timer-bar/where-countdowns-appear/position.md)
* [Display conditions](/samita-countdown-timer-bar/where-countdowns-appear/conditions.md)
* [Design a countdown](/samita-countdown-timer-bar/design-and-translation/design.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/device-targeting.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.
