+
+ | `userId` _String_ |
+ The ID for this user in your database. |
+
+
+ | `event` _String_ |
+ The name of the event you're tracking. We recommend human-readable names like Played Song or Updated Status. |
+
+
+ | `properties` _Properties, optional_ |
+ A dictionary of properties for the event. If the event was Added to Cart, it might have properties like `price` or `product`. |
+
+
+ | `options` _Options, optional_ |
+ An `Options` object lets you set a [timestamp](#historical-import), [enable or disable destinations](#selecting-destinations), or [send additional context](#context). |
+
+
+
+Find details on **best practices in event naming** as well as the **`track` method payload** in our [Spec](/docs/connections/spec/track/).
+
+## Screen
+
+The [`screen`](/docs/connections/spec/screen/) method lets you you record whenever a user sees a screen of your mobile app, along with optional extra information about the page being viewed.
+
+You'll want to record a screen event an event whenever the user opens a screen in your app. This could be a view, fragment, dialog or activity depending on your app.
+
+Not all services support screen, so when it's not supported explicitly, the screen method tracks as an event with the same parameters.
+
+Example `screen` call:
+
+```csharp
+Analytics.Client.Screen("019mr8mf4r", "Register", new Properties() {
+ { "type", "facebook" }
+});
+```
+
+The `screen` call has the following fields:
+
+
+
+ | `userId` _String_ |
+ The ID for this user in your database. |
+
+
+ | `name` _String_ |
+ The screen name you're tracking. We recommend human-readable names like Login or Register. |
+
+
+ | `category` _String_ |
+ The screen category. If you're making a news app, the category could be Sports. |
+
+
+ | `properties` _Properties, optional_ |
+ A dictionary of properties for the screen view. If the screen is Restaurant Reviews, it might have properties like `reviewCount` or `restaurantName`. |
+
+
+ | `options` _Options, optional_ |
+ An `Options` object lets you set a [timestamp](#historical-import), [enable or disable destinations](#selecting-destinations), or [send additional context](#context). |
+
+
+
+Find details on the **`screen` payload** in our [Spec](/docs/connections/spec/screen/).
+
+## Group
+
+`group` lets you associate an [identified user](/docs/connections/sources/catalog/libraries/server/java/#identify) user with a group. A group could be a company, organization, account, project or team! It also lets you record custom traits about the group, like industry or number of employees.
+
+This is useful for tools like [Intercom](/docs/connections/destinations/catalog/intercom/), [Preact](/docs/connections/destinations/catalog/preact/) and [Totango](/docs/connections/destinations/catalog/totango/), as it ties the user to a **group** of other users.
+
+Example `group` call:
+
+```csharp
+Analytics.Client.Group("userId", "groupId", new Traits() {
+ { "name", "Initech, Inc." },
+ { "website", "http://www.example.com" }
+});
+```
+The `group` call has the following fields:
+
+