> 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/banners/manage.md).
# Manage banners
Find, sort, duplicate, publish, and delete banners from the list page.
**Banners** in the app menu lists everything you've built.
One row per banner, newest first.
## The columns
| Column | What it tells you |
| -------------- | -------------------------------------------------------------- |
| **ID** | The number the shortcode uses |
| **Name** | What you called it |
| **Shortcode** | The snippet to paste, for a banner placed at a custom position |
| **Status** | Active or Draft |
| **Position** | Top, Footer, Sticky, or Custom |
| **Created at** | When you made it |
## Finding one
* **All**, **Active**, and **Draft** tabs narrow the list by status
* The **search** icon filters by name
* The **sort** icon orders by date or name, newest or oldest first
## Working on several at once
Tick the checkboxes and a row of actions appears:
| Action | What it does |
| ----------------- | ------------------------------------------------------------ |
| **Set as active** | Publishes them to the storefront |
| **Set as draft** | Takes them off the storefront, keeping the record |
| **Duplicate** | Copies them, so you can vary one without losing the original |
| **Delete** | Removes them for good |
{% hint style="danger" %}
Deleting can't be undone. If you might want the banner back for next year's sale, set it to **Draft** instead — a draft costs nothing and keeps everything you built.
{% endhint %}
## Editing one
Click a row. The builder opens over the list; close it and you're back where you were.
## Why a banner might not be showing
It has to be **Active**, its [conditions](/samita-countdown-timer-bar/banners/placement.md) have to match the page, it has to be inside its [schedule](/samita-countdown-timer-bar/banners/placement.md), and the shopper must not have closed it already.
The app embed also has to be on. See [Turn on the app embed](/samita-countdown-timer-bar/quick-start/enable-app-embed.md) and [Countdown not showing](/samita-countdown-timer-bar/help/countdown-not-showing.md) — the same checks apply.
## Next steps
* [Create a banner](/samita-countdown-timer-bar/banners/create.md)
* [Where a banner appears](/samita-countdown-timer-bar/banners/placement.md)
* [Banners overview](/samita-countdown-timer-bar/banners/overview.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/banners/manage.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.
