Apply 1 suggestion(s) to 1 file(s)

.gitlab/issue_templates/Snowplow event tracking.md

@@ -15,7 +15,7 @@ We generally recommend events be tracked using a [structured event](https://docs
 
 * Category: The name for the group of objects you want to track. They can just be the GitLab category, or a specific workflow within a category.
 * Action: A string that is used to define the user action.
-* Label: An optional string which identifies the specific object being actioned.
+* Label: Optional. The specific element, or object that's being acted on. This is either the label of the element (e.g. a tab labeled 'Create from template' may be `create_from_template`) or a unique identifier if no text is available (e.g. closing the Groups dropdown in the top navbar might be `groups_dropdown_close`), or it could be the name or title attribute of a record being created.
 * Property: Optional. Any additional property of the element, or object being acted on.
 * Value: Optional, numeric. Describes a numeric value or something directly related to the event. This could be the value of an input (e.g. `10` when clicking `internal` visibility)