Screen tracking
Send screen_view events with screen names and optional screen classes.
Last updated June 3, 2026
Track screens with readable screen_name values and screen_class patterns for grouped dynamic screens.
Prerequisites
- A mobile SDK installed
- A navigation hook or screen lifecycle callback
Steps
Send a readable screen name
Use a title users would recognize.
screen-view
1tracker.screenView({ screenName: 'Checkout' })Add screen_class for dynamic screens
Group many detail pages under one pattern.
course-detail
1tracker.screenView({2screenName: 'Course Detail: Productivity Masterclass',3screenClass: 'Course Detail'4})
Use route paths when appropriate
Route-based apps can send paths such as /course/:id.
Options / Configuration
| Option | Type | Required | Description |
|---|---|---|---|
| screenName | string | ✓ | Specific screen or route name |
| screenClass | string | no | Grouping pattern for dynamic screens |
| appVersion | string | no | Version shown in screen filters |
Event model
| Event | Used for |
|---|---|
| screen_view | Screens table, Realtime feed, screen context, top screens |
What happens next
Open Screens and confirm grouped rows appear when screen_class differs from screen_name.
Verify your setup
Verify your setup
Troubleshooting
Rows are noisy
Send screen_class for dynamic screens so instances group into one row.
Was this page helpful?