Unique Properties support for newly created Contact properties
Starting September 21st, we will begin rolling out the ability to set new contact properties to be unique.
Up until now, a user could not set a contact property to be unique. Starting September 21st, we will begin rolling out the ability to set new contact properties to be unique.
Why is this changing?
Historically, HubSpot has provided unique property support for Companies, Deals, Tickets, and Custom Objects; however, Contact records have solely relied on email properties for uniqueness enforcement. Admin users are now empowered to create unique custom properties for Contacts via the UI and developers can do the same via the Properties API, allowing customers to have even more control over their Contacts data. Going forward, HubSpot users can now leverage unique properties to eliminate duplicate records and maintain clean, reliable Contact data.
What do I need to know?
- Only net new properties can be set to contain a unique value.
- Similar to the other object types, the contact object type can only have a maximum of 10 unique properties.
- When converting visitors to a contact record, we will drop any visitor property values that would violate unique property constraints. More information on identifying a visitor available in our developer documentation and knowledgebase.
- At the time of this post, the import tool does not adhere to this new standard, yet. It should be updated in the coming weeks to meet the requirements.
Please let us know if you have any questions by joining the conversation in our community.