Non-Hubspot form help mapping with labels

[montyrach305]

We're working with a system where we have very few options in terms of changing the HTML for the form to map with Hubspot contact properties.

What's the correct way to map using labels: is it using the for="___"?

<label for="firstname">Not a name</label> 

Thank you so much!

[montyrach305]

Thank you for pointing that out about the for, of course it's connected to the input field. So essentially the label doesn't have any impact on the mapping.

We're struggling, because if we push contacts via the forms API too often, it interferes with the audience building for LinkedIn. We're hoping to use the non-Hubspot forms processing, but the mapping is posing a major challenge due to restrictions for the field ID's in the CMS.

If my label is <label>Type of query *</label>, would its field map to an internal name of 'type_of_query*'?

[Jaycee_Lewis]

Hi, @montyrach305 👋 Thanks for your question. Getting the non-HubSpot Forms tool set up can be challenging as there are several requirements that must be met. You can find the priority order for how the tool scans for matching properties here — Mapping non-HubSpot form fields and HubSpot properties.

Based on your form example:

<label for="firstname">Not a name</label>

This won't map to HubSpot because it doesn't follow either mapping method. HubSpot looks for either:

• An input field with name="firstname" or
• A label with the text "firstname"

The `for` attribute isn't used for mapping. To fix this, you could either:

<label for="input1">firstname</label>
<input type="text" name="random_name" id="input1">

or preferably:

<label for="input1">Any Label Text</label>
<input type="text" name="firstname" id="input1">

If you cannot customize your form this way, you'll need to look at either:

• a HubSpot native form or
• a custom coded version and submit via the Forms API

Talk soon! — Jaycee