Lytics Segment API

Segments are named, logical expressionsof users. These segments may logically be builtusing other segments as well. The segment apiprovides a list of segments built by both the admin, pre-definedsegments automatically added to each account as well as custom onescreated through the UI.Segments represent a number of concepts:* *Segment* A list of users, users are members (or not) of a segment* *Trigger* As a user enters, or leaves a segment, this is a trigger. Triggers do not have a Size, only a history of events.* *Goal* A segment that also implies conversion. In Lytics App, there are *Goals* that show more prominently in a funnel type interface.* *Dynamic Attribute* A user belonging to a segment describes an attribute about that user. For instance *IsPurchaser* is both an attribute that can help personaliation, as well as a segment. We call these special segments *Aspects* at Lytics.* *Metric* A segment when used exclusively for the purposes of tracking conversions/metric.The Segment resource has the following attributes:| field | DataType | Description ||-------------|------------------|---------------|| id | string | unique id, Lytics assigned| created | Date | Created date| updated | Date | Last Updated Date| kind | string | What Type of segment from list above ["aspect","goal"] or leave empty for "segment".| slug | string | customer-assigned unique id (We auto assigned by slugifying `Name` if not provided).| name | string | Name of this segment| description | string | Long text description (optional)| is_public | bool | Is this segment available as part of user profile api (entity api)| segment_ql | string | Segment QL Logical Expression| tags | []string | List of tags, for organization purposesTo see a list of available fields available for segmentation rules see **catalog** api.