I have several cases where {TOKEN} is not being passed to the endurl for a survey. Here's the endurl:

Email template, basic admin notification:

And the email generated to me:


This means the endurl for the user was:
My rpt.php file requires the token parameter, as you might expect. When it's empty, rpt.php redirects the participant to an error form to notify me of the issue.

Now I know why some have been complaining.

The extremely odd thing about this issue is I use the same pattern on several surveys (about 20). The {TOKEN} has not failed before.

Looking at the individual response from {VIEWRESPONSEURL}, [token] appears twice:

• [token] Token ID TW1912081575783506HhqYjq
• [submitdate] Submission date 12-07-2019 16:48:33
• Completed Y
• [id] Response ID 256
• [startlanguage] Start language en
• [seed] Seed 902380868
• [token] Token TW1912081575783506HhqYjq

I took the survey myself to see what the confirmation email rendered. Here's some good news. The confirmation email includes the correct link. Here's the line in the email template: And here's how the email looks:
However, as before, the endurl was not correctly rendered. The {TOKEN} is not inserted, even though it's obviously there in the confirmation email.

Any thoughts for my next round of debugging?

Many thanks.

Here's some additional information. I added code to the rpt.php file to send me an email to help track the issue.

The endurl is processed from the survey and points to my website's rpt.php script. I'm checking for and trapping the querystring params at the top of my rpt.php script. Here's what I get (for example):
At the same time, this is what I get from the Basic Admin notice email:
Notice that token= nothing. No token is shown.

Based on the email from my rpt.php script, it appears that the token is being processed. The confusing part is I don't see the token in my Admin notice. In other words, it appears that {TOKEN} is working, but for some reason, it doesn't show up in the Basic Admin notification and probably doesn't show up on the confirmation email.

Very odd.

Any thoughts?

Did you try {TOKEN:TOKEN} (with no spaces)?

Ah...no spaces...I missed that. That's the secret for email templates.
For what it's worth, the endurl still only has {TOKEN} and appears to be working.
Does it make sense to change all my endurl strings to {TOKEN:TOKEN}??

As far as I know, {TOKEN:TOKEN} works everywhere but please test and let us know.

Thanks, Tony. I will certainly test and report back.

Using {TOKEN:TOKEN} as a parameter for the endurl definitely works. All of my other surveys just use {TOKEN} and I have not seen an issue.