HubSpot Ideas


Custom (non-properties) fields in Forms

The one thing that really annoys me about Hubspot forms is that you have to create custom property if you want to add a custom field to a form.


We have a lot of different forms, most time for just a short amount of time but with multiple entries by the same client.  So we don't want custom properties bloating our contact.   

We would like to be able to add an unlimited amount of form fields that isn't connected to a property.  Just like you for example can do in Gravity Forms or Formidable Forms.

This data could be saved on the form submission itself or be added to the marketing event attendee (in some cases).

4 Replies
Most Valuable Member | Elite Partner

this has come up so many times over the years, like for events where you need to capture meal preferences, etc. and the only solution has been creating custom objects with their own custom properties instead of saving to the contact record. I understand the challenge from HubSpot's pov - without a property, where does this data live in the CRM? and also the flexibility of collecting information that isn't data you would need to report on, filter by, etc.


I can also see the point.


Imagine I have 10 forms with 10 fields each. I would have to create and maintain 100 Ticket Properties.


Maybe sometimes I just a text or pdf file of the form, which will be created as soon as someone filled the form and stored at their Contact Tab, mapped only with the email.


Some other scenario.. imagine I have 50 products and I want to collect the preferences and the needs (specifications maybe) for each product for each Customer. A mess.


@HanzWil I am on board with that.


@Jnix284 I would say that the data could live in some kind of HubDB table or a custom event.  I would say where you store this information should not hold this functionality back. 


This would be such a massively helpful update.....there are many times we want to capture submission data, but don't need it to write to a contact property (or to overwrite contact data). We either end up creating tons of unnecessary/one-time use contact properties which clutter the record, or pushing data to custom objects instead of the contact record (so the CO can contain the clutter).