Tealeaf UI Capture overview

UI Capture is a JavaScript (JS) library that integrates with a web application to capture data related to visitor interaction, browser environment, and performance. The data is processed and used for a wide range of customer analytics, usability reports, and replaying actual visits.

UI Capture comes with an extensive capability of data capture functionality, but the framework can also be extended to enable capture of a wide variety of custom data.

Some examples of data captured by UI Capture include mouse clicks, keyboard input, scroll, touch interactions, snapshots of the rendered HTML (DOM snapshots), browser type, screen dimensions, cookies, JavaScript exceptions, and page load time.

Quick Links
Supported browsers, application types, and protocols Impact on your website Download and install UI Capture
UI Capture Tutorials Other related documentation

Supported browsers, application types, and protocols for UI Capture

Supported browsers

    The UI Capture JavaScript is supported for deployment to the following browsers:
  • IE 11.0 and Microsoft Edge
  • Firefox 30.0 and later
  • Chrome 30 and later
  • iOS 7 Mobile Safari and later

Note about Acoustic Tealeaf CX on-prem

For replay, the Tealeaf RealiTea Viewer uses an embedded instance of the version of Internet Explorer that is installed on the local machine. Replay of Tealeaf sessions in Tealeaf RealiTea Viewer (RTV), the stand-alone application for desktop replay, requires Internet Explorer support. If Internet Explorer is not supported by your enterprise’s IT department, basic replay can be managed through the browser.

Creation of events that monitor JSON-based data that is submitted from Acoustic Tealeaf UI Capture is not supported in Tealeaf RealiTea Viewer. You must use Browser-Based Replay to create events from these versions of UI Capture.

Supported application types

All modern web applications are supported with the following exceptions:

Updated 6 months ago

Tealeaf UI Capture overview

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.