Hi everyone, I have a survey with an trigger sending respondents an email upon completion with further instructions and links to three generic surveys. These three subsequent links have two embedded data fields and a pipe text field appended to them. Here's how one of the target links is set up in the trigger: http://binghamton.qualtrics.com/jfe/form/SV_abcNS0YIjHll5vn?FID=${e://Field/FID}&GID=${e://Field/GID}&GRP=${q://QID3/ChoiceTextEntryValue?Format=Urlencode} The problem I'm facing is, for some reason, when these links actually get emailed out a whole bunch of extra "proxy" stuff has been added and it breaks the link functionality (but only if the value from the appended piped text field contains spaces). Here's what a emailed link looks like after a test run: https://proxy.qualtrics.com/proxy/?url=http%3A%2F%2Fbinghamton.qualtrics.com%2Fjfe%2Fform%2FSV_abcNS0YIjHll5vn%3FFID%3DR_3pgcqqLcQ8BEErG%26GID%3DR_2PoIVDgVY2V1xUt%26GRP%3Dtest&token=bx6rLmrpgFv8nBfiialV5dzLoexBljpUbIPHo2hGfWU%3D%20test%20test For the life of me, I can't figure out what's going on. I'm not using any proxy settings in my browser. I thought my Zotero connector might be the problem as it's set to direct traffic through a proxy, but that's been removed. I've cleared browsing cache and cookies. I've tried tunneling in to my university and configuring the survey from there... no change. The kicker is, this survey was a direct import from another Qualtrics account, associated with another institution, where everything works as intended (i.e. no added proxy characters, pipe text can handle spaces). All I did was modify the route survey url to reflect a different target in the imported survey. Any ideas? I've been working with Qualtrics chat support for a few days but no avail so far...

Just a guess, but try:GRP=${q://QID3/ChoiceTextEntryValue?format=urlencode}instead of:GRP=${q://QID3/ChoiceTextEntryValue?Format=Urlencode}

Seems like in live link you are appending parameters with & rather than ?. Can you check replacing & with ?

Query strings and proxy setting interference?

Query strings and proxy setting interference? | Experience Community