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

# Lead list enrichment: Understanding the results

This document describes the outputs generated by [enriching an existing lead list](/builders/enrich-a-list-of-contacts) and explains how those outputs are determined.

***

## Output columns you can expect to see

Your CSV enrichment results will include at least:

* **Contact (Full Name)**
* **Buyer Name**
* **Salutation**
* **First Name**
* **Last Name**
* **Job Title**
* **Contact Email**
* **Phone Number**
* **Relevance**
* **Is Active**

If your CSV included any of the following inputs, we will also include them in the output so you can compare your inputs to Starbridge’s outputs:

* **Provided Job Title**
* **Provided Contact Email**
* **Provided Contact Phone**

The rest of this article focuses on two important outputs: **Is Active** and **Contact Email**.

***

### Quick definitions

* **Is Active:** Whether Starbridge believes the contact should be treated as “active at this buyer.” This is driven by whether we can verify the person works at the buyer, and by whether the email we use for the contact passes a bounce check.
* **Contact Email:** The email Starbridge returns (if any), after enrichment and validation steps like bounce checking.

***

### Which email we use for a contact

For every contact, we pick one email to evaluate, based on what our web verification found:

* If we **confirmed the contact works at the buyer** → we use **our enriched email**. If we did not find one, we use **your provided email**.
* If we **confirmed the contact does not work at the buyer** → we use **your provided email**.
* If we **could not confirm either way** → we use **your provided email**.

Starbridge runs a **bounce check** on this email. You can see the outcome of bounce checks in **Relevance**.

***

### How to interpret “Is Active”

Is Active is based on rigorous web verification and on the bounce check of the email we use for the contact.

* If we **confirmed the contact does not work at the buyer** → **Is Active = false**
* If we **confirmed the contact works at the buyer**, or **could not confirm either way** →
  * **Is Active = true** if the email we use passes the bounce check, or if there is no email to check
  * **Is Active = false** if the email we use does not pass the bounce check

Why we default to Is Active = true when we cannot confirm employment and there is no provided email or your provided email passes the bounce check:

* If a contact exists in your CRM or lead list and we cannot confidently verify they left, we do not want to push you toward inactivating or deleting good data just because the web has no conclusive information.

***

### How to interpret “Contact Email”

* **Contact Email** shows the email we use for the contact (see above), but only if it passes the bounce check.
* If that email does not pass the bounce check, **Contact Email** is empty. We do not fall back to another email.
* We only return our enriched email for contacts we confirmed work at the buyer.

**Email outcomes**

This table explains what you’ll see in **Is Active** and **Contact Email**. Read this table from left to right.

| Web verification | Your provided email | Our enriched email | Is Active | Contact Email |
| - | - | - | - | - |
| Works at the buyer | Any | Passes bounce check | true | Our email |
| Works at the buyer | Any | Fails bounce check | false | No email |
| Works at the buyer | Passes bounce check | No email found | true | Your provided email |
| Works at the buyer | Fails bounce check | No email found | false | No email |
| Works at the buyer | No email provided | No email found | true | No email |
| Could not confirm | Passes bounce check | Not used | true | Your provided email |
| Could not confirm | Fails bounce check | Not used | false | No email |
| Could not confirm | No email provided | Not used | true | No email |
| Does not work at the buyer | Passes bounce check | Not used | false | Your provided email |
| Does not work at the buyer | Fails bounce check | Not used | false | No email |
| Does not work at the buyer | No email provided | Not used | false | No email |

***

### Examples

#### Example A: You see a contact with Is Active = false but your provided email passed the bounce check

* We verified they no longer work at the buyer, so the contact is inactive.
* Their email has not been deactivated. This can happen when a buyer keeps an old email inbox active, often to forward or monitor messages for a departed employee.

#### Example B: You see a contact with Is Active = true, the Relevance says we confirmed they are still employed at the buyer, and your provided email failed the bounce check

* Our verifier found strong evidence the contact works at the buyer, and we found our own email for them that passed the bounce check.
* Because we use our enriched email for confirmed contacts, your provided email's bounce check does not affect **Is Active**, and **Contact Email** shows our email.

#### Example C: You see a contact with Is Active = false, the Relevance says we could not confirm whether they are still employed at the buyer, and your provided email failed the bounce check

* Our verifier could not find strong evidence they work at the buyer. It also could not find strong evidence they do not work at the buyer.
* For contacts we could not confirm, we use your provided email. It failed the bounce check, so the contact is inactive and **Contact Email** is empty.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.