# 12. Clients Duplicates

The **Duplicates** action identifies cases where a client registers more than once, typically using the same email or other key data. This can happen if a client forgets they already have an account or signs up again via different marketing campaigns.

##### Use Cases

1. **Tracking Re-Registrations**  
    View duplicate entries to understand why a client signed up multiple times, whether due to forgotten credentials or different marketing campaigns.
2. **Maintaining Complete Client Records**  
    Ensure all client sign-ups are accurately tracked and linked to a primary record, preserving a full registration history.
3. **Identifying Duplicate Accounts**  
    Only clients with multiple registrations will appear in the **Duplicates** section, allowing for efficient detection and resolution.

##### <span style="font-size: 13pt; font-family: Arial, sans-serif; color: rgb(161, 163, 165); background-color: transparent; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre-wrap;">How It Works</span>

**1. Automatic Detection** As soon as a new registration matches an existing email (or another unique identifier), the system flags it as a duplicate behind the scenes—no manual setup required.

**2. Duplicates Icon** In the main **Clients** table, any row with flagged duplicates displays the **Duplicates** icon in the **Actions** column:

<p class="callout info">**Note**: Clicking this icon opens a page showing all known duplicate accounts associated with that primary record.</p>

**3. Details**

Clicking the icon takes you to a dedicated **Duplicates** screen for that primary client. Here you’ll see all associated accounts lined up side by side, with:

<div bis_size="{"x":143,"y":652,"w":840,"h":119,"abs_x":729,"abs_y":870}" class="_tableContainer_16hzy_1" id="bkmrk-callout-field-descri"><div bis_size="{"x":143,"y":652,"w":840,"h":119,"abs_x":729,"abs_y":870}" class="_tableWrapper_16hzy_14 group flex w-fit flex-col-reverse" tabindex="-1"><table class="w-fit min-w-(--thread-content-width)" data-end="2133" data-start="1706" style="width: 102.619%; height: 118.807px;"><thead data-end="1779" data-start="1706"><tr data-end="1779" data-start="1706" style="height: 29.7017px;"><th data-col-size="sm" data-end="1716" data-start="1706" style="width: 9.36431%; height: 29.7017px;">Callout</th><th data-col-size="sm" data-end="1732" data-start="1716" style="width: 13.8954%; height: 29.7017px;">Field</th><th data-col-size="md" data-end="1779" data-start="1732" style="width: 76.727%; height: 29.7017px;">Description</th></tr></thead><tbody data-end="2133" data-start="1854"><tr data-end="1927" data-start="1854" style="height: 29.7017px;"><td data-col-size="sm" data-end="1864" data-start="1854" style="width: 9.36431%; height: 29.7017px;">**1**</td><td data-col-size="sm" data-end="1880" data-start="1864" style="width: 13.8954%; height: 29.7017px;">**Email**</td><td data-col-size="md" data-end="1927" data-start="1880" style="width: 76.727%; height: 29.7017px;">The duplicated email address.</td></tr><tr data-end="2043" data-start="1928" style="height: 29.7017px;"><td data-col-size="sm" data-end="1938" data-start="1928" style="width: 9.36431%; height: 29.7017px;">**2**</td><td data-col-size="sm" data-end="1956" data-start="1938" style="width: 13.8954%; height: 29.7017px;">**Description**</td><td data-col-size="md" data-end="2043" data-start="1956" style="width: 76.727%; height: 29.7017px;">Key metadata (e.g., affiliateID, deskLabel, projectKey) to distinguish each record.</td></tr><tr data-end="2133" data-start="2044" style="height: 29.7017px;"><td data-col-size="sm" data-end="2054" data-start="2044" style="width: 9.36431%; height: 29.7017px;">**3**</td><td data-col-size="sm" data-end="2070" data-start="2054" style="width: 13.8954%; height: 29.7017px;">**Created**</td><td data-col-size="md" data-end="2133" data-start="2070" style="width: 76.727%; height: 29.7017px;">Timestamp of when each duplicate account was first created.</td></tr></tbody></table>

</div></div>**Next Steps: Resolving Duplicates**

1. **Audit Each Record:** Click into individual client profiles to compare personal details, activity logs, and transaction history.
2. **Merge or Deactivate: Merge**: Consolidate contacts, balances, and documents into the primary profile.  
    **Deactivate**: If merging isn’t appropriate, deactivate the extra accounts to prevent confusion.
3. **Monitor Over Time:** Periodically revisit the **Duplicates** view to catch new re-registrations and ensure ongoing data hygiene.

##### Conclusion

By leveraging the **Duplicates** feature, you can:

1. Keep your client database **clean** and **reliable**
2. Preserve a **comprehensive history** of every registration
3. Prevent fragmented support or billing records

Regular use of this tool ensures that every client interaction is tied back to a single canonical profile—boosting data accuracy and operational efficiency<span style="background-color: transparent; font-family: Arial, sans-serif; font-size: 11pt; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; white-space-collapse: preserve; color: rgb(161, 163, 165);">.</span>

<span id="bkmrk--3" style="font-weight: normal; color: rgb(161, 163, 165);">  
</span>