> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conversion.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scoring Settings

> Choose which contacts to score, set score ranges and tiers, and write scores to contact fields.

Open a score and go to the **Settings** tab.

## Contacts to score

Score **All contacts** in your workspace, or only **Contacts in an audience**.

Membership is checked on each scoring run. Contacts who leave the audience stop being scored, but keep any values already written to their fields. Contacts who join are scored on the next run.

***

## Ranges and tiers

Fit and engagement each have a **Minimum score** and **Maximum score**, which default to −100 and 100. A contact's score never goes beyond its range, however many points they earn. Each range must include 0.

The total score's range is the two ranges added together, so it isn't set separately.

Set where tiers B and A (or 2 and 1) start. Tier C (or 3) covers everything below. By default, the second tier starts at 20 and the top tier at 60.

<Note>
  Range and tier changes apply after you [publish](/product-docs/scoring/publishing).
</Note>

***

## Output fields

Write scores to contact fields so you can use them in [audiences](/product-docs/audiences/overview), [workflows](/product-docs/workflows/overview), and [syncs to Salesforce](/product-docs/sync/salesforce/syncing-out). You can map any of these outputs:

| Output               | Field type |
| -------------------- | ---------- |
| **Fit score**        | Number     |
| **Engagement score** | Number     |
| **Total score**      | Number     |
| **Fit tier**         | Text       |
| **Engagement tier**  | Text       |

Select an existing field or create a new one. Output fields are optional: scores are always available on the score's pages.

* Fields update only when a contact's score or tier changes, and field changes can trigger workflows like any other update.
* Mapping changes apply immediately, without publishing.
* Changing a mapping doesn't clear the previous field.
* Other tools and people can still edit a mapped field. The next change to the score overwrites it.