FullStory

Public discussion around FullStory over the observed multi-week window was heavily weighted toward frustration, with bugs and reliability concerns dominating nearly every corner of the conversation. Commenters surfaced repeated crash signatures tied directly to FullStory integrations, including references to unhandled rejections and native session-start failures on iOS, with one mention noting the issue had touched thousands of users across thousands of events. The tone in these threads was transactional and urgent rather than exploratory, suggesting that for the teams involved, FullStory was less a tool under evaluation and more an active source of production pain.

The score trajectory tells a story of early cautious optimism giving way to a sustained drop. Scores climbed gradually through January and into mid-February, reflecting a brief window where sentiment appeared to stabilize or even improve slightly. That trend reversed sharply in late February and collapsed further by mid-May, when a cluster of mentions drove the score to its lowest recorded point in the window. A brief partial recovery appeared in late May before sentiment slipped again in June, leaving the overall picture as a downward drift with no sustained recovery.

Reliability and bugs accounted for the bulk of complaint-theme mentions, and several of the sample threads read as escalated engineering tickets rather than casual feedback, which may amplify the negative signal. One mention flagged a security-adjacent concern around token exposure, adding a layer of unease beyond pure performance complaints. On the other side, a small number of voices acknowledged integration value and surfaced feature requests, suggesting some users still see potential worth investing in. A brief comparative mention framed FullStory against an alternative platform in favorable terms for the competitor, hinting that the broader competitive conversation may be shaping how some commenters contextualize their dissatisfaction.