Contacts

Why should I use a datepicker field type for a custom date property?

Last updated: March 1, 2016

Using a datepicker field type for a form field may be better than using a single line text field type. Why? Because two things can happen: visitors would not be able to enter just any old value into the field on a form and segmenting lists using this property will be much easier.

What visitors will see

  • Visitors to your forms won't be able to enter: Jan 1st 2016. Instead, they would click into the field and see a calendar to select a date.

select-day-on-datepicker-calendar-field.pngSegmenting lists

  • When segmenting lists using a single line text field type for your property means you would need to enter all the possible values contacts entered into the form field. You knew they were the same date, but the list tool needs you to tell it that. Using a datepicker field type means all contacts will have the same structured date value and you will only need to select that one single value to segment with. You will also be able to use a variety of date-specific segmentation options.

single-line-text-vs-datepicker-when-creating-lists.pngIf you are creating a brand new contact property with the intention to collect dates as values, this article should suffice. However, if you have an existing custom contact property with a single line text field type and are looking to switch to a datepicker field type, check out this article How do I change a single line text field type to a datepicker field type?

Related articles:

How can I create a custom date property with a calendar drop-down?
What format should I use to import date property values into HubSpot?
How do I import contacts?
How do I change a single line text field type to a datepicker field type?