Login
Start free trial

Feature announcements

In-app info cards for feature launches.

Image, text and a next step. An info card is a modal with one or more steps, each with a title, text, an image or video and a button that opens a tour, a help article, a checklist or a link. Trigger it by event and audience.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
Start free trial
Book a demo
Write the steps, pick the audience, publish.
Start free trial
Trusted by 4,500+ teams
Room for the introduction. Some changes need a picture and two sentences. An info card gives them a focused moment, then hands over to the feature.

Steps, media, a button.

Built in the editor, previewed live.
Each step is one page with its own media and text. Set the Next and Done labels and whether users can close early.
Open a link, a help article, a news item, a checklist, a tour, a conversation or a custom action.
Choose an event trigger, audience rules and frequency. Views are counted per card.

A compact notice? Use a banner.

Inline or floating, one line and one action.
A banner stays visible while the user works. Use it for a launch line, an incident notice or a nudge, and link to the release note for the details.
See in-app banners

Manage campaigns in one place.

Info cards next to tours, checklists, banners and emails.
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.

Info cards your agent can set up.
Through the Gleap MCP, an AI agent writes the cards with images and buttons, targets them by event and contact attribute, and checks the reach. The draft waits for your review.
See the MCP server
Everything is in the same place.
Tridonic runs tickets, surveys, AI support, product tours and tooltips from one Gleap dashboard instead of switching between separate tools.
Elif Kavas
Digital Customer Experience Platforms Specialist, Tridonic
About info cards
What are in-app info cards?
Info cards are in-app modals with one or more steps, used to introduce a feature, welcome a user or explain a change. Each step has a title, rich text, an optional image or video and a button with an action. Gleap calls them info cards in the dashboard; the documentation also uses the term modals.
Can an info card have several steps?
Yes. Add steps in the editor and drag to reorder. Each step is one page of the modal with its own media and text. You set the Next button text, the Done button text and whether a close button appears before the last step.
What can the button open?
A URL, a help article, a news item, a checklist, a product tour, a conversation workflow, a feedback form or a custom action that your app implements. You can also close the widget when the action runs.
Can we control who sees a card and when?
Yes. An info card supports an event trigger with optional delay, audience conditions from contact attributes, tags and events, page rules, and a frequency of once or every time. 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. See the event-based messaging guide.
What can we measure?
The card's detail view counts views. Pair it with the product event you want users to reach and with feedback from the widget to judge whether the introduction helped.
Does the card need a developer?
Only for the one-time SDK install. Info cards are delivered through the Gleap SDK, and your team edits and publishes them in Gleap. Custom actions and tracked events need engineering work.
Do info cards work in native mobile apps?
Yes. The iOS and Android SDKs show info cards as well as the JavaScript SDK. To reach people outside the app, use push notifications.
When should we use an info card instead of a banner or a tour?
Use an info card when the change needs a picture and a paragraph. Use a banner for a one-line notice that stays visible while the user works. Use a tour when the user should follow steps on the interface itself, and a tooltip to explain one control.
Can AI agents create info cards?
Yes. An agent connected to the Gleap MCP server drafts info cards with titles, text, images and buttons, targets them by trigger, page, events and contact attributes, and previews how many people match. When an event it needs is not tracked yet, it gets the tracking code for your SDK. Drafts wait for your review.
How do info cards fit the Gleap platform?
They share the customer record and the widget with support. A question after the card goes to Kai Support, and a report of something broken becomes a ticket with session replay. See how the platform shares context and how Gleap closes the loop.
Which plan includes info cards?
Info cards are part of outbound messaging, included from Team ($149 per month, billed annually), with unlimited seats. See pricing for plan details.
Kai Support First level support
The introduction the feature deserves.
Start free trial
See pricing
4.6/5
on G2