Guide analytics

Understand how people use your guidance

Use publishing analytics to see which guides, portals, and workflow assets are getting attention from customers or teammates.

Customer success, support, product education, and operations teams measuring self-serve guidance.

Workflow

Built from real workflow context

stpwise starts with what users actually do, then turns that source into guidance across docs, videos, portals, embeds, and live in-app walkthroughs.

1

Publish guidance

Share guides, portals, and walkthrough content with the audience that needs the workflow.

2

Track engagement

Review usage signals to understand which content is being opened and reused.

3

Improve what matters

Use analytics as a signal for what to update, promote, or turn into live in-app help.

Use cases

Where it fits

Help center reporting
Customer education
Support deflection
Internal enablement
Benefits

Why teams use it

See which published guidance gets used
Prioritize updates based on real engagement
Connect content performance with onboarding and support workflows
Related pages

Connect the workflow

Frequently asked questions

What can guide analytics show?

Guide analytics can help teams understand engagement with published guidance so they can improve the content that matters.

Are analytics available for portals?

Published portals and guides can provide engagement signals that help teams understand how self-serve guidance performs.

Can analytics identify stale content?

Analytics can show usage patterns, while guide health and drift signals help teams identify content that may need maintenance.

Record once. Publish every way users need help.

Turn one workflow into a guide, walkthrough video, branded help center, and live in-app walkthrough.

Track guide engagement
Guide Analytics for Workflow Documentation - stpwise