How to group users into audiences

Your app serves many people, and some of them belong together, such as one team or one plan.

Each person's memory is already separate. An audience gives a group of people one name.

• An audience is a named group of users. It is either a fixed list of users or a rule over user traits, with 1 to 20 conditions.
• Every app has a default audience, project, that holds every user.
• Every data point goes to the project audience. The audience field on a send takes only project or nothing, and recall does not filter by audience.
• Users have traits: a string key up to 200 characters and a value up to 2,000 characters.
• To keep two customers' memory apart, use one app for each customer. An app key selects one app.

1. Decide which users belong together, such as one team or one plan.
2. Create the audience as a fixed list or as a rule over user traits, with 1 to 20 conditions: PUT /v1/memory/audiences/{slug}.
3. If you use a rule, give your users the traits it refers to.
4. Check who is in it: GET /v1/memory/audiences/{slug}.
5. After you change traits, refresh the members: POST /v1/memory/audiences/{slug}/recompute.

• An audience does not yet limit who reads a data point. A send with audience set to anything but project returns audience-unknown.
• A rule depends on user traits. Check the trait values on each user.

Nadia at Acme is on the pilot team. You make a fixed audience, acme-pilot, that holds Nadia and her colleagues. Her notes still go to her own memory, and the audience names the group.