Passing external user ID as variable in URL, into Axure and back out for varification

[UXJackal]

Hi there,
I want to test a simple dummy with users, to see if they know how to navigate my site and if they finde what they are looking for. For the test, I need to identify users, based on an ID. The ID is handed over by a third party like this: https://surveylink.com/survey/1188927/6r93si/!pi**[state]** state is the ID.

After completing the prototype I have to send the user back to the third party agency including his ID so he can be identified and paid for participating in the test. The like should look like this https://thirdpartyagency.com/survey/selfserve/1819/g0d9/190925/?state=XXXX&var=1. XXXX is the ID I have to pass over.

So my question is. How can I fetch that ID stick it to the user during the test in the prototype and then pass it on to the third party agency for verification?

I was thinking of using global variables but I am stuck with my knowledge and need help on how to do it.

[mbc66]

This thread might help you…

Variables through URL

I need to pass some variables through a URL. It works up to a point. I’ve got 4 variables. It passes 1 but then if I add more, it stops passing them all. I’ve tried various combinations but there doesn’t seem to be a pattern. Sometimes it’ll pass 3, sometimes only 2. Any ideas gratefully received! Cheers Andy

Or perhaps this more recent thread…

Read URL parameter(s) on page load

I’ve tried googling and searching on this forum site how to read url param on page load and I can’t seem to find any clear sample or instructions how to do this. Can someone help me please! Thanks in advanced.

Although, I’ve never been able to get anything like that to work. Also, there are security issues which result in browser differences, settings, plugins, firewall and AV programs which can block attempts to access the current or previous page URL.

It might be better to just ask the participants to manually enter an ID in your prototype, like on a landing page. When your tasks are finished, you could have a “jumpoff” page in your prototype which generates and shows them a code they can then enter or provide to the third party site for verification of completion and payment. Or, if you have a limited set of users and can get the third party to assign specific IDs (or share that set of IDs with you) you could create unique landing pages, one per user, so the URLs to your prototype might look something like, mysite.com/test5/1001 and mysite.com/test5/1002 etc.