# Trailspark Leads

> Source: https://docs.trailspark.ai/destinations-rules/trailspark-leads-overview

## Overview

**Trailspark Leads** is a second, optional list alongside Trailspark Accounts: one row per person, so you can see who at a scored account is engaged. It is **off by default** and available on every CRM Trailspark Accounts supports.

## Turning it on

Turn it on from the **Destination** tab of your CRM's page, once your CRM is connected. The **Trailspark Leads** card has the switch, described on screen as "Adds a second list with one row per person, so you can see who at an account is engaged."

**Which scores get a person onto the list** controls who gets a row. By default, only people currently scored **Hot** do, so turning this on doesn't flood your CRM with every person Trailspark has ever seen.

**Account rows always update before person rows.** If both lists have work waiting, a backlog of person rows can delay person rows. It can never delay an account row.

## How people are matched

Trailspark matches a person to your CRM by **email address**, against your CRM's own contacts. A person with no email on file, or one Trailspark can't match, still gets a row, and Trailspark keeps checking for a match.

## Score status on a person's row

- **Current**: the row reflects a live score.
- **Merged**: your CRM merged this person's contact into someone else's. The row is marked **Merged** once, and then left alone for good. It is never updated, deleted, or brought back. This is deliberate: a merged person's row is finished, not an error to fix.

## Erasing a person's data

If you erase a person's data in Trailspark, their row on Trailspark Leads is **deleted**. This is the only reason Trailspark ever deletes a row here. It doesn't touch their contact in your CRM; that record is yours to remove separately if you want it gone too.

> [!WARNING]
> Erasing a person in Trailspark deletes their row here, but it does **not** stop them from getting a row again. Erasing someone's data does not yet stop them from being scored as a live person in Trailspark, so if they are still being scored, a later update can add a new row for them. Deleting a live, still-scored person is separate work Trailspark doesn't yet offer.

## Next steps

- [Trailspark Accounts overview](https://docs.trailspark.ai/destinations-rules/trailspark-accounts-overview): the account list every person row links back to
- [Which accounts appear, and what happens after](https://docs.trailspark.ai/destinations-rules/which-accounts-appear): which accounts get a row, and what happens after
- [Connection health](https://docs.trailspark.ai/destinations-rules/trailspark-accounts-connection-health): how each list's backlog is reported
- [Your Trailspark Leads board on monday](https://docs.trailspark.ai/destinations-rules/trailspark-leads-board-monday): the monday-specific details