Available for the following Plan types:
FullStory Enterprise*
FullStory Advanced*
FullStory Business
FullStory Free
*with the following add-on:
FullStory for Mobile Apps
Available to the following User roles:
Admin
Architect
Standard
Introduction
Segment Export is a feature of the Data Export module that allows our data savvy users to analyze the events FullStory captures in ways custom to their needs outside of the current UI. This makes your digital experience data ripe for more heavy statistical analysis, custom reporting, and machine learning training data sets. Please see here for more information about what data is in data export, a technical walkthrough for using data export, or our sql cookbook of different recipes.
Getting Started
To get started with Segment Export, select the Segment you want to export and click 'Create Export' above the User Trends Card.
You can then name your export and confirm the time range of your export, which matches the time range selected for your segment. FullStory offers 3 download types: CSV, JSON, and NDJSON. The download will be a gzipped file, so you will need to unzip it before uploading it directly to something like Google Sheets or Excel.
Note: Windows users will need an additional application such as 7-Zip to unzip the .gz format. Mac OS users will be able to unzip the file without any additional applications.
After you click Export, it will create a job in the Data Exports table. Find this in your sidebar. This tab will be pre-filtered to only the exports you have created. If you want to see the Data Exports of all data grouped by time ranges, you can un-check the 'Only Mine' check box in the top right.
The time it takes for the download to be ready will depend on how much data you are downloading. Many times, this will take a few seconds, but it can also take 5-10 minutes. The Progress icon on the right will give you a sense of how long it will take.
When the Status of your export goes from 'In Progress' to 'Completed,' the export is ready to be downloaded.
From there you can find the file in the Downloads folder of your computer. Open it with Excel/Sheets (for CSV) or use it in R/Python/etc for JSON and NDJSON.
Export Users
Export users is similar to the "Export as CSV" that exists on the Session Playlist.
Fields Available
|
Field |
Description |
|
IndvId |
System generated variable that uniquely identifies a user |
|
Created |
The time and date the User was created expressed in UTC |
|
UserID |
If using FS.identify, user's unique ID (uid) will be listed |
|
DisplayName |
The name of the User as it is displayed by FullStory |
|
|
The email address of the User |
|
NumSessions |
The total number of sessions captured all time by the User |
|
NumPages |
The total number of pages this user has visited |
|
NumEvents |
The total number of events FullStory has captured for this user |
|
TotalSec |
The total length of time of the User's captured sessions |
|
ActiveSec |
The total amount of active time for the User |
|
AvgSessionSec |
The average session length in seconds |
|
AvgSessionActiveSec |
The average active session length in seconds |
|
MaxSessionSec |
The length of the user's longest session in seconds |
|
LastSessionNumPages |
The number of Pages visited in the last session by this user |
|
LastSessionNumEvents |
The total number of events in the last session by this user |
|
LastSessionSec |
The length of time in seconds of the last session by this user |
|
LastSessionActiveSec |
The length of active time in seconds in the last session by this user |
|
LastSessionStart |
The time that the last session of this user started |
|
LastPage |
The last URL the user visited in their last session |
|
LastIp |
The last IP the user visited your site from |
|
LastLatLong |
The latitude and longitude for the User's most recent session |
|
LastEventStart |
The time of the last event the user generated on your site |
|
LastBrowser |
The last browser type the user used your site from |
|
LastDevice |
The last device the user used your site from |
|
LastPlatform |
The last platform (i.e. iOS, Android) the user used your site from. |
|
LastOperatingSystem |
The last OS (ie Windows) the user used your site from |
|
UserVars |
If applicable, your custom user variables will be added. See FS.getUserVars for more information. |
*User specific fields listed above do not reflect the total based on the exported Segments time filter but rather, the total lifetime of that User having been captured by FullStory.
Export Events
Export events will provide data at a much more granular level than users. This data is great for advanced use cases like predicting churn, behavioral cohorting, and more.
Fields Available
The fields available in Export Events, will be very similar to the fields in Data Export, including a few additional fields described below:
|
Field |
Description |
|
UserCreated |
The time the associated UserId was created expressed in UTC |
|
EventTargetSelector |
Untokenized version of the css selector a user engaged with |
|
SessionStart |
The time in UTC that the last session started |
|
PageStart |
The time in UTC that the user navigated to the current page |
|
PageUserAgent |
Formerly called PageAgent, the User Agent String of the browser |
|
PagePlatform |
The platform of the user (FullStory for Mobile App sessions only) |
|
PageScreenWidth |
The width of the CSS Resolution of the screen in pixels |
|
PageScreenHeight |
The height of the CSS Resolution of the screen in pixels |
|
PageViewportWidth |
The width of the viewport size of the browser in pixels |
|
PageViewportHeight |
The height of the viewport size of the browser in pixels |
|
ReqURL |
If the 'EventType' is 'request,' the URL for the corresponding XHR request. |
|
ReqStatus |
If the 'EventType' is 'request,' the HTTP response code for the corresponding XHR request |
|
Pageviews |
Indicates the end of the page that is currently being viewed. Triggered whenever the URL path changes, or optionally the hash fragment, but not query string variables. |
Match Types
|
Match Type |
Description |
|
Events |
Export all event data that match your search / segment criteria |
|
Individuals |
... of Individuals that match your search / segment criteria |
|
Sessions |
... from sessions that match your search / segment criteria |
|
Pages |
... from Pages that match your search / segment criteria |
Segment Export in Action
Events
In the example shown above, Segment Export will include all events of the user navigating to the /checkout page and the user clicking on the text 'Purchase.' This is the most restrictive setting that will generate the least events.
Use Case: A segment of users that changed text in a search box. Use Event download to see which specific strings they were typing in.
Individuals
This export will include all events from users who went to the /checkout page and clicked Purchase. These events have to be within the time range of the export, but they do not have to happen in the same session that the user took these two actions.
Use Case: A segment of users that engaged with a new feature. Use Individual Download to understand how engaging with that feature might have affected other behavior on your site.
Sessions
This export will include all events from the sessions where users went to the /checkout page or clicked Purchase. Note: If we were to toggle 'across any number of sessions' to 'within the same session' for this segment, the export would be restricted only to sessions where both events happen.
Use Case: A segment of users that completed a checkout funnel. Using Session matching can help determine the paths that users take during successful conversions.
Pages
This export will include all events from the Pages /checkout and the page that the Purchase text is on. If Purchase does not happen on the Checkout Page (i.e. there is a separate purchase page), it will only provide the events from the page in the sessions where 'Purchase' clicked. For example, if a user gets to the 'Purchase Page' in two different sessions, but only clicks 'Purchase' once, only the events from the session where they clicked 'Purchase' will be included in the export.
The page referenced in the above example (and in the export itself) is different from the usual use of Pages (the feature) and the pages in our PageVars API. Data that comes from Pages and their metadata are not currently available via data export.
Use Case: A segment of users in an A/B test for a page. Page matching can help determine what interactions are happening on the page in question for the test group versus the control group.