topic Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon. in Lead Capture Tools

Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

TPesach3 — Mon, 01 Jul 2024 18:32:21 GMT

Hi everyone,

I'm experiencing an issue with mapping a multiple-choice field from a Webflow form to HubSpot. Here's the situation:

Issue: When a user selects multiple options on the Webflow form, the data is being submitted, and I can see the submission in HubSpot. However, the selected options are not populating the corresponding HubSpot property. Instead, it comes through as a single value "on" followed by the selected options in a single line, like this: on Option1, Option2, ...
Form Setup: The Webflow form allows multiple selections, and the corresponding HubSpot property is set as a "Multiple checkboxes" field.
Integration Method: I'm using Webflow's native integration with HubSpot.
Field Type: The Webflow form uses a <select> element with multi-selection enabled.

Here's what I have checked so far:

HubSpot Property Configuration: Confirmed that the property in HubSpot is set to accept multiple values.
Field Mapping: Double-checked that each Webflow form field is correctly mapped to the corresponding HubSpot property.
Captcha Settings: Disabled captcha on the HubSpot form to ensure it isn't blocking submissions.

Despite these steps, the multiple-choice selections are not populating the correct HubSpot property. Instead, I only see a single value with all selected options concatenated together. Could someone guide me on what might be going wrong or suggest any additional settings I should check?

Thanks in advance for your help!

Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

Jnix284 — Mon, 01 Jul 2024 18:36:06 GMT

@TPesach3 can you share a screenshot of the multi-checkbox property in HubSpot showing the concatenated together result from the form submission? and the same property with multiple selections from a contact that didn't submit via the form for comparison?

It sounds like the only viable solution would be a custom coded action (requires ops hub pro) to check the single value string and update to the individual selections - this is definitely along the lines of a bug or unintended consequence of the integration, I'm not sure if that would fall on Webflow or HubSpot to fix it.

Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

TPesach3 — Mon, 01 Jul 2024 18:52:54 GMT

Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

Jnix284 — Mon, 01 Jul 2024 18:59:08 GMT

Thank you @TPesach3 this is helpful - a typical multi-select property would look like this:

It's not showing an error, usually if non-included values are contained in a property it would have a red outline to indicate that the values don't exist for that property.

As I mentioned above, the only viable solution would be a custom coded action (requires ops hub pro) to check the single value string and update to the individual selections - this is definitely along the lines of a bug or unintended consequence of the integration, I'm not sure if that would fall on Webflow or HubSpot to fix it.

Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

ALJimenez — Tue, 02 Jul 2024 19:57:59 GMT

We had the same issue with our Webflow forms not mapping multiple choice fields correctly via their HubSpot app.

After weeks of back and forth with their support, they finally admitted it's a glitch and that the app has very limited support. The Webflow support team is listed as the support contact in their app marketplace, but it's a third party developer and it apparently has a lot of issues. The Webflow support rep said they have a native app they built out themselves, but they push the third party one to HubSpot users because theirs is even less functional.

In the end we opted to simply embed the HubSpot forms directly. They're all working perfectly now.

Re: Issue with mapping multiple choice propery - Webflow<>Hubspot addon.

Jnix284 — Tue, 02 Jul 2024 23:56:24 GMT

Thank you for sharing this context @ALJimenez, this is really helpful to understand.