The Acoustic Analytics Developer Hub

Welcome to the Acoustic Analytics developer hub. You'll find comprehensive guides and documentation to help you start working with Acoustic Analytics as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Verifying the target page

All of the provided Acoustic Tealeaf target pages are named so that the data they receive can be captured, processed, and integrated into replay by Acoustic Tealeaf.

Overview

Skill Level: Any

Prerequisites

Note: The file name of the Acoutic Tealeaf target page must include TealeafTarget in it for easy identification. Do not change this file name after you configure Acoutic Tealeaf UI Capture.

Complete the following steps to verify that there are no impediments to the capture and processing of the Acoutic Tealeaf target page in your system.

Step-by-step

  1. In the Web Console of the Acoutic Tealeaf Passive Capture Application, you configure file extensions to drop from capture. Verify that the file extension used for your Acoutic Tealeaf target page is not dropped from capture.
  2. In the Acoutic Tealeaf RealiTea Viewer, some file extensions are treated as interpreted pages, which means that the pages are interpreted on the web server before they are delivered to RealiTea Viewer. Verify that the extension for your Acoutic Tealeaf target page file name does not appear in the list of possible interpreted pages in RealiTea Viewer.

Updated 25 days ago


Verifying the target page


Suggested Edits are limited on API Reference Pages

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