Skip to main content

Expand the audience selector to filter on groups and results from other modules (Audience selector v2)

The audience selector is used across the platform, for events, surveys, forms and other content. Today it can only filter on user properties. Organisations already have meaningful audiences elsewhere: people who joined a group, finished a course, attended an event, filled in a survey, or completed onboarding. Those audiences cannot be reused when targeting new content.

Desired solution:

The same audience selector, everywhere it appears, can filter on a much wider set of sources:

  • Default user properties

  • Custom user properties

  • Community properties

  • Results from other modules

    • Organisation groups: member of a group, or not a member

    • E-learning: completed a course, or did not complete it

    • Events: attended an event, or did not attend

    • Surveys: filled in a survey, or did not fill it in

    • Onboarding: completed onboarding, or not completed

    • The same pattern for other modules

The audience stays in sync with the source. Selecting “member of group X” includes people who joined later and drops people who left. The same applies to course completion, event attendance and the other results above.

Document folders will use this selector too to set who can see a folder. See Use the audience selector to set who can see a document folder.

Impact:

  • Admins no longer rebuild an audience by hand each time group membership or a module result changes

  • Less risk of reaching the wrong people, or missing people who recently joined, attended or completed something

  • Follow-up workflows become possible from the same selector: a survey for everyone who attended an event, a reminder for everyone who did not finish a course, a form only for members of a group

Use cases:

  • An organisation has twelve public professional groups that employees join themselves. To invite the members of one group to an event, or to send them a survey or form, the group itself is selected as the audience. No user property has to be set on each member first.

  • A communication group organises its own events. The event is targeted at the members of that group, so only they see it.

  • After a course, a short survey goes only to people who completed it. People who have not finished the course can be reached separately.

3 comments

Log in to comment and vote

Comments3

  • Margje Buren

    •

    Oct 26

    •

    Merged request

    •

    3 votes

    Allow targeting audiences by "primary function" and "community" attributes

    Organizations can define whether a role is a "primary function" and can assign users to communities, but these attributes are not currently available as filters when selecting a target audience or when downloading results. Use case: A user is a member of Community 1, Community 2, and Community 3, with Community 2 set as their primary community. When this user completes a partially anonymous survey, their response is grouped under Community 2.
    • Ronald Bruin

      •

      Oct 9

      Another use case:
      A user is a member of Community 1, Community 2, and Community 3, with Community 2 set as their primary community. When this user submits a form for location A, the submission is only visible to the moderators of community 2.

  • sjrdbkkr

    •

    Aug 24

    •

    Merged request

    •

    1 vote

    Evenementen op communicatiegroep niveau

    Onze communicatiegroepen organiseren zelf ook evenementen. Er is nu geen handige manier om dit in te richten. Het zou mooi zijn dat zij zelfstandig evenementen kunnen aanmaken die alleen voor die groepen te zien zijn.