Deduplication controls how Maestra decides when two customer profiles describe the same person and should be merged. A few settings let you tune that behavior — which contacts must be confirmed before they grant account access, and whether profiles with different unique identifiers can ever be merged at all.
In your point of contact settings, you can choose which contacts require confirmation and which ones grant access to the customer’s account.
Once you turn this setting on, every new contact added through that point of contact will require confirmation or grant account access according to the rule you set. The setting does not retroactively apply to customers already in your database.
If you need existing contacts to either gain account access or move into a “pending confirmation” state, edit those customer profiles through a point of contact that has the desired settings. That re-runs them through the rule.
Unique identifier rules
In the settings of a custom field marked as a unique identifier, you can prohibit merging customers that have different values for that ID.
This is useful when an identifier — for example, an internal CRM ID or a loyalty number — is guaranteed to be unique per person. Blocking merges across different IDs prevents Maestra from collapsing two distinct people into one customer profile just because they share another signal like an email or phone number.
Why this matters
These settings are part of building a single, accurate customer profile — the foundation for precise targeting, a better customer experience, and clean data. 
