Starters: questions and a free-text field, inside your own page

Starters is a new engagement widget format, the second one that renders inside your own page rather than docked to a corner, alongside the inline button. It combines three things in one 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 entirely. Tapping a chip or sending the field opens the conversation panel with that text as the first message.

What's in the cardCopy Anchor Link

• A heading, required in at least one language, the same rule as the inline button's label: nothing renders without it. It's a plain title, not a button; only the chips and the free-text field actually open the conversation.
• Up to three question chips, resolved from your site's starter-question library for the page type and language a shopper is on: the same library and the same resolution the welcome screen, question bar and chat bubble already use. There's no toggle to turn this on: showing the resolved chips is what the format is. If your library has nothing for that page, the chip row is simply left out (no empty gap, no placeholder chips), and the heading and free-text field still work.
• A free-text field, the same input-and-send control the question bar uses, with its own translatable placeholder.

Same mount points as the button, none of its width controlCopy Anchor Link

Starters uses the same three mount modes as the button (a custom element, a marked element, or a CSS selector), ranked the same way, with the same four-second watch window and the same mount check on the Display tab.

One thing it doesn't offer: width or alignment. A card carrying a heading, a chip row and a free-text field has no single "content-fitted" size, so Starters always renders at the full width of its mount container.

One honest limit: no zero-shift claimCopy Anchor Link

The inline button can promise zero layout shift when you reserve its mount point, because its box is fixed once configured. Starters can't make that promise in any mount mode: whether the chip row renders depends on what your library resolves for that page and language, so the card has two possible heights instead of one fixed size. That's a stated property of the format, not a bug. See Web tag performance for the full picture.

The tag's byte ceiling moves againCopy Anchor Link

The assistant bundle's transferred ceiling stays at 9 KB gzip (now measuring 9 051 B, 165 bytes of headroom), and its uncompressed ceiling rises 26 KB → 28 KB (now measuring 27 905 B). Starters reuses the button's mount mechanism and the question bar's own input-and-send control rather than adding new equivalents (that reuse is what kept the transferred figure nearly flat), but its own markup (a non-interactive header, a reused chip stack and input bar, wired per widget) still added real uncompressed bytes. Full figures on the tag performance page.