Concepts
Understand how UXCam works under the hood
Concepts
This section explains how UXCam works at a fundamental level. Understanding these concepts helps you make better integration decisions and get more value from your analytics.
Core Concepts
How Session Recording Works
Understand the technical approach behind screen capture, data transmission, and session reconstruction
Privacy and Compliance
GDPR, CCPA, consent management, and data handling practices
Understanding Occlusion
How UXCam protects sensitive data in recordings and the different occlusion strategies
Quick Reference
| Concept | Description |
|---|---|
| Session | A period of user activity from app open to background |
| Screen | A distinct view or page in your app |
| Event | A tracked user action (tap button, complete purchase) |
| User Property | An attribute assigned to a user (subscription tier, account type) |
| Occlusion | Hiding sensitive data in recordings |
| Schematic Recording | Wireframe-style recording that captures layout without actual content |
Integration Concepts
Understanding these helps you configure UXCam effectively:
Automatic vs Manual Screen Tagging
- Automatic: UXCam detects screens based on Activity/ViewController names
- Manual: You explicitly tag screens with meaningful names
Most teams use a hybrid approach - automatic detection with manual overrides for key screens.
Recording Modes
- Full Recording: Captures actual screen content (requires occlusion for sensitive data)
- Schematic Recording: Captures screen structure as wireframes - more privacy-friendly
Session Lifecycle
App Opens → Session Starts → User Interacts → App Backgrounds → Session Uploads → Dashboard Shows Data
Sessions upload when the app goes to background. If force-closed before upload, data may be lost.
Further Reading
- SDK Reference - API method documentation
- Getting Started - Platform integration guides
- Troubleshooting - Common issues and solutions
Updated about 12 hours ago
Did this page help you?
