Login
Start free trial

Contextual help

In-app tooltips without code.

Explain any element in place. Pick the element in the visual editor, write the hint, choose a pulsing hotspot or a hint on hover. Page rules and audience decide where it shows.

4.6/5 on G2
Trusted by 4,500+ teams worldwide
Start free trial
Book a demo
Workspace nameAcme
Bug reportingEnabled
See how to report a bug.
Install the SDK, open the editor on your app, place the first tooltip.
Start free trial
Trusted by 4,500+ teams
One hint, on the exact control. A tooltip answers the small question before it reaches support. It links to the help article when more is needed.

Built in the visual editor.

Mode, target, pages, audience.
A pulsing hotspot with your icon and color, or the hint on the element itself when the user hovers.
A CSS selector or a data-gleap-tour anchor, page rules and audience conditions. Group tooltips per screen.
What a hint cannot cover, Kai Support answers from your knowledge base in the same widget, or offers a tour.

Need a sequence? Use a tour.

Tooltips explain one thing. Tours walk through several.
A product tour anchors steps to your interface and advances on Next, a click or an input. Use the visual editor and shared audience targeting; tours also support event triggers.
See product tours

Manage campaigns in one place.

Tooltips 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.

Tooltips your agent can draft.
Through the Gleap MCP, an AI agent places tooltips on elements from your code and limits them to the right pages and people. If the event it needs is not tracked yet, it gets the tracking code for your SDK.
See the MCP server
Tickets, tours and tooltips in one dashboard.
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 tooltips
What is tooltip software?
Tooltip software adds contextual hints to elements of your web app without changing its code. In Gleap, a tooltip is attached to an element through a selector, shows as a hotspot or on hover, and follows page rules and audience conditions. You place it in a visual editor with the SDK installed.
How does a Gleap tooltip appear to the user?
In one of two modes. Hover hotspot adds a small pulsing marker beside the element, with your icon, color and position; the hint opens when the user hovers it. Hover element shows the hint when the user hovers the element itself, with no marker. The tooltip is a white card with an arrow, and it can contain text, links, images and video.
Do we need a developer to add tooltips?
Only once. A developer installs the Gleap JavaScript SDK; after that, your team opens the visual editor on your site, picks the element and writes the hint. For markup that changes often, add a data-gleap-tour attribute so the anchor stays stable. See the tooltip setup guide.
Can we choose which pages and users see a tooltip?
Yes. Each tooltip group has page rules and audience conditions built from contact attributes, tags and events. Without page rules, matching elements on other pages also receive the tooltip, so set both the selector and the pages.
Are tooltips triggered by events or a frequency?
No. Tooltips use page and audience matching and appear whenever the element is on screen for a matching user. Use a product tour or an info card when a message should appear once after an event.
Does a tooltip editor need access to our code?
No. The editor runs on your live site through the SDK and stores selectors, content and rules in Gleap. Nothing is written to your repository, and the SDK renders tooltips at runtime.
Do tooltips work in native mobile apps?
No. Tooltips are a JavaScript SDK feature for websites and web apps, built on hover and DOM selectors. In native iOS and Android apps use in-app banners, info cards, checklists, news, surveys and push notifications instead.
What happens when we redesign a page?
Review the selector, position and page rules after the change. A selector that no longer matches cannot anchor the hint, which is why data-gleap-tour attributes are the safer anchor.
How are tooltips different from tours, checklists and info cards?
A tooltip explains one element on hover. A tour walks through a sequence of steps. A checklist lists tasks with actions and progress. An info card is a modal with media and a button. They share audience rules and customer records, and tooltips and tours share the visual editor.
What happens when a tooltip is not enough?
The user asks in the same widget. Kai Support answers from your knowledge base, can offer a tour, and brings your team in when needed. A report of a broken control becomes a ticket with session replay, which is how Gleap closes the loop.
Switching from Chameleon or UserGuiding?
Gleap fits when tooltips should live in the same widget as tours, support and feedback, on one customer record. Compare Gleap vs Chameleon, Gleap vs UserGuiding and Gleap vs Whatfix.
Can AI agents create tooltips?
Yes, as drafts. An agent connected to the Gleap MCP server places tooltips on CSS selectors it knows, for example from your code, and limits them to pages and people with page rules and audience rules. When the audience needs an event your app does not track yet, the agent gets the tracking code for your SDK. Check the draft in the tooltip builder before you publish.
Which plan includes tooltips?
Tooltips 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 right hint, right on the element.
Start free trial
See pricing
4.6/5
on G2