topic Re: Non-hubspot form with tracking code- Persona and Lead Source in Lead Capture Tools

Non-hubspot form with tracking code- Persona and Lead Source

SSupport7 — Thu, 14 Dec 2023 15:55:23 GMT

I have a non-hubspot form with a tracking code to post the data to hubspot- all is great, except for two fields.

Both are <select> fields and both contain options which match the options available in Hubspot for posting to the "Persona" and "Lead Source" fields.

However, when the form submission is captured the "Persona" field where I choose the option "Sales Rep/Group" gives the error: This value wasn't passed to the Contact record. 'Sales Rep/Group' isn't one of the allowed options. It is though!

For Lead Source, I am not sure what I need to put in my label to make it work, then I have the same problem with the options probably.

Is this a bug? Has anyone got a non-hubspot form to pass data to these specific fields?

Re: Non-hubspot form with tracking code- Persona and Lead Source

karstenkoehler — Thu, 14 Dec 2023 16:36:22 GMT

Hi @SSupport7,

HubSpot might be expecting the internal value here, not the name: https://knowledge.hubspot.com/forms/use-non-hubspot-forms#mapping-non-hubspot-form-fields-and-hubspot-properties

Best regards!

Re: Non-hubspot form with tracking code- Persona and Lead Source

SSupport7 — Fri, 15 Dec 2023 10:13:06 GMT

Thanks for the quick reply.

The article you shared does explain the order in which attributes are checked to match fields, but doesn't explain how options are matched I believe? Currently we match the fields successfully using an invisible label matching the name of the field in Hubspot (with underscores).

I will try internal name in option text node and value attribute. If it works in value attribute, great! Though from previous experiments it seems to prioritize the next node, and ideally I don't want to display the internal name to the user as it's not user friendly.

Re: Non-hubspot form with tracking code- Persona and Lead Source

SSupport7 — Fri, 15 Dec 2023 10:25:15 GMT

Yes, so if I do this I still get the error:
`<label for="a" class="sr-only">persona</label>
<select id="a" name="3rdpartyname">
<option value="persona_5">

Sales Rep/Group

</option>
</select>`

This "works" but is no use from a UX perspective, because how would the user know what this means?

`<label for="a" class="sr-only">persona</label>
<select id="a" name="3rdpartyname">
<option value="persona_5">persona_5</option>
</select>`

I guess the next thing I need to try is to have a completely hidden field for Hubspot's benefit and use JS to update that from a user-friendly field?

Or to try the API instead? API would take more time to get up and running but hopefully once set up would avoid weird workarounds.

Re: Non-hubspot form with tracking code- Persona and Lead Source

SSupport7 — Fri, 15 Dec 2023 11:04:27 GMT

Thanks Karsten Köhler - I have accepted your solution to the question about option values not being accepted- you were right that Hubspot was expecting internal name for options.

To make it workable I went for the approach of having for each <select> a duplicate <select hidden> which Hubspot could see and process. I used JS to update the hidden field with my own field's value on a change event.