Custom (non-properties) fields in Forms

[HanzWil]

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).

[HanzWil]

Hi everyone! My name is Hallie, and I'm a Program Manager on the CXM team. The product team confirmed that this isn't currently on the roadmap, but they will keep it in mind for the future. Please continue to share feedback and use cases on this in the meantime, and thanks for your understanding! 🙂

[Jnix284]

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.

[MSpyropoulos]

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.

[HanzWil]

@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. 

[laurabren]

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). 

[JtenHam]

I am really waiting for this to become a thing.. We have a lot of forms that are used to gather information in a structured way for this particular case. Think of.. ordering a training for example. It's usefull to store some of the info, but it's not necesarry to store the amount of people coming or what timeslot they prefer for the training.

Lots of unnessecary properties.. that also overwrite when the form is filled in a second time. Please let us store the form in full on the Contact record and select what answers should be mapped to a property!

[ACiantar]

+1, needed for our use case

[jstith]

I'm new to HubSpot, but I didn't realize this was an issue until I tried to just add a field for notes and realized I couldn't. My use case is we are meeting people at tradeshows and want to be able to quickly add the new leads to the CRM and make a few notes right on the form without having to leave the form. 

It seems to me that if a playbook and an email can be added to the contact record, why can't a form submission be treated the same way and we'd just be able to click on that activity and see the entire form submission. The form itself should be storing the info, not the contact record. If this was the case, we could map anything or nothing to the contact record in a property if we so desired, but the form submission would still show up in the activity feed. 

[ecandgs]

+1 - this would be great to have. We deal with the same issue of "throw away" data clogging up company and contact properties. It makes a mess of things and then other teams get overwhelmed by the number of properties available. I know I can lock down access to certain properties, but this could all be solved by allowing form fields that are unmapped.

[bCubbit]

+1 - in many cases there is no need to store information in a property. Capture it all and add it to a note on the object activity feed. This makes it filterable and actionable as well without the need for a property for every question ever asked. We opt for Typeform over Hubspot forms + 3rd party integrations to get around this, but it would be great to be able to centralize everything.

[cbz]

Agreed. I need to be able to collect information without tying it to any property. If it must be connected to something, it could just create a "Note" (whereby any text typed in a form field becomes a new "Note" in the Activity Log either for the Company or for the Contact.). 

[moniserie]

Agreed. I am unsure why the information can't be kept in a csv/Excel behind the form itself, like a Google form and map only the properties you designate.  I ended up utilizing Google forms for the forms that I do not need to make ALL those extra properties for. I then use Zapier to "zap" only the information I want back into HubSpot properties.

[Joe_From_Boston]

Could this data be added to the contact record via a Note?

[ABeian]

+1

[JWebb99]

This would be a greatly appreciated feature.  Forms are not always about sortable. refernceable data.   I tried adding a simple yes/no radio button but can't do it without tying it to a connected property.

[JaredNZ]

Our current workaround for this is using two forms.

We have a form on Formstack that collects all of the information we would like (many non-property connected fields),

then our main form on HubSpot is filled out with the Formstack integration. The property connected fields are completed in the Hubspot form and the Formstack form can be used to see all the one-time collected data.

I would love to see non-property connected fields in HubSpot Forms

[JB17398]

It's ridiculous that you still need to use a 3rd party forms tool to capture custom questions that are relevant to the form submission but should not be stored on the contact record. There needs to be a way to ask these questions and just show the response as part of the form submission entry on the timeline, plus use the data in workflow automations (a very common use case for our clients, as an HS agency partner).

[hhiggins]

Hi everyone! My name is Hallie, and I'm a Program Manager on the CXM team. The product team confirmed that this isn't currently on the roadmap, but they will keep it in mind for the future. Please continue to share feedback and use cases on this in the meantime, and thanks for your understanding! 🙂

[BCox9]

+1 for this request too! 

We supply software solutions, for a number of which we often offer a free trial. Some software requires us to collect several users' names and email addresses, and a specific role type they fulfil. We often face delays receiving this information when we follow up with the customer, and don't need this on the customer record, we just need it for that particular trial request. It would be great to be able to add fields that then just sit specifically within the form response entries.