Skip to contentSkip to navigationSkip to topbar
On this page
Looking for more inspiration?Visit the
(information)
You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

Spec: Screen


The Screen call lets you record whenever a user sees a screen, the mobile equivalent of Page, in your mobile app, along with any properties about the screen. Calling Page or Screen in one of Segment's sources is one of the first steps to getting started with Segment.

Segment University: The Screen Method
Check out our high-level overview of the Screen method in Segment University. (Must be logged in to access.)

Here's the payload of a typical Screen call, with most common fields removed:

1
{
2
"type": "screen",
3
"name": "Home",
4
"properties": {
5
"Feed Type": "private"
6
}
7
}

And here's the corresponding Objective-C event that would generate the above payload:

1
[[SEGAnalytics sharedAnalytics] screen:@"Home"
2
properties:@{ @"Feed Type": @"private" }];
(information)

Info

Based on the library you use, the syntax in the examples might be different. You can find library-specific documentation on the Sources Overview page.

Beyond the common fields, the Screen call takes the following fields:

FieldTypeDescription
nameoptionalStringName of the screen

See the Name field docs for more details.
propertiesoptionalObjectFree-form dictionary of properties of the screen, like name

See the Properties field docs for a list of reserved property names.

Example

example page anchor

Here's a complete example of a Screen call:

1
{
2
"anonymousId": "3a12eab0-bca7-11e4-8dfc-aa07a5b093db",
3
"channel": "mobile",
4
"context": {
5
"ip": "8.8.8.8"
6
},
7
"integrations": {
8
"All": true,
9
"Mixpanel": false,
10
"Salesforce": false
11
},
12
"messageId": "022bb90c-bbac-11e4-8dfc-aa07a5b093db",
13
"name": "Home",
14
"properties": {
15
"variation": "blue signup button"
16
},
17
"receivedAt": "2015-02-23T22:28:55.387Z",
18
"sentAt": "2015-02-23T22:28:55.111Z",
19
"timestamp": "2015-02-23T22:28:55.111Z",
20
"type": "screen",
21
"userId": "97980cfea0067",
22
"version": "1.1"
23
}

The User ID is a unique identifier for the user performing the actions. Check out the User ID docs for more detail.

The Anonymous ID can be any pseudo-unique identifier, for cases where you don't know who the user is, but you still want to tie them to an event. Check out the Anonymous ID docs for more detail.

Note: In our browser and mobile libraries a User ID is automatically added from the state stored by a previous identify call, so you do not need to add it yourself. They will also automatically handle Anonymous IDs under the covers.


Each screen can be tagged with a name. For example, many apps have a "Signup" screen that can be useful to tag so that you can see users as they move through your funnel.


Properties are extra pieces of information that describe the screen. They can be anything you want.

Segment has reserved some properties with semantic meanings and handles them in special ways. You should only use reserved properties for their intended meaning.

Reserved properties that Segment has standardized:

PropertyTypeDescription
nameStringName of the screen. This is reserved for future use.