Show an in-app banner

Updated May 22, 2026

You have something short to say to everyone on your site — a sale, a maintenance window, a new feature — and you do not want to wait for people to open the chat. A banner does that. You write one line, choose how it looks, decide who sees it, and publish. Nothing to install.

The three banner styles

The Style field decides where the banner sits:

Style Where it appears Good for
Inline A card on the widget's home screen, among the other cards. The visitor sees it after opening the widget. Announcements that can wait until someone comes looking.
Floating full width A bar across the page, outside the widget. Impossible to miss. Urgent notices, deadlines, site-wide warnings.
Floating pill A small rounded badge near the chat bubble, visible without opening anything. Gentle nudges — "New feature", "Sale ends today".

1. Create the banner

Go to Marketing → Engagement → Banners and click New Banner in the top right. Choose Blank Banner to start from scratch, or pick one of the ready-made templates.

2. Fill in the General section

  • Name — for your own list. Visitors never see it.
  • Widget — which chat widget shows the banner. See "Which visitors will see it" below.
  • Published — leave it off until the banner is finished.

3. Write the content and choose the look

Content is the banner's text. Keep it to one line — every style is short and wide, and long text simply gets cut down to an unreadable strip.

The rest of the editor is styling, and a live preview on the right updates as you go:

  • Background — a single colour, or a gradient of up to five colours with an angle between 0 and 360 degrees. New banners start on Yaplet's default yellow; change it to something of yours.
  • Layout — the style from the table above, the corner rounding, and whether to show a close button so visitors can dismiss the banner.
  • Border — optional. Width and colour.

4. Decide what a click does

The Action section turns the banner into a button. Pick an Action type, then write the Action text that appears on it:

  • No action — the banner is just a notice.
  • Start conversation — opens the chat, optionally starting one of the brand's chat workflows.
  • Start survey — opens one of your surveys.
  • Show feedback form — opens one of your forms.
  • Open URL — sends the visitor to an address you choose.
  • Show knowledgebase article — opens one of your help articles inside the widget.
  • Show news article — opens one of your news posts inside the widget.

5. Set the trigger and the audience

Scroll down to the Trigger section and click it. Banners use the same trigger settings as every other engagement campaign: which event shows the banner, on which pages, to which visitors, and how often. Full details in Trigger rules and Frequency caps.

A banner with no trigger conditions never appears — the editor says so in the Trigger box.

6. Publish

Turn Published on and click Save. Matching visitors start seeing the banner straight away.

Which visitors will see it

Every banner has a Widget field. A chat widget belongs to one brand, and a brand has exactly one chat widget, so this field decides whose visitors get the banner. With a single brand there is nothing to choose — new banners are attached to your widget automatically.

One consequence worth knowing before you ever delete a widget: deleting a chat widget deletes its banner campaigns with it. The brand itself survives — its public address, its knowledge base and its products all stay — but the banners are gone and cannot be recovered. Deleting the widget also deletes everything that happened through it — every conversation, message, visitor record and session replay for that widget. Only delete a widget whose history you are sure you no longer need.

Reading the results

Open the banner and click Reports. Four tabs: Successfully sent, Failed to send, Waiting to be sent and Clicked. The Clicked tab also records how long the visitor took to click. See Read engagement campaign analytics for what each tab means.

What's next?

Need finer targeting? Read Trigger rules. Want to walk someone through a feature rather than just announce it? Build a product tour.

Did this article answer your question?