Widget performance
One widget's own funnel: views, opens, starts, its start rate, messages per conversation, and a version-over-version comparison that is explicitly not a controlled test.
Every widget's own editor has a Performance tab in its right-hand panel, right after Versions. Where the site-wide Engagement report answers "how is the site doing," this tab answers "how is this widget doing": its own funnel, on its own selectable date range.
Choosing a range
A date range picker sits at the top, with the same presets and custom-range calendar as the other reports. It remembers its own range independently of the Engagement report's, so changing one doesn't move the other. There's no compare-to-previous-period toggle here; the version comparison below covers that need in a different way.
What it shows
If the widget had no views and no opens in the selected range, the tab shows a single empty state instead of zeroed tiles.
KPIs
- Widget views: sessions where this widget was visible.
- Conversations opened: sessions where the chat panel opened from this widget.
- Conversations started: sessions where the shopper sent a first message.
- Start rate: started divided by views. A dash when the widget had no views in range.
- Messages per conversation: the average number of messages (shopper and assistant combined) across every conversation this widget started in range. A dash when nothing started.
A widget's figures roll up every version that was live during the range, the same way the Engagement report's per-widget table does. Republishing mid-range doesn't split the widget's history in two.
Version comparison
Not a controlled test
This card compares the current live version's start rate against the previous published version's, over two windows of matching length on either side of the publish date. It deliberately shows two numbers side by side and never a winner, a confidence figure, or significance language: seasonality, traffic mix, and catalog changes can all explain a difference on their own. Treat it as a smell test, not proof that the new version is better or worse.
The card is absent entirely for a widget with only one published version: there's nothing to compare yet. It's also independent of the date range picker above: it always measures around the most recent publish, not the range you've selected for the KPIs.
Where this comes from
The Performance tab and the Engagement report's per-widget table read the same underlying figures, computed from the events ledger rather than from any per-conversation field, so an erased conversation never changes a past figure retroactively, even though the conversation itself is gone.
The widget editor
A two-column workshop: the widget standing on a page-sized storefront on the left, seven tabs on the right, and one bar across the top that says what shoppers get.
A/B testing a widget
Run your draft against your live version with real traffic split between them, and get a verdict you can trust: the traffic floor, the detection limit, and the one-session-at-a-time limitation to know before you start.