Skip to content
Open the app

Targeting with tags and audiences

Not every message is for every student. Tags and audiences let you aim content — a briefing block, an event, a resource — at exactly the group it's meant for, and leave everyone else's view uncluttered.

Two kinds of audience

  • Synced facets (read-only) — courses, degrees, campuses, and cohorts that come in from your student records. You don't manage these; they reflect enrolment.
  • Your own tags — segments you create, like "First in family", "Commencing", or "On appeal", to target groups your SIS doesn't already describe.

Managing your tags

  1. Create a tag

    Add a tag for a group you want to reach, and give it a short label for compact display (for example, a long official term shortened for a chip).

  2. Turn it on or off

    Toggle a tag active or hidden without deleting it.

  3. Use it while authoring

    When you write content, target it by tag so only matching students see it.

Students can self-select some groups

Some role tags are ones students pick for themselves (in the people/groups area of the app). That lets students opt into content streams that fit them — and it means your targeting reflects how students see themselves, not just what's on file.

A note on small groups

Targeting narrowly is good for relevance, but remember that insights suppress very small groups so individuals can't be identified from aggregates. Targeting controls who sees content; it doesn't expose who engaged at an individual level.

Common questions

Why can't I edit courses or campuses?

Those come from your student records and stay read-only so they always match enrolment. Create your own tags for anything they don't capture.

If I don't tag content, who sees it?

Untargeted content is shown to the whole cohort (within its week scope). Tags narrow it; no tag means everyone.

Can I combine a synced facet with my own tag?

Yes — target by campus and a custom tag together to reach, say, first-in-family students at one campus.

Was this helpful?
Need more help?

The fastest answer is usually one question away.

Edit this page on GitHub