> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Banner

> Banners shown in app and web surfaces - types, targeting, scheduling and navigation.

Banners are promotional tiles shown in the mobile app, on eCommerce pages and in other web channels. You configure them centrally, target them at an audience or a set of stores, and the app fetches whichever ones apply to the customer in front of it.

<Info>
  Your integration only ever **reads** banners. Creating and scheduling them is done by marketers in the Admin Portal — your job is to fetch the right ones and render them.
</Info>

## Banner types

| Type           | Used for                                                    |
| -------------- | ----------------------------------------------------------- |
| `Hero`         | Priority campaigns and featured content, shown prominently. |
| `Partner`      | Partner offers and co-branded promotions.                   |
| `OfferByChain` | Offers scoped to a particular chain.                        |

Each banner carries an image, a navigation action, a priority and a schedule. Priority controls the order when several banners compete for the same slot.

## Lifecycle

```mermaid theme={"system"}
flowchart LR
    D["Draft"] --> P["Published"]
    P --> X["Disabled"]
    X --> P
```

Only published banners inside their scheduled window are returned to your channel. A banner that has expired or been disabled simply stops appearing — there is no separate signal, so do not cache the list indefinitely.

## Targeting

Banners are filtered before they reach you. Two mechanisms combine:

* **Audience** — segments from [Audience — Lobyco Segmentation](/integration/other-integrations/audience-lobyco-segmentation).
* **Chain and store** — location-specific campaigns, so a store-scoped banner only reaches customers shopping that estate.

You do not implement this filtering. Request banners for the customer and render what comes back.

## Navigation

Every banner has an action that fires when a customer taps it.

| Action            | Where it sends the customer                                                                                                         | Use for                                                                                       |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| **Deep link**     | A specific screen or piece of content inside the app. Configured in the banner's metadata and resolved by the app.                  | Anything that already has a home in your app — an offer, a challenge, the customer's profile. |
| **External link** | A URL. Optionally wrapped in an in-app web view rather than handed to the system browser, which keeps the customer inside your app. | Landing pages, partner sites, anything outside the app.                                       |

If you render your own web content in the wrapper, read [Web Content in Mobile App](/integration/other-integrations/web-content-in-mobile-app) first — it covers the constraints that apply inside it.

## Images

Banner images are uploaded through the Admin Portal, stored in Azure Blob Storage and delivered to you as URLs. Various formats and dimensions are supported, so treat the image as arbitrary remote content: size it responsively rather than assuming fixed dimensions.

## API reference

Endpoint documentation for this service: [Banner](/api-reference/communication/banner).