Who created each of our segments, and which are recent?
FullStory's segment list is fine for browsing but not for an audit across the team. Querri lists segments with creator and creation date so cleanup is a single question.
AI Chat
FullStory + Querri
Querri reads your FullStory segments, the session list for the user ID you set, recording and privacy settings, data operations and webhook endpoints, and keeps them beside your other systems.
Querri only reads from FullStory and never changes your records. SOC 2 Type II, HIPAA and ISO 27001:2022 certified, and your data is never used to train a model.
What you can answer
FullStory's segment list is fine for browsing but not for an audit across the team. Querri lists segments with creator and creation date so cleanup is a single question.
AI ChatBlocked IPs, domains, geo rules and recording features each come from a separate settings area. Querri reads them into one place, and Facts & rules can record what your team expects them to be.
Facts & rulesSession links for one person are easy to lose in support threads. Querri keeps that user's sessions with their FullStory URLs in the Library so anyone with access can find them.
The LibraryWhat comes over
Querri copies this data into your Library on a schedule, next to every other system you connect, so one question can draw on all of it.
Each sync reloads the data you picked, daily, weekly or monthly, or whenever you run it by hand.
Querri reads from FullStory and never creates, edits or deletes anything there. Every answer runs on Querri's own copy.
Querri's own sharing and row-level access decide who sees which rows, in chat, dashboards, Claude, ChatGPT and the API.
How to connect
Say "connect FullStory" or pick it from the connector catalog.
FullStory connects with an API key and a FullStory user ID, both entered in the secure form the Connector Agent never sees. The user ID decides whose sessions are read.
Pick the data you want and how often it refreshes, then approve the first load.
The data lands in your Library, ready for chat, dashboards and scheduled reports.
FAQ
Use a FullStory API key plus the user ID whose sessions you want to see. After you ask the Connector Agent for FullStory, both values go into the secure form and are kept encrypted.
Segments, the sessions of the user ID you entered, data operations, recording settings for blocking, domains, geography and features, webhook endpoints and available webhook event types.
On a daily, weekly or monthly schedule, or whenever you start a sync yourself. Segments, sessions and settings are reloaded in full on every run, so what you query reflects FullStory at the time of that sync.
No. Sessions are read for the one user ID set on the connection, with session ID, time and replay link. Event-level behavior data and sessions across all users are not part of this connector.
No. Querri only reads from FullStory. It never creates, edits or deletes records there, and every answer runs on Querri's own copy of the data.
Yes. Querri is SOC 2 Type II, HIPAA and ISO 27001:2022 certified, credentials are stored encrypted, and your data is never used to train a model.
Keep exploring
Connect FullStory, add the rest of your systems, and get answers your whole team can check.