The widget list
Read what is actually running on your site: four honest statuses, two views, and the row actions that put a widget online, copy it, or remove it.
The list answers one question: what is actually running on your site right now.
Each row shows the widget's own appearance as a thumbnail (its real colour, size and shape, the same values your storefront renders), its name and format, where it sits, which pages it targets, its status, and when it last changed.
The thumbnail and every other configuration column show the widget's effective version: the one that is live, or its draft if it has never published. A widget that is live on one version while you work on the next shows the live one, because that is what the list is about.
Last 7 days: one performance signal, three states
Each row also carries a Last 7 days column: that widget's start rate over the last 7 days (a small trend line and the change against the previous 7 days), or one of two words instead of a number:
- No data: the widget recorded no views in the last 7 days. This covers everything from "just created" to "published but nobody's seen it yet"; there's no distinction drawn here between those.
- Never appeared (in amber, with a session count): the widget recorded mount failures but zero views: a configuration problem, not a quiet week. This only applies to an inline button or Starters widget whose mount point wasn't found on the page. See Widgets that failed to mount and Place an inline button on your pages.
A bare 0% is never shown for either failure case: the column always says in words whether the widget was never seen at all, or seen and simply not converting, because a chart alone can't tell those apart. Click through to a widget's own Performance tab for its full funnel over any date range, not just the last 7 days.
Status has four values, not two
The switch is what you control; the label beside it is what your visitors get:
| Status | What it means |
|---|---|
| Live | Active, targeted, and published. Shoppers see it. |
| Never published | Nothing has ever been published for this widget, so there is nothing to serve, whatever else is configured. See Drafts, publishing and versions. |
| Needs setup | Active and published, but no page type is selected and Show on all pages is off, so it renders nowhere. See Why a new widget isn't live yet. |
| Offline | Switched off. |
Only one is shown at a time, and they are ordered by which one to act on first: switched off outranks everything (there is no point picking page types for a widget you have not turned on), and never-published outranks needs-setup.
Never published is not an error. It is the state of every widget between being created and being published for the first time, so it reads as progress rather than as a fault.
A row can also carry a discreet Draft waiting marker next to its status. That is a different fact from the status: a widget can be perfectly Live on one version while newer, unpublished work sits in a draft. The marker is there so a colleague sees the work in progress before opening the widget: a widget has one draft, shared by everyone in your organization, so the last save wins.
Flip the switch on a row to put a widget online or take it offline without opening it. Taking a Live widget offline asks you to confirm, because shoppers stop seeing it straight away; every other change applies immediately.
Search, filters and views
Search by name, filter by format or status, and sort by name, status or last change. Your filters and your chosen view live in the page's address, so a filtered list survives a refresh and can be shared as a link.
The Placement column names where a widget docks: "Bottom right", "20/20 px". An inline button reads simply Inline: its position is a point in your own markup, which this column can't name and won't guess at.
Two views, same widgets. List is the default on a wide screen and shows every column. Gallery shows each widget as a card standing on a neutral page, in the corner or along the edge it docks to. The gallery shows the region, never the exact offsets: a card is too small to render a 24px and an 88px offset differently without lying about them, so the numbers stay on the card as text.
Below 768px viewport width, gallery is the only view. Six columns can't be read on a phone, so the view switch is hidden and the gallery is what you get whatever the address says: a ?view=list link shared from a desktop opens as a gallery there. The address itself isn't rewritten, so that same link is a list again on a wide screen, and widening the window past 768px mid-session brings the list back immediately.
Row actions
The ··· menu on each row offers Edit, Duplicate, putting the widget online or offline, and Delete.
Duplicate copies everything (look, placement, targeting) into a new widget that starts offline and named after the original, which is the quick way to make a variant (a second bubble for another page type, say) without re-entering a dozen fields. Anything the original inherits from your site's branding stays inherited in the copy, so a rebrand still reaches both.
If the tag isn't running, nothing on this page matters
When no tag activity has been recorded for your site in the last 7 days, a notice sits above the list. Until the tag is live on your pages, no widget appears to anyone, whatever its status says. A brand-new site with no visitors yet shows the same notice: it reports that we have seen no activity, not that your tag is missing. See Embed the assistant.
Multiple widgets on one site
You can enable more than one widget on the same site, of any format or a mix. Each renders as an independent surface with its own placement and page-type allow-list, including two chat bubbles docked to opposite sides, a bubble and a question bar shown together, or a floating widget and an inline button on the same product page.
Nothing prevents two widgets from landing on top of each other, but you're told when it would happen. The list names both widgets above it when two Live widgets share a region and can appear on the same page; the editor draws your site's other live widgets as dashed outlines in the preview and warns in its footer. It is a warning, not a rule: you can save and publish either way. Give them different offsets or a different stacking order to clear it.
The overlap check compares published geometry against published geometry. Another widget's unpublished draft is not on your shopper's page, so it is neither drawn nor counted as a collision.
Inline widgets are outside that check entirely: they have no corner of the viewport to collide in, so they are neither drawn as outlines nor compared. What protects a mount point instead is that two live widgets on one site can't claim the same slot. Two widgets aimed at the same CSS selector are nobody's to stop but yours.
Delete a widget
Delete a widget from the ··· menu on its row, or from the bottom of the General tab on its own page, then confirm. It's a soft delete: deleting stops it from rendering on your site immediately (you don't need to disable it first) and removes it from the list, along with its version history. The deletion can't be undone from the dashboard.
The confirmation says more when shoppers can currently see the widget: how many versions go with it, and an offer to switch it off instead, which stops it just as fast and keeps the work.
Engagement widgets
The chat bubble, the question bar, the inline button and Starters: the surfaces that invite shoppers into a conversation on your site, and how they get from created to live.
Add a widget
Pick a format from the catalog. Selecting a card creates the widget straight away, as an unpublished draft that reaches nobody until you publish it.