Session: a session is everything the user did within your app, from launch until they closed it or sent it to the background. It includes all the meta-data collected during the user visit, including device and user data and interactions with your application such as screen visits, events triggered, and gestures.

Video: it is a video representation of the session that shows the exact reproduction of what the users did with the application. How they interacted, how the screens were displayed, what messages or errors they had, etc.

Rage tap or gesture: A rage tap represents rapid-fire taps in frustration. It's defined by at least 3 taps within a certain radius on the screen and at most 300ms between consecutive taps. It would show you when users are frustrated with a certain element in your app.

Unresponsive gesture: represents a tap or gesture that triggers no response from the application. It could be either an interaction with an element that is not responding (e.i. bug) or the user trying to interact with a static element of the screen (e.g. text).

Schematic recording: by default, UXCam generates a schematic representation on iOS apps to visualize in-app behavior, without recording the app’s screen. This technology reconstructs the session by drawing rectangular shapes and texts in a way that reflects the app’s actual screen layout. We do it to make sure you're compliant with Apple privacy guidelines.

UI Freezes: indicates when the app is blocked or frozen. We detect a UI freeze when you run a process on the UI thread that takes too long and it can’t process the user input. We track it by adding a piece of code that tries to run on the main thread at regular intervals. If the gap between runs is unexpectedly high we declare a UI Freeze.

Crashes: A crash occurs when there’s an unexpected exit caused by an exception or signal that has not been addressed during development. When an unexpected signal occurs, the app will crash and be forced to close.

Active user: active users are unique users that visited your app. UXCam defines a unique user based on the Install ID, however, you can also set up your own User ID. 

Event: An event can indicate any user interaction with your app, such as pressing a button, completing a process, seeing an error message, etc. UXCam detects two events by default: rage taps and UI freezes. However, if you want to track other actions from your application you need to send them as Custom Events. 

Event properties: Each event can have up to 20 properties attached, these properties can provide further information about the events. E.g. count, status, name, category, type, etc. 

Install ID: UXCam uses a Vendor Device ID to identify unique users (UIDevice.currentDevice.identifierForVendor.UUIDString) which is a random UUID tied to the app publisher.

Session ID: It’s a unique ID assigned to each session. 

Device time: Shows an exact time of completing a session by a user in their time zone.

Recording time: Shows when we recorded a session in UTC. 

Uploading time: Shows when we uploaded a session to UXCam in UTC.