Cohortes

Des ensembles de personnes définis par ce qu'elles font ou ce qu'elles sont : chaque cohorte est un nom et une définition, et la définition est des clauses qui se lisent comme elles s'écrivent, a fait tel événement tant de fois en tant de jours, ou porte tel attribut à telle valeur. Une définition vide ne sélectionne personne, à dessein.

The library

Each card is one cohort: its name, whether it is active, how many people it currently selects and how fresh that answer is. A cohort whose clauses count behaviour over history is swept on a schedule and says when it was last evaluated, or that it never has been; one defined purely by current attributes is live and carries no timestamp, because a timestamp would imply a staleness it does not have. The toolbar narrows by search, kind and state, and deleting asks first, warning that analyses filtered by the cohort stop being filtered by it.

The definition editor

Opening a card unfolds its definition in place: behavioural clauses (did an event at least so many times within so many days, with the project's own event names suggested) and state clauses (an attribute compared to a value). A cohort is named first and defined after, and an empty definition selects nobody rather than everybody, which the open row says in as many words. Opening a second card does not close the first, so two definitions can be compared side by side without losing edits.

Where cohorts are used

A cohort scopes a question in the Analytics workbench, targets a campaign in the Inbox, and gates workflow triggers on the Workflows screen. The same set of people, wherever the set is needed.

Where this meets the API

The concept behind the screen is the People and cohorts pillar; the people being selected are the People directory. On the wire: the library is the cohorts query and editing is createCohort, updateCohort, setCohortActive and deleteCohort (GraphQL reference).