THIS FEATURE IS AN ADD-ON TO OUR REGULAR PLAN. IF YOU'D LIKE TO LEARN MORE, SHOOT AN E-MAIL TO SUPPORT@FULLSTORY.COM FOR PRICING DETAILS.
Our primary purpose at FullStory is to provide the best tool possible for you to improve your customer’s experience. Since we’re indexing so many events, we’re aware that there is some pretty powerful data under the hood and much of it could be applied more specifically to your organization. We’re also aware that the programmers, data scientists, and software engineers you have on staff may be salivating at the thought of getting their hands on the hard data we’re collecting! So we designed a feature with your top priorities in mind.
A raw data extract of events that have been recorded for your organization.
See below for a full list of Data Export contents.
The possibilities are endless! This data set can be used on its own or to supplement existing models that aim to analyze user behavior. You can simply use the data for providing your marketing team with a point and click analysis tool or you can plug it into your fraud detection (e.g.) algorithm to add extremely powerful data to your model. The point is, you know best how the data is most relevant to your business needs.
There are two ways to access your Data Export extracts. By default, you will receive one data file of all the events that were recorded for your organization in the preceding 24 hours (midnight to midnight EST). You can request to change the frequency of extracts between the range of every 30 minutes up to every 24 hours.
User Id: A unique identifier for a user cookie on a given device/browser. This ID is reset if the User clears their cookies, switches devices, changes browsers, etc.
User App Key: The user identifier that was passed to FullStory from your system using FS.identify.
Individual Id: A unique identifier for the Individual that combines all Users with the same User App Key. For example, if you’ve identified user 123 whenever they visit your site, their Individual will include all of their Sessions across devices, browsers, etc.
Session Id: The identifier for a particular session. This value is only unique within the set of sessions for a given User.
Page Id: An identifier for a page within a session. Again, this is only unique within the session to which it belongs.
User Email Address: The email address that was set via FS.identify.
User Display Name: The display name that was set via FS.identify.
Page Url: The full URL of the page on which the given event occurred.
Page Duration: The total time this User spent on this page during this session (milliseconds).
Active Page Duration: The active time (mouse movement, text entry, clicks, etc.) this User spent on this page during this session (milliseconds).
Page Referrer URL: The page from which the user reached this page.
Event Time: The absolute time when the event occurred.
The type of event that was recorded. Typical types are:
“change”: changing the text in a text entry field.
“navigate”: a URL change, either to a completely new page or a new hash fragment.
We also use heuristics to identify and surface 3 behaviors that we believe are useful to our customers, called Rage Clicks, Error Clicks, and Dead Clicks. For any “click” event type that has been identified as Rage, Dead, or Error a field labelled EventModFrustrated will be associated and it will include a score to rank the level of frustration.
“Rage Clicks”: your customer clicks the page a bunch of times in rapid succession because they’re frustrated.
“Dead Clicks”: your customer clicks something, but nothing happens.
“Error Clicks”: your customer clicks something and a console error is generated.
Event target text: Where applicable, this contains the text of the event target. For example, if the user clicked a button that says “Pay now”, the event target text would be “Pay now”.
Event target selector: Where applicable, this contains the CSS selector for the event target.
Latitude/Longitude: The latitude/longitude corresponding to this session.
User Agent: The full user agent string for the system on which this session was recorded.
Browser: The browser that was used for this session.
Device: The device type that was used for this session.
Operating System: The operating system type that was used for this session.
The FullStory team awaits your every question.Contact Us