> 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/content.md).
# Popup content and image
Set the heading, text, link, and image on a sale popup.
Everything a shopper reads or clicks in a sale popup comes from the **Component** tab. The app describes it as "Set up what your popup bar says, where it shows up, and how it looks — so it fits perfectly with your store and sales campaign."
The Component tab of the popup editor.
## Heading text
The bold first line. A new popup starts with `🔥 Hurry up! 🔥`.
A popup is small and appears while the shopper is doing something else, so the heading has one job: say what this is in a glance. "Free shipping this weekend" works; a full sentence doesn't.
## Content text
The line underneath. A new popup starts with:
> The Sale is on – Don't miss out on hot deals for a limited time only!
One line is the right length. Two is the maximum before the popup starts to feel like an advert you have to read.
{% hint style="info" %}
Long text can be cut off rather than wrapped, depending on the **Truncate content** setting in [Popup General Settings](/samita-countdown-timer-bar/sale-popups/general-settings.md). Check how your text actually renders at the size you chose.
{% endhint %}
## Link
A popup can be clickable. Set a **Link** and the whole popup becomes a link to it — a collection, a product, a landing page.
The **Open link in new tab** option keeps the shopper's current page open. For a link to somewhere on your own store, leaving it off is usually better: you want them to follow the offer, not accumulate tabs.
Leave the link empty and the popup is purely informational, with only the close button to interact with.
## Image
An optional picture beside the text, which makes the popup feel like part of your store rather than a system message.
| Requirement | Value |
| ------------ | -------------- |
| Formats | PNG, JPEG, JPG |
| Maximum size | 1 MB |
Sizing is set separately on the **Design** tab — **Image size** offers **Small**, **Medium**, and **Large**, with the option of a different size on mobile. See [Design and position](/samita-countdown-timer-bar/sale-popups/design.md).
{% hint style="info" %}
The image is displayed cropped to fill its area, so a picture with its subject near an edge can lose it. Square images with the subject centred survive every size.
{% endhint %}
A popup with no image is narrower and less intrusive — a reasonable choice for a text-only announcement.
## Translating a popup
Like countdowns, a popup's text can be written per storefront language using the language switcher in the editor's top bar. See [Translate countdown text](/samita-countdown-timer-bar/design-and-translation/translate.md) — the flow is the same.
## Next steps
* [Design and position](/samita-countdown-timer-bar/sale-popups/design.md)
* [Visibility and schedule](/samita-countdown-timer-bar/sale-popups/visibility.md)
* [Create a sale popup](/samita-countdown-timer-bar/sale-popups/create.md)
* [Translate countdown text](/samita-countdown-timer-bar/design-and-translation/translate.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/content.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.
