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

# Duplicate Detection

> Field matching rules to prevent duplicate leads.

Duplicate checks help you avoid selling the same lead twice. When a lead matches your duplicate criteria, it's marked as a duplicate and rejected.

## Global duplicate checks

Global duplicate checks apply to all leads coming in from any source. You define:

* **Fields**: One or more fields to check together (e.g., email alone, or email + phone for a composite match). A lead is only flagged as a duplicate if *all* the selected fields match a previous lead.
* **Days**: The lookback period. A lead is considered a duplicate if a matching value was seen within this many days.

For example, if you set up a duplicate check on email with a 30-day window, any lead with an email that matches a lead from the last 30 days will be marked as a duplicate. If you add phone to the same check, only leads matching *both* the email and the phone will be flagged.

## Source-level duplicate checks

You can also configure duplicate checks at the [source level](/features/sources#source-level-duplicate-checks). These checks only apply to leads coming through that specific source, giving you more granular control.

## Apply to pings

Duplicate checks can also be configured to apply to pings. When enabled, a ping will return a duplicate status, allowing you to reject a lead before it's even posted.

## Matching options

Both global and source-level duplicate checks support additional matching options:

| Option             | Description                                                                                                                                                            |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ignore punctuation | Treats values as matches even if punctuation differs (e.g., "[john.doe@email.com](mailto:john.doe@email.com)" matches "[johndoe@email.com](mailto:johndoe@email.com)") |
| Case sensitive     | When enabled, "[John@email.com](mailto:John@email.com)" and "[john@email.com](mailto:john@email.com)" are treated as different values                                  |