Link replays and track recording fixes
Connect
SPIRITT
FullStoryFullStory
Put context to work
SPIRITT brings FullStory user profiles and session replay links into support and product workflows. It also runs event imports, maintains extraction rules, and checks recording controls so your team can act on dependable context.
What you can do with FullStory.
Faster issue handoffs
Match a customer's UID or email to FullStory users and recent replay links, then carry that context into the issue your team is resolving.
Reliable event ingestion
Import server events, track asynchronous job results, and resolve failed records without treating a submitted batch as a completed import.
Deliberate capture controls
Inventory masking and blocking rules alongside recording settings, and turn configuration gaps into concrete, accountable remediation work.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the support, product, or analytics operation you want to run around FullStory.
02
Connect FullStory
Connect FullStory with an API key suited to your mission. Creating or updating element recording and masking rules requires an Admin API key.
03
Delegate an outcome
Ask SPIRITT to build a replay lookup desk, operate server event imports, or maintain a recording control review workflow.
Hand over a mission.
Choose a mission. Make it yours.
Put FullStory to work.
Put FullStory context to work
Questions
FullStory, with SPIRITT.
01Can SPIRITT watch FullStory session replays?+
The available session lookup returns recent replay links using an application UID, email, or exact session UID. SPIRITT can retrieve those links and route them with user context, but this connection does not provide replay contents for automatic viewing or behavioral analysis.
02What access does FullStory require?+
FullStory connects using an API key. SPIRITT can validate the connected account and identify its organization and key role. Creating or updating element recording and masking rules requires an Admin API key; the key's permissions govern which operations can run.
03Can it run recurring user and event imports?+
Yes. SPIRITT can upsert individual users or submit asynchronous imports of up to 50,000 users or server events per batch. It can check import status and retrieve successful or failed records. A recurring workflow can reconcile results, resolve exceptions, and use idempotency protection for event imports.
04How can FullStory context reach support and engineering?+
SPIRITT can match a supplied UID or email to a FullStory user, retrieve recent session links, and carry that context into connected Jira or Linear issues and Slack handoffs. It can also use approved CRM fields to maintain FullStory profiles rather than leaving customer context disconnected.
05What custom systems can SPIRITT build around FullStory?+
Useful builds include a support replay lookup desk, an import exception queue, a segment directory, and a quota planning dashboard. These use available user records, replay links, job results, segment metadata, and quota readings. Segment metadata alone does not provide membership exports or funnel measurements.
06How does extraction management differ from privacy controls?+
Extraction rules define capture sources and mappings and can be created, updated, archived, or resumed. Element rules govern recording or masking, while recording settings and their history support configuration reviews. These are distinct controls: archiving an extraction rule is not a substitute for masking sensitive page elements.