Email Token / Display a specific value of a contact 'multiple options' property

[AudreyJouan]

Hello,

In our forms, we are collecting through a checkbox field multiple values.

I would like to know if it is possible in an email to display the values of a token separately, instead as of them being displayed as a string of value.

For example, in a form we collect one or several Market(s) of Interest 'Market A, Market B, Market C, Market D, Market E'.

When we use this 'Market of Interest' token in an email, it is displayed as string of value, as follow for example:

Market A, Market C, Market E

Would it be possible in an email, to select the token 'Market of Interest' and choose to display the first, or second (etc) value available ?

As such, if we were to choose to display the 2nd value available in a field, we could have a display as follow (based on previous example):

Market C

Which would prove very useful for personnalization.

Thank you in advance for your help,

Audrey

[CAnderson716 · Accepted solution]

Hi @AudreyJouan, I would probably use multiple active lists for this one segmented by the Market Values selected. Then in your emails, personalize it to that particular market of interest. It is a bit of a workaround, but would accomplish the end goal of personalizing based on the market of interest. This would help at least until this feature is released.

[AudreyJouan]

Hi @CAnderson716 ! That is definetly is nice workaround. Thank you for your help!

[karstenkoehler]

Hi @AudreyJouan,

As far as I know, this is not possible out of the box. You could suggest it in the HubSpot Ideas section of the community. Requests made there are evaluated by the product team based on their popularity.

For an intermediate solution, this can probably be achieved with HubSpot Operations Hub Professional and custom code actions. With custom code, you could copy the desired value into a separate contact property for further use.

Best regards!

[AudreyJouan]

Hi @karstenkoehler 

Thank you for your help. I will workaround with the solution provided by @CAnderson716 in the meantime as less coding is involved and it would seem to fit most of our use cases.

Kind regards