Skene
Product docs

Product documentation

Learn how to use Skene: workspaces, sources, milestones, widgets, and analytics.

~5 min read

Analytics & insights

Once your widget is live, Skene tracks how users move through onboarding milestones. This guide covers key metrics, navigation, and how to use insights for improvement.

Overview metrics

Unique users

Distinct users who interacted with the widget during the selected period

Completion rate

Percentage who completed all milestones in a lifecycle

Time-to-value

Average time from first interaction to completion

You can pivot these metrics by time window (7 or 30 days) and by source.

Milestone funnels

For each source, Skene shows a funnel of milestone completions from first to last. This helps you see where users drop off.

  • Sharp drops = good candidates for clearer copy or additional support
  • Stuck on last step = consider if it's too heavy or belongs elsewhere
  • Compare funnels before and after changes to measure impact

Per-source views

With multiple sources, filter analytics to a single product area. Compare onboarding for your main product vs. a separate SDK or add-on.

Anonymous vs. identified users

By default, Skene uses anonymous identifiers stored in the browser. You can see onboarding progress without integrating your auth system.

Want richer analysis? Pass a stable user ID when embedding the widget. Skene will associate milestone progress with that ID.

The improvement loop

Treat analytics as the start of an improvement loop, not just a dashboard to look at.

1

Identify low completion or long TTV

2

Adjust copy, add docs, or split steps

3

Rebuild and republish widget

4

Watch metrics for impact

For tactical ideas on which changes to try, see the PLG playbooks.

Analytics look wrong or empty?

  • Widget is published and embedded on pages users actually visit
  • Time window includes days when users were active
  • Ad-blockers or privacy extensions not blocking test users
  • Filtering by the correct source in analytics views

For persistent issues, see Troubleshooting.