Email Triggers don't show piped URL properly | XM Community
Skip to main content
Has anyone tried to pipe in a URL from a survey (we ask the user to provide a URL) into an email trigger? When we see a response come in the URL has all of this other junk thrown in with it so this:



www.google.com



becomes this in the email:



https://clicktime.symantec.com/3G7DhGeNfNiJxkGCQrUMjcc7Vc?u=https%3A%2F%2Fwww.google.com.



Is there any way to avoid this or fix it so that it'll show the actual URL? It gets quite jumbled when there are multiple URLs being entered. I tried creating an email trigger via the Action tab, but I run into the same issues. A workaround is just to ask the user to not include "http://www" but users might not always follow the request.



Thanks!
Hi there! Can you show us how the user is inputting it and then how it's popping out in your Data and Analysis tab?
Hi Jen,



As an example we'd have the following question:



_List URL for the section(s) or tool(s) that need to be included in this report._



We'd then have an open text box that they can input the information. So in this case let's say they input:



_www.canadapost.ca/personal_



The email sent out would list that piped text as:



_https://clicktime.symantec.com/36FUHeSaxme96M725dV6bPh7Vc?u=www.canadapost.ca%2Fpersonal_



I'd love it just to show "www.canadapost.ca/personal" with no hyperlink or anything in hopes of getting rid of the extra URL chunks.



Hope that makes sense!





Thanks,



Kristy
Some screenshots for reference...



Survey question:



!





Answer piped into the email:



!
That's so bizarre! Are you seeing the Symantec addition in the recipient's email or on the actual trigger from Qualtrics?



I'm guessing it's the former and that your email protection system is adding that in on the email side after it leaves Qualtrics. To be sure though, you could check your Data and Analysis tab and see what is entered there for that question. If it appears as just the 'www.canadapost.ca/personal' in Data and Analysis, it's Symantec that is adding it. In that case, I would suggest some custom code to remove the "https://www" or any variation there.
Thanks Jen - I'm playing with some code now, and managed to take out the 'symantec' add-on...will try to look for something that would allow me just to strip the http://www out altogether, but it's a start!!

Leave a Reply


Terms & Conditions