Hubspot: Passing different values from dropdown or multi-selection field to Hubspot

Is it possible to pass different values for specific form field selections (dropdowns & checkbox fields).

We have some conversational dropdowns:

I'm a Broker, I'm an Owner/Investor, etc.

We'd like to pass just the following value: Broker, Owner/Investor

Alternatively we want to have values appear for some States and Provinces as their name value on the form, but pass a different value on the back end:

New York > US - New York

Ontario > CAN - Ontario

This would make passing data into HubSpot or other data sources a lot more effective.

Is this possible to do? I don't see it anywhere on the standard configurations

Thanks

Hi Chad,

Thank you for reaching out to us for help. Yes, you can do this by adding additional form fields that will be populated based on the answer from the other fields. These additional form fields will be the ones mapped to Hubspot to pass a different value. Let me show you how to do it:

1.) Add additional Dropdown and Multiple Choice fields to the form and set them as hidden. These fields will be populated with different values depending on the chosen answer from the other fields. For example, if the "I'm a Broker" option was selected on the first dropdown field, the other dropdown field will then be populated with the option "Broker".

2.) For the second dropdown field you added, set its options based on the values you want to pass to Hubspot, e.g. Broker, Owner/Investor

3.) Add a condition to populate the second dropdown field based on the chosen answer from the first dropdown field. You need to create a separate condition for each option you have on the dropdown field

For example, Condition 1 is that if "I'm a Broker" is selected on the first dropdown field, the second dropdown field's value will be set to "Broker". The text you will set on the condition must be the same options you have already set on the second dropdown field.

Then, here's Condition 2 for the other option

You can refer to this guide for more details about this kind of conditional logic.

4.) Next, for the second multiple choice field you added, set its options to the ones you want to pass to Hubspot.

5.) Go back to the first multiple choice field. This is the field that will be shown on the form. For this, we'll use Calculation Values to set each option's values to the options of the second multiple choice field. So for example, for the option New York, you'll set its value to US - New York. Just make sure that the values you'll set here are the same options on the other multiple choice field.

6.) We'll now set a condition to copy the values of the first multiple choice field over to the second multiple choice field if any of the options are selected.

After setting all that up, here's how the form would work:

As I have mentioned, those other fields are hidden on the form. I just set them as visible in my test form so you can see how the conditions work.

7.) Now, you can go to your Hubspot integration and map those hidden fields to your Hubspot fields.

Also, here's the link for my demo form. You can clone it if you want to check the form's backend or if you want to test it out yourself.

Let us know if you have any other questions.

This solution seems like a ton of additional work when most platforms allow you to set your Label value, and your proper data value on fields....

Is there any functionality for this coming in the future?

Hi Chad,

It seems that what you're referring to is equivalent to setting the calculation values of the different options of a field which I have explained in my previous response. On your screenshot, the Label is equivalent to the options set whether for the dropdown field or multiple-choice fields.

The Internal Value is equivalent to the Calculation Values which is the value that will be used for the option that was selected.

As you may have noticed, when you're mapping the fields from Jotform to Hubspot, you can only select the form field itself which means that whatever value is on that field, that's the one that will be passed over to Hubspot. If there's a calculation value set on the field, then that's the one that will be passed to Hubspot. The workaround I suggested is a bit of work indeed but that's the best solution I can come up with for what you're looking to happen with the Hubspot integration.

Let us know if you have any other questions.

Calculation field seems more along the lines of what I'm looking for instead of all the extra work & conditions set up in the first message. Seems like a lot of extra work to just pass a value for a label of a field.

Am I correct in assuming:

If the field label is: I'm a Broker, and I set up the calculation as Broker the field passed into HubSpot (or via email, etc.) will be Broker

This is all I'm looking for

Thanks!

Hi chadmarch,

Thanks for getting back to us. That is incorrect if the field that is passed on to HubSpot is I'm Broker instead of Broker the field would be shown on HubSpot and would be listed as will be I'm Broker as well even if there is a calculation value-added on the field that is only listed as Broker the integration does not get the calculation value-added on the field but instead the real value listed to it. You would need to pass the calculation value to another field just like what my colleague suggested in his previous reply in order to list it as Broker only on Hubspot.

Let us know if you have any other questions.

It's very unfortunate the fields & forms work this way.

Is there any update coming in the future that would add labels and backend values?

Seems like a ton of extra work and calculations / additional fields for something that should be pretty standard for form Label & Value options.

Hello chadmarch,

Thanks for reaching out to Jotform Support. Unfortunately, the feature you're looking for isn't available at Jotform right now. We've gone ahead and escalated your request to our developers, but when or if it's developed depends on their workload, how viable it is, and how many other users also request it. If there are any updates, we’ll circle back to this thread and let you know. In the meantime, I suggest the workaround suggested by my colleagues.

Thanks for your patience and understanding, we appreciate it.