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

1

Send a readable screen name

Use a title users would recognize. React Native uses the tracker instance shown here; native guides above show the equivalent platform call.

screen-view.ts

1await tracker.trackScreen({2  name: 'Checkout',3  path: '/checkout'4});
2

Add screenClass for dynamic screens

Group many detail pages under one pattern.

course-detail.ts

1await tracker.trackScreen({2  name: 'Course Detail: Productivity Masterclass',3  path: '/courses/123',4  screenClass: 'Course Detail'5});
3

Use route paths when appropriate

Route-based apps can send paths such as /course/:id.

Options / Configuration

OptionTypeRequiredDescription
namestringSpecific screen or route name
pathstringStable route path
screenClassstringnoGrouping pattern for dynamic screens

Event model

EventUsed for
screen_viewScreens 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?