Segment

  • Category IDs the segment is assigned to. Part of the segment's audience - see users.

  • Creation timestamp

  • ID of user who created this record

  • ID of the custom module when the segment targets a custom module instead of a built-in one

  • More detailed description of segment

  • Filter expression selecting the records that belong to this segment. Not JSON - it is the same string grammar as the filter query parameter of the record list endpoints, documented there in full: field operator value terms joined with &/; (AND) or | (OR), groups in parentheses, and the same operators (=, !=, >, >=, <, <=, ~/!~ LIKE with % wildcards, ... for an IN set). Example: (name~%acme%&statusId...1,2,3)|spaceId=5.

  • Unique identifier - primary key

  • Module this segment applies to (e.g. 'contact', 'deal'); must match a value from the modules table

  • Name of the Segment

  • Numeric position used to sort segments in the UI

  • Team IDs the segment is assigned to. Part of the segment's audience - see users.

  • Last edit timestamp

  • ID of the user who last edited this record

  • User IDs the segment is assigned to. Part of the segment's audience together with teams and categories: leaving all three empty makes the segment readable by everyone and editable or deletable only by an administrator, while any non-empty audience restricts it to its members.