Who can use this feature?
- Available with Enterprise and Advanced plans.
- Requires an admin or architect role to configure.
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.
Using Segment Export to power workflows, send data to third-praty systems, or batch sync with your data warehouse? Check out Fullstory's new product, Data Direct, for an always-on alternative.
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 at the bottom of the 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, Numbers, Google Sheets, or your favorite spreadsheet program or use R, Python, etc. to work with the exported data.
Export Users
Export users is similar to the "Export as CSV" that exists on the Session Playlist.
Fields Available
*User specific fields listed below do not reflect the total based on the exported Segment's time filter but rather, the total lifetime of that User having been captured by Fullstory.
|
Name |
Export Field Name |
Description |
| Individual Id | IndvId |
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.
Example: https://app.fullstory.com/ui/<ORG_ID>/session/<INDVID>:<SESSIONID>
|
| Timestamp for Created User | UserCreated | UTC RFC 3339 timestamp for when the cookie associated with UserId was first seen. |
| User Id | UserId | A unique identifier for a user cookie on a given device/browser. This ID may be reset if the User clears their cookies, switches devices, changes browsers, etc. This field is not visible within the Fullstory UI—see UserAppKey below for more information. |
| User Display Name | UserDisplayName | The display name that was set via FS.identify or FS.setUserVars. |
| User Email Address | UserEmail | The email address that was set via FS.identify or FS.setUserVars. |
|
Number of Sessions |
NumSessions |
The total number of sessions that have been recorded for this user. |
|
Number of Pages |
NumPages |
The total number of pages that have been visited by this user. |
|
Number of Events |
NumEvents |
The total number of events associated with this user. |
|
Total Session Length (in seconds) |
TotalSec |
The total length of time in seconds of the user's captured sessions. |
|
Total Session Active Time (in seconds) |
ActiveSec |
The total active time in seconds for the user's captured sessions. |
|
Average Session Length (in seconds) |
AvgSessionSec |
The average length of time of the user's sessions. |
|
Average Session Active Time (in seconds) |
AvgSessionActiveSec |
The average active time of the user's sessions. |
|
Longest Session Time (in seconds) |
MaxSessionSec |
The longest session time for the user. |
|
Last Session Number of Pages |
LastSessionNumPages |
The number of pages visited in the user's last session. |
|
Last Session Number of Events |
LastSessionNumEvents |
The number of events in the user's last session. |
|
Last Session Total Session Length (in seconds) |
LastSessionSec |
The time in seconds of the user's last session. |
|
Last Session Active Time (in seconds) |
LastSessionActiveSec |
The active time in seconds of the user's last session. |
|
Start Timestamp of Last Session |
LastSessionStart |
When the most recent session for this user started. |
|
Last Page |
LastPage |
The last page visited in the user's most recent session. |
|
Last IP Address |
LastIp |
The IP address for the user's most recent session. |
|
Last Lat/Long |
LastLatLong |
The latitude and longitude for the user's most recent session. |
|
Start Time of Last Event |
LastEventStart |
The time for the last event in the user's most recent session. |
|
Last Browser |
LastBrowser |
The browser for the user's most recent session. |
|
Last Device |
LastDevice |
The device for the user's most recent session. |
|
Last Platform |
LastPlatform |
The platform for the user's most recent session. |
|
Last Operating System |
LastOperatingSystem |
The OS for the user's most recent session. |
| Custom User Variables | UserVars | If you're passing any user variables into Fullstory, we'll include them in the export. |
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 are the same as the fields in Data Export. For a full list of the current Event fields available, visit our developer docs.
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.