#Fs capture code#

The exact event name will be searchable via FullStory’s OmniSearch capabilities. The eventName parameter is a string containing the name of the event.

The new FS.event JavaScript API allows you to add a custom event to the event stream captured by FullStory. So, if you’d like to send client-side events over using our FS.event Javascript API, read on. Visit the Segment integration or Tealium integration page for more details.

#Fs capture code#

If you have already instrumented custom events in Segment or Tealium - we have integrations to pull in your events automatically with no extra code to write. You can also use custom events to visualize important moments in user Journeys, run powerful Conversions analyses, and measure trends with metrics and dashboards.

Then when viewing sessions, jump straight to the most important part and view the useful properties you've sent over. You can send client-side instrumented events into FullStory via our Javascript API to search and segment your sessions. Just like FS.identify and FS.setUserVars, which let you pull in custom user data to identify and add more valuable information about your users to your FullStory experience, we built FS.event to let you pull in your custom event data to identify and add more context to events occurring within a session. Have already identified a few key events that are crucial for you to understand your customer experienceĪlready have instrumented some events in a customer data platform you’d like to pull into FullStory Want to capture more details than can be captured by user click or tap actions You can always search for users who clicked or tapped any CSS selector or text on your site or mobile app to get insights right away.īut you might want to add some custom instrumented events as an extra layer of context on top of your rich FullStory data, if you: FullStory gives you out of the box insights, and the ability to construct searches and find insights without any instrumentation.