Feature referenceHistory and insights · 06 of 06

History and insights

Usage analytics

Usage analytics measures the path from an eligible page view to a visible Stand invitation, an activation, a started chat, and conversation time.

Availability
All plans
Configured in
Stand app → site, profile, Stand-in, or team activity widgets
Category
History and insights
Reference status
Current

Before you begin

Plan availability: All plans.

Prerequisite: Recorded widget or conversation activity in a scope the signed-in member can access.

Key boundary: Analytics are operational counts, not unique visitors or marketing attribution. Current UTC periods are partial.

01

Recorded metrics

MetricMeaning
OpportunitiesPage loads or contexts where Stand had an opportunity to be shown.
Widget showsTimes a Stand invitation or widget became visible.
ActivationsReported chat opens before a conversation exists, or the first valid submission in an always-visible inline composer.
Chat startsNew visitor conversation sessions created.
MinutesAccumulated duration of closed conversations, displayed in whole minutes.
02

Time views

  • Hourly view covers the last 24 hours and refreshes the current-hour data every 60 seconds.
  • Daily view covers 28 UTC days.
  • Weekly view covers 52 UTC weeks.
  • The current hour, day, or week is partial; charts label this rather than projecting it as a completed period.
  • All period boundaries use UTC and can differ from the viewer’s local calendar.
03

Where scope comes from

  • A Site activity widget reports that site.
  • A rep profile reports the rep’s activity.
  • Stand-in views can report an AI Stand-in scope.
  • Owners can inspect broader organization and member scopes where provided.
  • Non-owners see their own permitted scope rather than unrestricted organization-wide analytics.
04

How to read the funnel

The metrics describe successive but not perfectly interchangeable events. A page can create an opportunity without showing the widget, a widget can show without being activated, and an activation may not start a chat if availability changes or the visitor leaves. Custom visitor API clients must report their own activation events; creating a conversation does not infer an open.

Use the same metric and scope when comparing periods. A site-level show count and an organization-level chat-start count do not form a valid conversion rate.

05

When conversation time is counted

Minutes are recorded when a visitor or rep ends a conversation, a Stand-in finishes it, idle cleanup closes it, or a visitor submits an offered email follow-up. The duration runs from the recorded start to the recorded close, including idle time, and belongs to the UTC hour, day, and week containing the close. It is not split across periods. Test conversations are excluded.

06

Limitations

  • Counts are event totals, not deduplicated people, accounts, or browser sessions.
  • Minutes are based on recorded session duration and are not billing units.
  • Analytics do not expose transcript contents; use History for qualitative review.
  • Live counts are saved periodically, normally once per minute. A process or cache failure can lose recent statistics; missing past events are not reconstructed.
  • Short delays can occur before recent events appear, and unavailable data is shown as unavailable rather than silently replaced.