Create a new segment. A segment defines a part of the population of an
entity, for example, the population of users. It contains an overall
proportion of the population as well as optional targeting criteria, like
the country a user is from. A segment can also be coordinated with other
segments, by setting exclusivity_tags and exclusive_to, preventing one
user to be included in two segments, that are exclusive to each other,
simultaneously.
Note, the segment is not active until it is allocated.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The ID to use for the segment, which will become the final component of the segment's resource name.
This value should be 4-63 characters, and valid characters are /[a-z][0-9]-/.
The body is of type object.
OK
A reusable slice of an entity population.
Time when the segment was first created.
Time when the segment was last updated.
Reference to the identity that created this segment.
Reference to the identity that last updated this segment.
The resource name of the segment.
For example:
segments/0smva5nxuhv4yts6paxt
A human-friendly name for the segment.
A description for the segment.
The targeting that this segment adheres to.
How much of the total population that is allocated to this segment, and the coordination with other segments.
Current state of the segment.
A bitset representing the buckets that are allocated for this segment.
General labels for this resource.
The workflow instance that created this segment. If set, permissions will be inherited from the workflow instance, in addition to the segment permissions.
The flag owning the rule this segment is connected to. If set, permissions will be inherited from the flag, in addition to the segment permissions.
The owner of the resource. If not set will default to the creator.