Great minds think alike

Migrated from legacy feedback forum with 39 votes.   There currently isn't a way to A/B test forms. I'm assuming other users out there would be interested in A/B testing whether or not certain fields create higher form submission drop off than others. ...read more

Currently there is no way to re-arrange the depenedent fields within the form. This makes it very tedious to edit forms after. The only way to move them is by deleting previous ones.   It should just have the same object orientated nature that is present in all of forms API. ...read more

The new auto-formatting and validation feature for phone numbers is a step in the right direction.   However, the current integration seems to be missing the mark with regard to user experience. I was unable to find any articles or posts in the Help Center announcing the new auto-formatting feature. The only Knowlege Base article that pops up when searching "phone number validation" is a detailed breakdown of editing default contact properties, and then there is only a reference to the validation and formatting being applied "automatically by Hubspot based on the country code."   This feature is certainly a step in the right direction, but several improvements are needed to improve the user experience and make the feature more functional overall (noting that recent comments on an "old" idea thread are already being discussed here; skip to page 7).   Suggested improvements include:   Global Setting to Enable/Disable auto-formatting at the account level - currently, the feature is enabled by default with no disable setting available Global Setting to assign a default Country Code - currently, the Country Code must be selected manually for every new contact (see screenshot below) Bulk edit phone numbers to apply Country Code format & validation -- currently, only able to apply formatting & validation when editing one individual contact at a time OR when adding to new contacts manually added (not via web forms -- this is needed, too) Retain "number only" format for export and/or sync to other apps or integrations to remove non-number characters (parentheses, plus sign, spaces) Default behavior of phone number formatting & validation when creating a new contact:     There are likely other enhancements that other users, especially those not based in the US, would appreciate. ...read more

we have restricitive requirements here in Germany (Double-opt-in) for emails. I would like allow customers to sign up the Newsletter (e.g. in the Footer) and fill in a contact form on the same page. If I activitate the double opt-in, both actions the form and the NL will trigger the opt-in workflow, which does not make sense. I just want the NL form to trigger this process.. Turning Double opt-in on or off per page does not help here. If we could trigger double-opt-in Workflow at the form level, all problem would be solved...   ...read more

I would like to add a Lead Flow to my page, but don't want to have my visitors fill in their email addresses. Can you make this optional (even recommended) instead or required? ...read more

Currently, there is no option to allow for the form to appear as the first thing the visitor sees on the pop-up. The visitor must first click on the pop-up and then the form appears. It seems more like a pop-up CTA not a pop-up form. One less step for the visitor would be for the form to just appear as the pop-up instead of a CTA first appearing and only when clicked will the form appear. When creating the 'pop-up form' you could have the option to have the form appear after the CTA or without a CTA. Thanks for your consideration!  ...read more

IMPORTANT: Not "Dependent Fields".   Please see Gravity Forms' conditional logic functionality for example: https://www.gravityforms.com/form-conditional-logic/   At present, HubSpot "Dependent Fields" can serve new form fields based on a selection made in a previous form field.    "Conditional Logic", however, serves different form field options based on a selection made in a previous form field. This is an important distinction as it requires only one "Property" for the options, regardless of the initial form field selection.   If I'm not clear, here's an example:   Property 1: Location Property 2: Duration   User selects from a Location dropdown. Location options are "Madrid" or "London".  We only offer "4 Weeks" and "6 Weeks" for "London", but offer "4 Weeks" or "12 Weeks" for "Madrid". "Dependent Fields" will serve Duration upon a Location selection, but all options will be shown, even though we do not offer all Duration options for both Locations.    HubSpot recommends we create a new "Property" for each Location. This is not feasible when there are many Locations.   "Conditional Logic" simply serves the appropriate form field options based on the Location selected. So when selecting "London" the options shown would be "4 Weeks" and "6 Weeks", and for "Madrid" only "4 Weeks" or "12 Weeks" would be shown, but they would all populate the same "Property". Duration.   Please upvote.  ...read more

Hello there,    It would be great if we had the option to make form fields autocomplete ; for adresses, using the Google Maps autosuggest could do something like that :  We have a lot of trouble treating duplicates and typos, which would be resolved if we could count on adresses being a unique match thanks to set values.    Thanks a lot! ...read more

Dependant form fields are a great way of showing users different form fields/properties based on their selection in another.   In some situations, however, we really need to be able to show a subset of the values within one property based on the selection in another.    For this we need to be able to create rule-based, conditional or dynamic dropdown fields that are also dependant on other properties.    Forms are one use case for this, but some users also wish this was supported in the CRM UI, to assist internal users in making the right selections quickly. ...read more