Source: https://docs.amadalis.ai/optimization/affinity-settings/

# Configure affinity

Checked against the product’s code on 7 November 2026.

Open **Optimization** > **Personalization** > **Engine** to review [affinity](https://docs.amadalis.ai/reference/glossary/#affinity) configuration. Affinity is a decaying score of recorded actions, not a model that invents a person’s interests.

## Read the active settings

Check **Affinity on** or **Affinity off** and its stated reason. Affinity is on only when the engine has saved settings, at least one thing on the site is personalized for a behavioral [audience](https://docs.amadalis.ai/reference/glossary/#audience), and the site’s personalization service is connected. When it is off, the reason beside **Affinity off** names the first of these that is missing. An editor screen alone does not prove a visitor is receiving affinity based content.

Review what each supported action contributes, how long scores are remembered and the interest categories in use. A shorter memory makes older actions matter less sooner. Merely listing an event’s intended weight in the event catalog does not change these active weights.

## Change the audience boundaries

1.  Review **A visitor joins an audience at**.
2.  Review **and leaves when it falls below**.
3.  Review the safety limits.
4.  Review any setting that replaces the default for one audience.

The first two fields set when a visitor enters and leaves an affinity audience, each as a number between 0 and 1. A saved [revision](https://docs.amadalis.ai/reference/glossary/#revision) lists them as **Join point** and **Leave point**. Separate points avoid repeatedly changing membership near one boundary. [When an audience applies](https://docs.amadalis.ai/optimization/affinity-engine/#when-an-audience-applies) explains the difference between page delivery and recorded membership.

Use **Add an interest** for a supported new interest category. The content catalog and the settings currently in effect can also supply interest categories; an empty manual list does not prove the engine has no interests available.

## Save and review a revision

1.  Change the intended values.
2.  Choose **Save**.
3.  Read **Review this change**.
4.  Choose **Approve & save** if the change matches your intent.
5.  Read the resulting revision and its receipt.

Use **Change history** to inspect earlier revisions, the recorded reason and an offered action to restore an earlier version.

Restoring an earlier version is a new change to the settings, with its own approval. A restore to a blank action weight can currently be refused when the active weight is zero. A restore does not rewind everything visitors did in the meantime. Check [the affinity explanation](https://docs.amadalis.ai/optimization/affinity-engine/) and [content catalog](https://docs.amadalis.ai/optimization/content-catalog/) together before relying on the experience.