> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/global-sections/footer-group/flyout.md).

# Flyout

Set up the Flyout slide-in panel with a persistent tab, promo codes, countdown timers, and promotional content triggered by scroll depth.

A compact promotional panel that slides in from the corner of the screen. Less intrusive than a full popup — visitors can keep browsing while the flyout is visible. Supports the same content as Popup: newsletter forms, promo codes, countdown timers, and more.

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FF5TIwAaKnOT3hUyOE6Qx%2FGroup%202%20(37).jpg?alt=media&amp;token=6263b27e-db1d-40c7-ab09-06ee4de89775" alt=""><figcaption></figcaption></figure>

***

### How to find

**Theme Editor → Footer group → Flyout**

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FiffUXli2BVAuFKqdJtVZ%2FGroup%202%20(40).jpg?alt=media&amp;token=3ca801da-f7eb-4e02-82cc-85b281c3570d" alt=""><figcaption></figcaption></figure>

***

### Display rules

| Setting                      | Options                                                            |
| ---------------------------- | ------------------------------------------------------------------ |
| Show                         | After scrolling 25% / 50% / 75% / 100% of the page                 |
| Frequency                    | Once, Every 6 hours, Every day, Every 3 days, Every week, No limit |
| Show on home page only       | Toggle                                                             |
| Disable for registered users | Toggle                                                             |
| Position                     | Left or Right                                                      |

Unlike Popup which triggers on a time delay, the Flyout triggers based on **scroll depth**. This means it appears when a visitor has already engaged with your content — a much better moment to present an offer.

{% hint style="success" icon="sparkles" %}
**Tip:** Use **No limit** frequency while testing in Theme Editor — other settings won't trigger inside the editor.
{% endhint %}

***

### Sticky tab

The Flyout has a unique feature that Popup doesn't — a **Sticky tab**. A small persistent tab that stays visible on the edge of the screen after the flyout is closed. Visitors can click it to reopen the flyout at any time.

| Setting       | What it does                                                                                             |
| ------------- | -------------------------------------------------------------------------------------------------------- |
| Icon          | 80+ built-in icons (arrows, shopping cart, envelope, star, etc.), or **Custom** to upload your own image |
| Label         | Text displayed on the tab (e.g., "The next show")                                                        |
| Position      | 7 placement options — left/right side, left/right bottom, bottom left/center/right                       |
| Invert colors | Swap the tab colors for contrast against your page background                                            |

<figure><img src="https://795663372-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6DraMvJNYYlFJqlho1aV%2Fuploads%2FSxRb4mDCis5a7dtEhxan%2FGroup%202%20(41).jpg?alt=media&amp;token=ece5ae79-c39c-44b0-97cf-faf6e0e828f1" alt=""><figcaption></figcaption></figure>

{% hint style="success" icon="lightbulb" %}
**Tip:** Use the sticky tab for ongoing promotions — a discount code or free shipping offer that visitors can access whenever they're ready, without being interrupted again.
{% endhint %}

***

### Popup vs Flyout

|               | Popup                                    | Flyout                                |
| ------------- | ---------------------------------------- | ------------------------------------- |
| Trigger       | Time delay (immediately to 1 min)        | Scroll depth (25% to 100%)            |
| Appearance    | Full overlay, centered                   | Slides from the side                  |
| Intrusiveness | High — blocks the page                   | Low — page stays visible              |
| Sticky tab    | No                                       | Yes                                   |
| Best for      | First-time visitor offers, announcements | Ongoing promotions, newsletter signup |

***

### Related

* [Popup](https://staylime.com/docs/avante-themes/global-sections/footer-group/popup.md) — full-screen overlay alternative
* [Announcement Bar](https://staylime.com/docs/avante-themes/global-sections/header-and-navigation/announcement-bar.md) — persistent top banner


---

# 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://staylime.com/docs/avante-themes/global-sections/footer-group/flyout.md?ask=<question>&goal=<user_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.
