Hi, we are looking to update our forms and find away to reduce creating lots of duplicates. Essentially we need the logic to say… if a form is on one landing page it would show these properties, and if on a different landing page a different set of properties. I don’t believe this is a fearture that hubspot currently has. Has anyone found a work around for this? Or could they offer some suggestions.
Hey @AElrington There’s no out of the box way to do this, but there’s a couple of ways this could be achieved, but would require some custom javascript to create.
The two ways I can think of are:
1. Using a hidden dependent field. If your main field is hidden, but has a dependent field associated with it, the main field will be hidden but any dependent fields can still be shown. For example you could have a custom property of “form page”. When this has a value of your specific page it could show additional fields based on the specific value.
The custom part here is getting that value into the hidden field, you would need to create some custom Javascript on the page to pass this value to the hidden field, otherwise it will have no way to determine the value for that page.
2. You could customise the form embed code to display specific form information dependent on the page itself.
Both of these would require some development to implement however and wouldn’t be officially supported by HubSpot.
As far as I know there is no way to do this using standard HubSpot features. I would imagine that one of the form apps in the app store would have functionality like that, and potentially interface with HubSpot fields for those conditionals.
Also wanted to add that Insycle (and just to be clear, I work for Insycle) can help reduce duplicates that flow in from forms (or through any channel). Insycle allows you to use any field as a potential matching field for duplicates. You control the final merged master record, setting rules for retaining data on a field-by-field basis.
You can also inject Insycle into HubSpot Workflows. So in your case, the workflow would go 1. Contact fills out a form → 2. Insycle checks for duplicates and if it finds any, merges based on the rules that you set and 3. then your emails go out to them if applicable.