> For the complete documentation index, see [llms.txt](https://docs.morpht.com/convivial-for-govcms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.morpht.com/convivial-for-govcms/concepts-and-tools/personalisation.md).

# Personalisation

The site can show different things to different visitors. Personalisation is built from three layers, each usable on its own.

See personalised components on the demo site:

* <https://govcms.convivial.io/demo/modifiers/audience-filter>
* <https://govcms.convivial.io/demo/components/personified-content>
* <https://govcms.convivial.io/demo/components/recommendations>

![A component shown only to a chosen audience](https://3733701002-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3fBWwpuJPUqPpT2ulMXp%2Fuploads%2Fgit-blob-0a024466a0922e3f1f788c19190a6455ab668193%2Fm-audience-filter.png?alt=media)

## Classification

Pages carry metadata that says who and what they are for:

* **Audience** — a content type in its own right; pages reference the audiences they are written for.
* **Stage**, **Goal**, **Intent** and **Intents satisfied** — taxonomy terms on the **Metadata** tab describing where a visitor is in their journey, what they are trying to do, and what reading this page tells us about them.

None of this changes what a visitor sees by itself; it is the data the other two layers use. Fill it in consistently or leave it empty — half-classified content personalises badly.

## Visitor context

As a visitor moves through the site, their choices and behaviour build up a context: the audience they picked, intents inferred from the pages they read, preferences they set. It is stored in the visitor's browser and sent to no one, which is why personalisation keeps working for anonymous visitors and why clearing the browser resets it.

## Personalised output

* **Audience Visibility Modifier** — the simplest tool: a component shown only to visitors in the selected audiences, with a **Default audience** for everyone else. See [Modifiers](/convivial-for-govcms/concepts-and-tools/modifiers.md).
* **Personified Content** — a template rendered against the visitor's context, for a greeting or a message that varies by audience.
* **Personified Data** — fetches JSON from an endpoint, passing values from the context, and renders it with a template: a personal feed of content.
* **Recombee Scenario** and **Recombee Search** — recommendations and search results ranked by the Recombee engine from the visitor's behaviour. Needs a Recombee account and developer set-up.

The components are described in [Advanced components](/convivial-for-govcms/content-editing/components/advanced-components.md). Two rules of thumb: prefer the Audience Visibility Modifier wherever it does the job, and always give personalised components a sensible default so a first-time visitor sees something useful.