Gradual supports a native integration with FullStory, letting you record and replay member sessions on your community site using your own FullStory account.
FullStory runs only after a visitor accepts analytics cookies.
Setting up the FullStory integration
Step 1: Find your FullStory Org ID
Your Org ID identifies your FullStory account, and you will find it in your FullStory account settings. Org IDs contain hyphens, and the whole value including the hyphens is what you need.
Step 2: Enable the integration in Gradual
Log in to dashboard.gradual.com as a Community Administrator
Navigate to Integrations in the lefthand menu
Scroll down to Traffic Tracking and locate FullStory
Select Setup
Enter your FullStory Org ID
Choose whether to send member identity to FullStory. This is off unless you turn it on — see Member identity below
Select Save
Once the integration is saved, you can turn it off and on again from its card on the Integrations page without re-entering your settings.
If you change the Org ID later, recording stops until the page is fully reloaded. This is deliberate: it stops sessions continuing to arrive in the account you just moved away from.
Cookie consent
FullStory does not load until a visitor accepts analytics cookies.
Before a visitor makes a cookie choice, nothing is sent to FullStory.
If a visitor rejects analytics cookies, nothing is sent to FullStory, however many pages they visit.
When a visitor accepts the Analytics category, recording starts.
If a visitor withdraws analytics consent later, recording stops from that point.
This works the same whether your community uses Gradual’s own cookie banner, OneTrust or Ketch. Whichever provider asks your visitors for consent, FullStory follows that provider’s analytics category.
To learn more, see Cookie and Consent Management, OneTrust Integration for Cookie Management and Ketch Integration for Cookie Management.
Member identity
By default, FullStory identifies each member by an internal Gradual ID. No name or email address is sent.
Turning on Send member identity to FullStory attaches the member’s display name and email address to their FullStory user record, so sessions can be matched to a person. Those two fields are all the setting sends: not job title, company, LinkedIn URL, location or profile photo.
Turning the setting off applies from then on. Names and email addresses already sent while it was on remain in your FullStory account, and removing them is done in FullStory rather than in Gradual.
When a member logs out, their identity is detached from whatever happens next in that browser, so a later visitor on a shared device is not recorded as them.
Troubleshooting and best practices
Recording starts as soon as a visitor accepts analytics cookies. To test, accept analytics cookies on your own community site and check that a session appears in FullStory a minute or so later.
If no sessions appear, check three things: that the integration is enabled, that the Org ID is the one from your FullStory account, and that you accepted the Analytics cookie category in the browser you tested with. An incorrect Org ID saves without an error but never produces a session.
This integration covers the web experience only. Native mobile apps are not recorded.
If you are still having trouble, reach out to [email protected].