Encoded links break in a Personalisation token

[SJoshi71]

Hi All,

We wanted to use a personalised token for a dynamic link. The link works whenever the encrypted ID (a custom field) does not have special characters in it. But if the encrypted ID has got a special character such as + or /, the token fails to work. I am not an expert in html/css field, but what I gathered online was whenever we are using a token, it encodes a value and if there is a special character, the encoding will change the URL. 
For ex + will return "%2B". Which breaks the URL.

Has anyone faced a similar issue? If they did, were you able to find a workaround?

Any help would be much appreciated.

Regards,

Sai 

[SJoshi71]

Hey @TomM2 ,

I did try to use a redirect for this but unfortunately, the redirect rule doesn't help much. I guess the best bet would be to have a HubSpot allowing to create URL field type.

[TomM2]

Hey @SJoshi71 this would be the case as HubSpot does need to encode/decode the personalization tokens. 

Have you tried creating a redirect link for your encrypted links? Like using a bit.ly link that terminates at the encrypted link? I'm not sure if it will work but might be a workaround to use it! 

[SJoshi71]

Hey @TomM2 , thanks for sharing the inputs. Whilst shortening the link sounds a good option as the encrypted id takes users to different SF pages, and the number of records are high, I doubt whether this will work. But I will give it a try