Non-HubSpot Form property name changes - Sync issues

Smart CRM & Sales Hub CRM
1

There was a recent change to the “name” of a field on our website form submission contact us page and that information is not syncing to the native HubSpot property “Message” as it was before. The internal name has not changed in HubSpot (HubSpot does not allow changes to their native properties) and do not understand why there is a disconnect. It is looking for the property name not the internal name. Has anyone else experienced this and found a way to resolve without needing to create a custom property and remap?

2

Hi @SMcGoldrick, I hope that you are well!
Thanks for reaching out to the HubSpot Community!
So that we help you the best we can, could you please share your form HTML?
For information, here is a related article “Use non-HubSpot forms”.
And you might be interested in this post “Troubleshooting non-HubSpot Forms”.
I’d love to put you in touch with our Top Experts: Hi @evaldas, @Stephanie-OG, @Anton and @alyssamwilie do you have tips to share with @SMcGoldrick, please?
Have a wonderful day and thanks so much in advance for your help!
Bérangère

3

Hi @SMcGoldrick,

As far as I know, if you would like to avoid creating a custom property, then you would need to update your form so that the “name” attribute on the form field is switched back to “message” and the label can be whatever the new value that needs to be seen by the visitor - assuming that was the reason for the change.

Otherwise it would need to be a custom property. If you end up going that route you could create a workflow to copy over all the values from the original “message” property to the new custom property to make the records consistent.

Hope this helps!

4

The internal property name was never changed on the form only what was seen by the visitor filling out the form. I am trying to avoid a custom property with workflow automations.

5

I found the portion in the HTML if that is what you were looking for and reading through the articles you suggested.

<label for=“et_pb_contact_message_0” class=“et_pb_contact_form_label”>What can we help you with?</label>
<input type=“text” id=“et_pb_contact_message_0” class=“input” value=“” name=“et_pb_contact_message_0” data-required_mark=“required” data-field_type=“input” data-original_id=“message” placeholder=“What can we help you with?”>
</p><p class=“et_pb_contact_field et_pb_contact_field_6 et_pb_contact_field_last” data-id=“privacy” data-type=“checkbox”>

6

Thanks for sharing your code, that helps understand the situation better.

You will see that there is a “name” attribute for that form field with the value of “et_pb_contact_message_0”.

name="et_pb_contact_message_0"

This was likely the same (or very similar) name attribute before the form field update and the reason why the automated map worked was because likely HubSpot detected the label “Message” and used that for mapping (instead of the name attribute).

Now since the label of the field has been updated, neither the name nor the label is producing any matches among HubSpot properties.

If you would like to completely avoid a custom property, then you could try utilizing some JavaScript to manipulate your form:

  1. You would first change back the form label to say “Message”.
  2. Then you would add a script that would make that original label (the portion below) invisible for the visitor.
    <label for="et_pb_contact_message_0" class="et_pb_contact_form_label">Message</label>
  3. Finally, add a span right above that field that would look like a label, but would not be attached to that form field - that is where you could have the thext “What can we help you with?” show up.
7

Thank you for this!