A Quick Overview of FullStory - hackforla/website GitHub Wiki

FullStory Fields

FullStory provides the following data for any Segment: Usage trends over time, Segment Health (events per session, session length, and active time), Click type (Rage, Error, Dead), Device/Browser/Screen Resolution Breakdown, and Website Referrers.

Page Insights

Within each Session Playback, we can view Page Insights. Page Insights include: (1) Click Maps for each element of the Page, and (2) Inspect Mode, which shows insights by clicking on the specific page element of interest.

An Engagement Heatmap overlay for each Click Map may be toggled on/off.

More information here: https://help.fullstory.com/hc/en-us/articles/360020624074-Page-Insights-User-Guide

Frustration Signals

Know the difference between Rage Clicks, Error Clicks, and Dead Clicks: https://help.fullstory.com/hc/en-us/articles/360020624154-Rage-Clicks-Error-Clicks-Dead-Clicks-and-Thrashed-Cursor-Frustration-Signals

Frustrated Sessions: https://help.fullstory.com/hc/en-us/articles/360020828013-Frustrated-Sessions

Click Attribution

From FullStory: “We currently use a combination of inferred page and intelligently processed CSS selector to identify and attribute clicks. Sometimes a given CSS selector can match multiple elements in the page. We currently attribute clicks to the first element we encounter. This generally isn’t a problem if the element or it’s parents have sufficient detail with href’s, class names or IDs in the HTML. That being said, we can do better and have a solution in the works to properly attribute clicks to ambiguous elements like this.”

Further Reading

https://help.fullstory.com/hc/en-us/categories/360001614373-User-Guides

⚠️ **GitHub.com Fallback** ⚠️