Virtually everything about your digital experience is captured and indexed in FullStory. With OmniSearch, you can run powerful queries to target sessions that match specific user and event criteria. In this article, we’ll define what user and event criteria is available using FullStory search.
Want to see what's new? Check out our newest Event Filters for Refreshed URL, Highlighted Content, Pinch-to-zoom, and Scroll Depth.
User Filters
User Filter |
Description |
Web and Mobile App Support |
Any user |
Finds any and all users. Use this option when more specific user criteria isn’t relevant for your search. |
✓ |
|
Finds users by email address when you're passing in the user's email address via a call to either FS.setUserVars or FS.identify. |
✓ |
Name |
Finds users by name when you’re passing in the user's displayName via a call to either FS.setUserVars or FS.identify. |
✓ |
Signed-Up Status |
Finds users who have been identified by a unique user ID (UID) via FS.identify. |
✓ |
User ID |
Finds users by specific UID that you’re passing into FullStory via FS.identify. |
✓ |
Total active time |
Finds users by the total amount of time they have been active on your site. |
✓ |
Total time |
Finds users by the total amount of time they have spent on your site, including time in which they were inactive. |
✓ |
Average session active time |
Finds users by the average amount of time a user is active on your site during a session. |
✓ |
Average session length |
Finds users by the average length of time a user spends on your site during a session, including time in which they were inactive. |
✓ |
First seen |
Finds users by the date they were first seen by FullStory. |
✓ |
Total sessions |
Finds users by the total number of sessions captured for a user. |
✓ |
Last seen |
Finds users by the most recent date a user accessed your site. |
✓ |
To further customize your user filters, consider using FS.setUserVars to get even more advanced. This API lets you send custom user data to FullStory that you can use to target users based on properties that are important to your business. For example, search by criteria like user role, product interest, or average spend.
Event Filters
Event Filter |
Description |
Web and Mobile App Support |
Any activity |
Finds any and all activities. Use this option when more specific event criteria isn’t relevant for your search. |
✓ |
Custom Event |
Finds activities where configured events have occurred. |
✓ |
Visited Page |
Finds activities where users visit a specific page. To read about the differences between Pages & URLs, check out this article. |
Web Only |
Visited URL |
Finds activities where users visited a specific URL. |
Web Only |
Clicked |
Finds activities where a user clicked on an element. |
✓ |
Changed |
Finds activities where a user changed a specific element on your website, such as an input field. You can even use this filter to search for the exact text a user entered into a specific input field (i.e. a form field or search bar). |
✓ |
Pinch-to-zoom |
Finds activities where a user zoomed in or zoomed out using a touch device. |
Web Only |
Refreshed URL |
Finds activities where a users refresh their pages using their browser refresh button or keyboard shortcut. Learn more about refreshed page here. |
Web Only |
Highlight |
Find activities where a users highlight content on a page. Learn more about highlight here |
✓ |
Rage clicked |
Finds activities where a user rage clicked (i.e. clicked repeatedly on an element in a short period of time). Learn more about rage clicks here. |
✓ |
Error clicked |
Finds activities where a user error clicked (i.e. clicked on an element and triggered an error). Learn more about error clicks here. |
✓ |
Dead clicked |
Find activities where a user dead clicked (i.e. clicked on an element with no response from the browser). Learn more about dead clicks here. |
✓ |
Thrashed cursor |
Find activities where a user thrashed their cursor (i.e. moved their cursor back and forth rapidly out of frustration). Learn more about thrashed cursor here. |
Web Only |
Suspicious activity |
Finds activities where a suspicious activity occurred (i.e. text may have been inputted by a SQL injection or cross-site scripting attack instead of a user). Learn more about suspicious activity here. |
Web Only |
Navigated to Screen |
Finds activities where a user navigated to a specific app screen. |
FullStory for Mobile Apps Only |
Crashed |
Finds activities where a crash occurred. |
FullStory for Mobile Apps (Android only) |
Low Memory |
Finds activities where data capture stopped due to low device memory. |
FullStory for Mobile Apps Only |
Abandoned form |
Finds activities where a user started filling out a form, but left before submitting their data. Learn more about form abandonment here. |
Web Only |
Watched Element |
When configured in FullStory Advanced & Enterprise accounts, this finds activities where an element rendered on the page and specifies if it was visible in the user’s viewport. |
Web Only |
Page load |
Finds activities with a specific page load time. |
Web Only |
DOM content loaded |
Finds activities with a specific DOM content load time. |
Web Only |
First Contentful Paint |
Finds activities with a specific First Contentful Paint time. |
Web Only |
Network error URL |
Finds activities where an Network error occurred. |
✓ |
Uncaught Exceptions |
Finds activities where an uncaught exception occurred. |
✓ |
Console error |
Finds activities where a console error occurred. |
✓ |
To further customize your event filters, consider using FS.event to get even more advanced. This API lets you send event data to FullStory that you can use in search as well. For example, search for activities where users completed a purchase using criteria like order value, number of items purchased, or other event properties you configure.
Adding Dependent Criteria to Event Filters
FullStory lets you add dependent criteria to event filters. Dependent criteria allows you to search for events when additional criteria is true. For example, the search below will return activities where the user clicked “Add to cart” when using a tablet.
Dependent Criteria |
Description |
Web and Mobile App Support |
City |
Refines your search by the user’s city, derived from their IP address. |
✓ |
State/region |
Refines your search by the user’s state or region, derived from their IP address. |
✓ |
Country |
Refines your search by the user’s country, derived from their IP address. |
✓ |
IP address |
Refines your search by the user’s IP address. |
✓ |
Browser |
Refines your search by the user’s browser (i.e. Chrome, Safari). |
Web Only |
Browser Version |
Refines your search by the user's browser version (i.e. 95.0.4638.54). |
Web Only |
Device Type |
Refines your search by the user’s device type (i.e. Desktop, Mobile, Tablet). |
✓ |
Platform |
Refines your search by the user’s platform (i.e. Web or Mobile Apps). |
FullStory for Mobile Apps Only |
Device model |
Refines your search by the user's device model (i.e. Samsung SM-G970U or Apple iPhone8,4). |
FullStory for Mobile Apps Only |
Device vendor |
Refines your search by the user's device vendor (i.e. Samsung or Apple). |
FullStory for Mobile Apps Only |
App version |
Refines your search by the user's app version (i.e. "latest," or a specific App version number). |
FullStory for Mobile Apps Only |
App OS version |
Refines your search by user’s device version (i.e. iOS 14.4.2). |
FullStory for Mobile Apps Only |
View |
Refines your search by the screen viewed when the event occurred. |
FullStory for Mobile Apps Only |
App package |
Refines your search by the mobile app package name. |
FullStory for Mobile Apps Only |
User agent |
Refines your search by the user's user agent, a string of browser information unique to each visitor on the web. | Web Only |
Page |
Refines your search by the specific page visited, based on definition in your Page Settings (Data Management > Pages). |
Web Only |
Previous Page |
Refines your search by previously visited page in a user's journey. |
Web Only |
Entry Page |
Refines your search by the page the user started their session on. |
Web Only |
Exit Page |
Refines your search by the page the user ended their session on. |
Web Only |
Operating system |
Refines your search by the user’s operating system (i.e. Windows, OS X, Chrome OS). |
✓ |
Time on Page |
Refines your search by the total time a user spent on a page where the event occurred. | Web Only |
Time on Page Active |
Refines your search by the total time a user was active on a page where the event occurred. | Web Only |
Time since page load |
Refines your search by the time elapsed since page load. |
Web Only |
Time since session start |
Refines your search by the time elapsed since the session began. |
✓ |
Console errors on page |
Refines your search by the number of console errors on the page. | Web Only |
Console warnings on page |
Refines your search by the number of console warnings on the page. | Web Only |
Display width |
Refines your search by the width of the user’s display (i.e. the screen they’re using). |
✓ |
Display height |
Refines your search by the height of the user’s display (i.e. the screen they’re using). |
✓ |
Viewport width |
Refines your search by the width of the user’s viewport (i.e. the visible area of a webpage). |
✓ |
Viewport height |
Refines your search by the height of the user’s viewport (i.e. the visible area of a webpage). |
✓ |
Visited URL |
Refines your search by the URL where the event occurred. |
Web Only |
Referrer URL |
Refines your search by the URL visited immediately prior to the event. |
Web Only |
|
Refines your search by the user's email address when you're passing in their email via a call to either FS.setUserVars or FS.identify. |
✓ |
Name |
Refines your search by the user's name when you're passing in a displayName value via a call to either FS.setUserVars or FS.identify. |
✓ |
Scroll Depth |
When searching for visited URL events, refines your search by how far a user scrolled on the page. Learn more about scroll depth here |
Web Only |
Gesture |
When searching for pinch-to-zoom events, refines your search by whether the user zoomed in or zoomed out. |
Web Only |
To further customize your dependent event filters, use FS.setUserVars, FS.identify, and FS.event to leverage your own custom properties.
FAQ
What is the difference between the "in any order" and "in this order" filters?
"In any order" implies that different filters can match the same event while "in this order" is the only way to guarantee that unique events are matched.