Starters

Starters is the second engagement widget that renders inside your page rather than against a corner of the viewport, using the same inline mount mechanism as the button, carrying more inside it. Where a button is a single labelled control, Starters is a small card: a heading, up to three of your site's starter questions as tappable chips, and a free-text field so a shopper can ask something else. Tapping a chip or sending the free-text field 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, with the same three modes as the button. See Place an inline button on your pages; everything on that page about the three modes, the four-second window and the mount check applies to Starters unchanged.
2. A heading. Required, in at least one language. The editor refuses to save a draft without one: Starters has no icon-only fallback the way a chat bubble does, because the heading is what tells a shopper what the questions below are about.

What you configureCopy Anchor Link

On the Content tab, Heading: up to 60 characters, one row per language enabled on your site, at least one of them filled. The field is the same shopper-facing text a button's label is; it's just presented and hinted as a heading here, since it reads as a static title rather than button text.

A shopper gets the heading for their own language, falling back to your site's default language. If neither is filled, Starters doesn't render on that page at all: same rule, same reasoning as the button's required label.

Below it, Placeholder: the grayed-out text shown in the free-text field before a shopper types anything, translatable per language. Leave a language empty and it falls back to your own default-language translation if you've filled one in, then to iAdvize's built-in default ("Ask a question…"), the same fallback the question bar's placeholder uses.

Under that, the Content tab tells you how many questions are in your site's library and links to Manage questions: the same starter-question library the welcome screen, question bar and chat bubble already draw from. There's no on/off switch here: showing the resolved chips is what this format is, not something you opt into. If your library currently has no question matching the page a shopper is on, the chip row is simply absent. The heading and the free-text field still render (see When there's no matching question below).

On the Display tab, the mount point and the page types. See Place an inline button on your pages. There's no width or alignment control: Starters always renders at the full width of its mount container.

On the Design tab, the same appearance fields as a chat bubble or a button (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. Because the widget carries two visually different regions, one field does double duty: Background colour and Icon and text colour paint the heading's icon chip the way they'd paint a button, while the free-text field keeps a neutral bar and puts the brand colour on its send button instead, the same reasoning the question bar already applies ("a saturated input field harms the legibility of the shopper's own typed text"), reused here for Starters' own field. Starters' Size defaults to Medium (56 px), matching the chat bubble and the button.

What it doesn't haveCopy Anchor Link

• No "First message." A button can pre-fill and send a sentence on click; Starters has no equivalent field. Its two ways to start a conversation (a chip, or the free-text field) already carry the shopper's own words.
• No width or alignment. A card carrying a heading, a chip row and a free-text field has no single "content-fitted" size the way a single button's label does, so the choice isn't offered: Starters is always full width.
• No "Show on all pages." Like the button, an inline widget needs page types you pick. See An inline widget needs page types.
• No font field, for the same reason as the button: it renders in a shadow root that inherits your page's font for free. See Style engagement widgets with CSS.

When there's no matching questionCopy Anchor Link

Your starter-question library resolves questions per page type and per language, with no cross-language fallback. When nothing resolves for the page a shopper is on, the chip row is left out of the widget entirely: no empty gap, no placeholder chips. The heading and the free-text field stay exactly as they are, because the free-text field always works: a shopper can ask anything, whether or not you've written a chip for that page.

That also means a Starters widget can be reported Live in the widget list on a page where your library currently has no matching question. It's telling the truth: the widget does render there, just without chips that day. Check the editor's preview and the starter-question library's own per-page-type coverage if you want to know where chips will actually show up.

What a shopper getsCopy Anchor Link

• Tapping a chip, or sending the free-text field, opens the conversation panel and sends that text as the first message: the chip's question, or whatever the shopper typed.
• The heading and its icon are not a click target. Only the chips and the free-text field open the conversation; tapping the heading does nothing. Nothing about it looks clickable either: no button styling, no hover state.
• Starters stays where it is while the panel is open, exactly like the button. Hiding it would collapse its box and shove your page around on every open and close.
• Every chip carries the AI disclosure, the same way it does on the welcome screen, question bar and chat bubble. The free-text field doesn't carry disclosure text of its own: it's the same input control the question bar already uses, which doesn't either.
• It's counted. When it scrolls into view, the tag records that this widget was seen, once per widget per browser-tab session. See Web tag performance.
• Its chips are measured. Each chip shown in the card counts as an impression for that question, and a tap on a chip counts as a click. They appear under Starter questions in the Engagement report's By starter question table, on each question's page, and in the totals on the Questions list. Typing in the free-text field records no question click.

The dashboard preview shows appearance, not placementCopy Anchor Link

The editor's Template scene draws Starters 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 Starters appears at its real mount point. That's also what feeds the mount check.

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