Collect data in a form without needing to create a property
We are an events company and use HubSpot to manage the event registration and delivery. A lot of the time this involves asking specific questions, getting menu orders for dinners etc., however when we create a form, we have to create a new property each time to collect this information, as they are all unique to each event.
It would be incredibly useful if there was a way to collect information in a form, without needing to have it assigned to a property.
Currently our properties have grown exponentially and the only way to handle this is to delete them after each event, however it seems incredibly inefficient to create and then delete properties like this and at such high frequency.
I do agree it would be nice to have one-time use fields that didn't require a property, given the database nature of HubSpot, I'm not sure how that would work out.
Have you looked at using an integration with a survey app to see if it can streamline this process?
One of my personal favorites is Typeform, which is very user friendly, easily integrates on your website, and can capture more long-form content for a single event, while still updating relevant contact properties in HubSpot (you choose what questions are connected to HubSpot properties).
Here is the link to Typeform in the app marketplace so you can learn more about it:
Hi @Jnix284 , thanks for the suggestion. I have looked into this and, unfortunately, it still means that any information not assigned to a property doesnt sync over to their contact record (which would be much easier than having to log into the third party platform each time) - and we have to pay to use an integration that covers our requirements!
I come from a background using a different CRM, Slate, that is built for Higher Education (typically admissions offices). Slate solves this problem by storing the form response, then additionally copying the values over to the person record if the form question is "mapped". Otherwise, the data stays within that specific form response. It is still accessible using a query though, since the response's secondary key is the person's primary key.
I wish Hubspot would implement something like this so we could take form responses for events without having to store information like "Would you like chicken or fish?" on their contact record.
This would be great functionality to have. We also use Slate, and the mapped/unmapped field functionality is very nice and logical. Forms designed to be submitted multiple times with different information are problematic in HubSpot. For a "Contact Us" form, I might want the form to populate the contact's name and email if known, but I don't want the form to populate the last message they sent.
I can't wrap my head around even a simple "Contact Us" Form.
Which department do you need help from (Sales, Service, Etc) Service? Great! What seems to be the issue (order tracking, order cancellation, etc) Order Tracking. What is your order number?
It would make so much more sense if there was a Form object where all this data would live that could be linked to a contact object....or for those with any knowlege of normalized databases:
Form Table --Form_ID --Form_Name --Form_Description
I agree with this. We have a couple of particular services where we need to collect a bunch of additional specific info in order to provide the person with a proper response back. We don't need to be able to use the responses for filtering, reporting or anything. The info is purely for 1 time use.
Form submissions display as a logged activity on a record, so just being able to see the answers there is all we need. We don't need our 20 questions to be properties.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
