The inline button

A button is the first engagement widget that renders inside your page rather than against a corner of the viewport. It's a labelled control you place where the question comes up (under an add-to-cart, beside a size table, in a cart summary), and activating it opens the conversation panel.

Create one from Engagement → Widgets → New widget, in the catalog's Inline section. Everything about drafts, publishing, versions and the on/off switch works exactly as it does for the other formats.

Two things it needs that a floating widget doesn'tCopy Anchor Link

1. A mount point. Its position is a point in your own markup, and you choose how the tag finds it. That choice is the one decision on this page worth taking seriously. See Place an inline button on your pages.
2. A label. Required, in at least one language. The editor refuses to save a draft without one.

A label is optional on a chat bubble because a round control docked to a corner reads as "chat" with no text. A control sitting inside a product page, among your own buttons, does not: an unlabelled one is indistinguishable from decoration and tells the shopper nothing about what pressing it does.

What you configureCopy Anchor Link

On the Content tab, Text: up to 60 characters, one row per language enabled on your site, at least one of them filled. (The optional First message sits under it.)

A shopper gets the text for their own language, falling back to your site's default language. If neither is filled (you translated Dutch, the shopper resolves to German, and your default language is English), the button doesn't render on that page at all. An empty control among your own buttons says nothing about what pressing it does, so nothing is better than something unlabelled. The editor's language rows mark an empty one as Missing on a button, where the same empty row on a chat bubble reads Icon only.

On the Display tab, alongside the mount point and the page types:

These two decide whether the button reads as part of your interface or as something dropped on top of it: a full-width button under a full-width add-to-cart matches; a content-fitted one beside it doesn't. Alignment has no effect at full width: the editor greys it out and says so, keeping your selection for when you switch back.

On the Design tab, the same appearance fields as a chat bubble (background colour, icon and text colour, size, corners, shadow and the built-in icon), all inheriting from your site's branding until you override them. A button's Size defaults to Medium (56 px), matching the chat bubble rather than the shorter question bar, because it stands next to your own controls.

What it doesn't haveCopy Anchor Link

• No position, no offsets, no stacking order. Its position is its mount point. A stacking rank would be meaningless inside your page's own stacking contexts, so it isn't offered and isn't stored.
• No "Show on all pages". An inline widget needs page types you pick. See An inline widget needs page types.
• No font field. The label inherits your page's font, because the button renders in a shadow root whose host sits in your document. That costs no network request, needs no font-src in your Content Security Policy, and lets the button blend in. To change it, set font-family on the host or on ::part(launcher-label). See Style engagement widgets with CSS.

An optional first messageCopy Anchor Link

A button can carry a First message (optional), on the Content tab under its text: up to 200 characters per language, optional in every one. When it's set, the shopper's click opens the panel and sends that sentence as their first message, in one action, which is what makes a button next to a specific product, size table or delivery block different from a second chat bubble placed lower down the page.

It follows the same language rule as the label: the shopper's own language, falling back to your site's default. Leave every language empty and activating the button just opens the panel, sending nothing.

It rides the tag's existing auto-send path (the same one data-iadvize-message uses on a trigger of your own), so if the panel is still loading, the message is sent as soon as it's ready rather than lost.

What a shopper getsCopy Anchor Link

• Activating it opens the conversation panel, through the same path as your own data-iadvize-open trigger. There is no second way to open a conversation.
• The button stays where it is while the panel is open. A chat bubble and a question bar hide themselves; an inline button doesn't. Hiding it would collapse its box and shove your product page around on every open and close.
• Activating it again while the panel is open does nothing. The panel stays open, and nothing is sent.
• It carries the AI disclosure, like every other surface the tag renders. It's part of the button's accessible name and its title, and no field you set and no CSS you write removes it.
• It's counted. When it scrolls into view, the tag records that this widget was seen, once per widget per browser-tab session. Every widget on the page shares a single request for that. See Web tag performance.

The dashboard preview shows appearance, not placementCopy Anchor Link

The editor's Template scene draws the button centred in the frame, with a line saying "Appearance only, not placement". That's honest rather than lazy: the dashboard cannot read your document, so any position it chose would be a guess rendered as a preview, and you'd discover the truth on your own site, after publishing.

To see where it actually lands, mint a Preview link and switch the scene to Real site: your page loads with your tag active and this draft previewed, and the button appears at its real mount point. That's also what feeds the mount check.

The widget list reports a button's placement as Inline for the same reason: there is no corner and no offset pair for that column to name.