Hi, does anyone know how HubSpot determines the property order of the properties that are displayed on a custom behavioral event entry? I have 3 properties that I need to display in a certain order, for example:
Custom Behavioral Event -
Property 1
Property 2
Property 3
but HubSpot shows me Property 3 before Property 1.
It is not alphabetical and I am sending the values in the order I want to be displayed so not sure what it is.
Hi, I already shared this with a support rep who wasn't able to help me but I found that the order is dictated by the internal name of the properties but not sure how. Also, I found the following workaround: first I create properties with different generic internal names like "prop_1", "prop_2", etc.. then I send a test request to see which one shows first. After knowing the order, I change the labels so I can decide what goes first or doesn't, and then I change the values on the request to match the labels.
Great question. I'm happy to help 😊 Do you have a specific example you can share here? I'd like to take a deeper look and reach out to my resources if needed.
Thank you for the additional information.
Best, Jaycee
HubSpot’s AI-powered customer agent resolves up to 50% of customer queries instantly, with some customers reaching up to 90% resolution rates. Learn More.
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !
Hi, I already shared this with a support rep who wasn't able to help me but I found that the order is dictated by the internal name of the properties but not sure how. Also, I found the following workaround: first I create properties with different generic internal names like "prop_1", "prop_2", etc.. then I send a test request to see which one shows first. After knowing the order, I change the labels so I can decide what goes first or doesn't, and then I change the values on the request to match the labels.
this still doesnt work for me though.. it is polluting the sort order with all the auto captured properties. Its beena few years - have you sorted out another oslution, @CIPS