In the example, the inserted content for the token "name" contains "&", which isn't processed properly by the URL builder. It should be processed as "%26" to be inserted in the form as "&" and avoid cutting of the URL.
We have > 1000 companies with "&" in their name in our DB - so it's a pretty big issue for us
Anyone else encountered this problem? This seems like a technical bug that can be solved quite easily...?
Hello @Alexrott, thank you for proving this information above!
There is a Hubl filter that can be added to your token document here|urlencodewhich would force that "&" to be encoded when the token is inserted. We would recommend using a module or template that is enabled for theprogrammable email beta. We just tested it out in my own account using a specific template that was enabled for programmable email, added the token first name to a URL with the urlencode filter appended to the token, then tested it in an email with a contact that has an "&" in the first name and the link does encode the "&" to %26.