> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/lead-board-scoring/how-lead-scoring-works-in-emarketeer.md).

# How lead scoring works in eMarketeer and tutorial

How to set up lead score rules step by step, where to view each contact's score, and how to filter contacts by score.

Lead scoring shows how sales-ready your contacts are by awarding points based on persona fit and engagement.

In this article, you learn how to set up lead score rules step by step, where to see each contact's lead score, and how to filter contacts by their score.

## Introduction: what is lead scoring?

With lead scoring, you see how sales-ready your contacts are and identify marketing qualified leads (MQLs). You award points based on how well a contact fits your buyer persona and how engaged they are with your marketing. You decide which criteria matter and set up score rules around them. The higher the score, the more sales-ready the contact, and the more confidently you can hand them to sales.

With lead scoring you can:

* Set up rules based on marketing engagement, contact card fields, and contact lists.
* See each contact's lead score on every contact list and on the contact card.
* Filter contacts by score — for example, all contacts above 50.
* Export contacts as a file and hand them off to sales.

## Key terminology

* **Lead score:** the number of points a contact has.
* **Score rules:** the criteria a contact must fulfill to gain or lose points.
* **Score set:** a container for one or more score rules. Use score sets to group rules — for example, one set for engagement rules and one for buyer persona criteria. If you sell more than one product, you can use a score set per product.
* **Explicit scoring:** rules based on persona attributes, such as demographics or company profile.
* **Implicit scoring:** rules based on behavior, such as clicks.

## How to use lead scoring in eMarketeer

Before you head into eMarketeer, decide on your lead scoring model. eMarketeer ships with some default score rules to give you a head start, but no model fits every business. Tailor the rules to your sales process, and build the model together with your sales team.

[Guide: how to build a lead scoring model and common lead scoring mistakes](/guides/lead-board-scoring/how-to-set-up-your-lead-scoring-model-and-lead-scoring-mistakes.md)

### You can score on the following in eMarketeer

Marketing engagement:

* Any engagement
* Email — opened or clicked a link
* Form — visited, submitted, or answered in a specific way
* Landing page — visited or clicked a link
* SMS — clicked
* Web Tracker — visits. To score web visits, [install the web tracker script on your website](/references/references/web-tracker/installing-the-web-tracker-script-on-your-website.md).

Information on the contact card:

* Any field on the contact card. You can score on whether the field has any value or matches a specific value — for example, job title is set or job title equals CEO.

Contact lists:

* Whether the contact is in a specific contact list.

## How to set up score rules in eMarketeer

### Set up score rules step by step

{% stepper %}
{% step %}

### Open lead scoring

Click the settings icon at the top right, choose "Account Settings", and then "Lead Scoring" in the left-hand menu. This view shows all your score sets and their active status.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-8230da602d4cba1b34756fc4a671eb628a49670c%2Fhow-lead-scoring-works-in-emarketeer-lead-scoring-score-sets.png?alt=media" alt="Lead Scoring in Account Settings, listing score sets and their status."></div>
{% endstep %}

{% step %}

### Add a score set

To add your own rules, click "Add Score Set." Name the score set after the kind of rules it contains — for example one set per product, or a set for engagement rules. You can also add an optional description.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-ccf8503450936793d8e1801b82ee8666a6d7a9ce%2Fhow-lead-scoring-works-in-emarketeer-new-score-set-name.png?alt=media" alt="New Score Set page with name and description filled in."></div>
{% endstep %}

{% step %}

### Add a rule

Click "Add New Rule" and give the rule a clear name in the Rule Name field.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-73c169d911005ffd0c6322125cab61f742c2e6ce%2Fhow-lead-scoring-works-in-emarketeer-new-score-rule-name.png?alt=media" alt="New Score Rule dialog with a rule name and the list of condition categories."></div>
{% endstep %}

{% step %}

### Build the rule criteria

Rules are built the same way as filters in eMarketeer. Under "Add condition", choose a category — for example engagement, contact fields, or contact list membership.

For a webinar registration, choose Engagement and set Engagement type to Form.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-a87040e98a7e8f0de73252504c4a52662f43acae%2Fhow-lead-scoring-works-in-emarketeer-score-rule-engagement-types.png?alt=media" alt="Engagement type drop-down with Form, E-mail, SMS, Landing Page and other types."></div>

Under Selection, pick the specific form, and set Condition to Submitted.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-5d7bc15a223a6005846124c809173d58d286c1de%2Fhow-lead-scoring-works-in-emarketeer-score-rule-form-submitted.png?alt=media" alt="Add condition dialog for a submitted webinar form."></div>

Next, consider occurrence — how many times the contact must do the action to get the points: at least, at most, or exactly a number of times. Then consider time frame — for example, only the last 30 days. Click "Add condition."

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-13ebbcbbce58747536fb6b22ca151131935ba5c1%2Fhow-lead-scoring-works-in-emarketeer-score-rule-occurrence.png?alt=media" alt="Occurrence options At least, At most and Exactly."></div>

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-5fee34d3fc22ab2555d68cede1160da8202f729d%2Fhow-lead-scoring-works-in-emarketeer-score-rule-time-frame.png?alt=media" alt="Time frame options Any time, Last X days and Between."></div>

To narrow a rule further, add another condition. For example, the contact signed up for the webinar AND visited a landing page three times. Choose a category again and repeat the steps for the second condition. The conditions are combined with AND. Click the AND chip to change it to OR.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-317dccecd518ce668d29b49d28a01add84b17d5b%2Fhow-lead-scoring-works-in-emarketeer-score-rule-combine-conditions.png?alt=media" alt="Score rule with two conditions combined with AND."></div>
{% endstep %}

{% step %}

### Apply the rule

Click "Apply."
{% endstep %}

{% step %}

### Set the point value

Next to the rule, set how many points the rule is worth. Choose "Remove" instead of "Add" to remove points. Use negative points for behavior that is unlikely to lead to a sale — for example, "student" as job title, a visit to your careers page, or a country you cannot ship to.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-068d967b3e281419ecef92cdd14875a0e9b75272%2Fhow-lead-scoring-works-in-emarketeer-score-rule-points.png?alt=media" alt="Score rules with Add or Remove and a point value."></div>
{% endstep %}

{% step %}

### Activate the score set

When the score set has all the rules you want, switch it to Active and click "Save Changes." Scores are calculated for each contact. After adding or editing a rule, there can be a short delay before scores update — usually a few minutes, depending on database size.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-59c1b9a531e7da349985b48e233c8da64c9f811c%2Fhow-lead-scoring-works-in-emarketeer-new-score-set-activate.png?alt=media" alt="New Score Set switched to Active with the Save Changes button."></div>
{% endstep %}
{% endstepper %}

### See each contact's lead score and score breakdown

Contacts are scored when they fulfill any of your rules. You see the score on every contact list and on the contact card. On the contact card, the "Lead" tab shows how the contact earned their points. The "Lead score over time" graph shows the score over time. Below the graph, a breakdown lists every fulfilled rule with its points and score set.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-562b44394d8ba43a238c6e2fc74d8d17ae60eb8c%2Fhow-lead-scoring-works-in-emarketeer-contact-card-lead-score.png?alt=media" alt="The Lead tab on a contact card, showing the lead score over time and the rules the contact fulfilled with their points."></div>

### Filter out your MQLs and hand them to sales

To find contacts that reached a specific score — say 80 or higher — use filters. Go to Contacts, click "Filter", and choose "Score" under Add condition. Set the condition to "Greater Than" and enter your threshold, for example 80. You can then list contacts above or below your sales threshold.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-38d4ba2770a240ad494a75dcbaa369358fe18dbe%2Fhow-lead-scoring-works-in-emarketeer-filter-contacts-by-score.png?alt=media" alt="Filter contacts dialog with a Score condition set to Greater Than 80."></div>

When you select contacts, the "Export" and "Bulk actions" buttons appear at the top of the list. Use bulk actions to update the selection — for example, add the contacts to a list. Use "Export" to download the contacts as a file ("Export as file") or send them to a selection or project in SuperOffice ("Export to CRM"). For SuperOffice export, the contacts must already be known in SuperOffice.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-2838740a4023f3ef0ae826c91bcda1b8ec34c433%2Fhow-lead-scoring-works-in-emarketeer-contacts-selection-export-bulk-actions.png?alt=media" alt="Export and Bulk actions buttons above a contact list with three contacts selected."></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/guides/lead-board-scoring/how-lead-scoring-works-in-emarketeer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
