Record app user sessions with Fullstory
Learn how to capture user app behavior for use with Fullstory.
Retool can record user behavior and interactions with apps using Fullstory. When enabled, data about user interactions with apps are reported directly to Fullstory for you to review in detail. You can then analyze app analytics, evaluate impact, and review interactions with session replay.
Considerations
A user session contains behavioral data, such as interactions, that occur with an app during a period of activity. Retool captures user session data for production apps that are accessed in user mode. This includes any external apps your organization may have.
A new session starts whenever a user launches an app. The session ends when a user leaves the app (e.g., closes the browser or navigates to a different page). Sessions may also end after a period of inactivity. Refer to Fullstory's session documentation to learn more about session activities.
Retool automatically includes the user's email address for each user session. User-sensitive data is automatically masked by Fullstory by default. If you need to display sensitive information in plain text within apps, Retool recommends using Config Vars or secrets to prevent this information being captured.
You can also configure data capture rules in Fullstory for specific elements using CSS selectors, if required.
1. Enable user session recording
To record user sessions, you need:
- A Fullstory organization. You can choose to create a new organization or use an existing one.
- Your Fullstory Org ID. Retool uses this ID when sending user sessions to Fullstory.
Navigate to the settings in your organization and set the Fullstory orgID. Once configured, Retool automatically captures and reports user sessions to Fullstory.
2. Define session elements
Fullstory automatically tags certain Retool components to provide insights, such as elements clicked the most. You can define additional elements with Fullstory using CSS selectors from Retool components.
Embedded apps
Embedded apps
Additional configuration must be set up to record apps embedded within an iFrame on another app. See [Fullstory] (https://help.fullstory.com/hc/en-us/articles/360020622514-Can-Fullstory-capture-content-that-is-presented-in-iframes) for additional information.
| Setup Description | Option | Expected Behavior |
|---|---|---|
| Parent and embedded app are on the same domain. | Default behavior | Records embedded app within the parent session. |
| Parent and embedded app are on different domains or subdomains. | Record emedded app with parent app | Records embedded app within the parent session. |
| Parent and embedded app are on different domains or subdomains. | Record embedded app as its own session | Records iFrame separately from the parent app. |