Login
Start free trial

In-app banners for product updates.

Users see the update and act on it in one click.

Book a demo Start free trial

A one-line banner reaches the right users inside your app at the moment it matters and links straight to the place to act. Inline or floating, in your color, targeted by event, page and audience.

★ 4.6/5 on G2 Trusted by 4,500+ teams worldwide

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

Trusted by 4,500+ teams
One message. One next step. A feature shipped, a service is down tonight, a setup is unfinished. The banner says it in a line and links to the place to act.

Style, action, audience.

Everything a banner needs, nothing more.
Inline pushes the page down. Floating overlays it with a shadow. Pick the color, alignment and whether the sender shows.
Open a link, a help article, a news item, a checklist, a tour, a survey, a form or a conversation.
An event or property trigger, audience rules and page rules decide who sees it. Send once or every time.

More to say? Use an info card.

A modal with media and a button.
When the change needs a picture and a paragraph, an info card gives it room. Same triggers, same audience rules, same list.
See info cards

Manage campaigns in one place.

Banners next to emails and push.
Manage formats in one outreach list with their own targeting controls. Publish, pause and review them together.
See all outreach tools

Built for AI agents.

Banners your agent can set up.
Through the Gleap MCP, an AI agent writes the banner, sets its button and color, and targets it by event, page and contact attribute. It checks the reach first, and the draft waits for your review.
See the MCP server
Engagement without per-seat budgeting.
Partfox moved from per-seat tooling to Gleap, integrated custom data in 10 days, and now runs live chat, AI support, bug reporting, feature requests, tours, checklists and surveys on one platform.
Maic Fankhauser
Product Manager, Partfox
About in-app banners
What is an in-app banner?
An in-app banner is a one-line notice shown inside your app or website with an optional action button. Gleap renders it inline, in the page flow, or floating over the interface, in your color, with an optional sender avatar and a dismiss button. Use it for a launch, an incident or a nudge.
How are inline and floating banners different?
Inline banners become part of the page: the SDK moves the page down by the banner's height so nothing is covered. Floating banners overlay the page with rounded corners and a shadow. Pick inline for notices that should stay, floating for a short interruption.
What can the banner's button do?
Open a link, a help article, a news item, a checklist, a product tour, a survey, a feedback form, a conversation workflow or a custom action your app implements. The banner closes after the action.
Can users dismiss a banner?
Yes, when you enable the dismiss button. You also choose the text alignment, the UI color with automatic text contrast, whether the sender shows, and custom CSS if the default style does not fit.
Who sees a banner and how often?
An event or property trigger starts delivery, audience rules from contact attributes, tags and events narrow it, and page rules limit where it appears. The frequency is once or every time the rules match, with optional start and stop dates. A one-off audience or a CSV upload of user IDs shows it to a fixed list of people the next time they open your app.
Do we need engineering work to publish a banner?
Only once. A developer installs the Gleap SDK on the web, iOS or Android; after that, your team writes, previews and publishes banners in Gleap. The banner guide lists the SDK version required.
Do banners work in native mobile apps?
Yes. The iOS and Android SDKs show banners as well as the JavaScript SDK. Page rules apply on the web; in native apps, target by audience and events. To reach people outside the app, use push notifications.
Can a banner serve as a release history?
No, and it should not. Publish news and release notes for the record, then use a banner to point the right audience at the entry.
How are banners different from info cards and tours?
A banner is a line with one action that stays visible. An info card is a modal with media, steps and a button. A tour walks the user through steps on the interface. All share customer records and audience targeting, with delivery controls that depend on the format, audiences and customer records.
Can AI agents create banners?
Yes. Through the Gleap MCP server, an agent drafts banners with their style, color and button action, targets them by trigger, page, events and contact attributes, sets start and stop dates and checks how many people match. If the audience needs an event your app does not track yet, the agent gets the tracking code for your SDK. Drafts wait for your review.
Where do banners fit in the Gleap platform?
They are one format in the outreach list next to emails, push, in-app messages, checklists and tours, and they share the customer record with support. Questions after a banner go to Kai Support in the widget, and a report becomes a ticket with session replay. See the platform, how Gleap closes the loop and AI customer support for SaaS.
Which plan includes banners?
Banners are part of outbound messaging, included from Team ($149 per month, billed annually), with unlimited seats. See pricing for plan details.
Updates users see.
Next steps they take.
Start free trial
See pricing

7 days free. Cancel anytime. Card required. First charge on day 8 unless you cancel.

4.6/5
on G2