I think you did not fully crasp the concept yet.

Survey 1 and survey 2 are completely independent surveys, their SavedIds purely depend on how often their link has been called. So of course the SavedID from Survey 1 and the SavedID from Survey 2 can be completely different.

In any way, in my opinion, if you pass an ID from survey 1 to survey 2, you could actually just ask the personaldate for the price draw in the first survey and you don't need the second one. Because if you can connect the two surveys via an ID, it is the same as asking the personal data in survey 1 already, annonymity wise it is the same. And you save yourself all this discussion here about how to pass an ID from survey 1 to survey 2.

But, to do so, what do you need to do?

1. In survey 1 you add an ID to the end url which calls survey 2
2. In survey 2 you need to add a question (usually text, which will be hidden after you tested everything and it works fine).
3. You need to read the ID passed on via the end url into your text question and store it there.
4. Now the ID that you passed from survey 1 to survey 2 should be stored as a "response" in that specific text question.

for testing, you can do it with anything, you cann just add a string instead of the Savedid, if this is confusing you at the moment. then you will see how things work. Because I have the impression that you do not fully understand what we are proposing here.

As @holch already said "You do not need the SAVEDID of survey 2.
And we use the SAVEDID of survey 1, because this is a unique value.

Now:
You add "var1={SAVEDID} to the end-url which is the start url of the second survey.

Now you have to capture this value (var1) in your second survey - to be able to compare.
I think you did not read this carefully
[url] manual.limesurvey.org/URL_fields/en#Start_URL [/url]

The very first example

• Code:

  http://ls.example.org/1234?QTEXT=prefilled

   : Fill in the question with code QTEXT with 'prefilled'

In your case it is not "QTEXT=prefilled", but "var1=[value of SAVEDID]"
Meaning: You have to create a question ("short text") with question code "var1"

Here you will find the value of the SAVEDID.
Now, if a respondent uses the end link several times to call the second survey you can recognize and remove this responses.
The same if someone manipulates the link and you find values that are not existing in the first survey.

Unfortunately you ignored the initial questions about your LimeSurvey version.
Because using the function "statCount" you may check if a value was entered already and screen out this respondent. But depends on your version.

Joffm 


 

Sorry, it is LimeSurvey Community Edition Version 5.4.7

Should it be Start URL form in Text elements? Because I can not find such field on that page. Only End URL and URL description:

Meaning: You have to create a question ("short text") with question code "var1"

Is that how it should be? 
Yes, it really sends the number to Survey 2 and if I use that link again it will be still tat number. 
But I can just change this number in the filed ...

That is why you HIDE this question after you tested it!

for me the workflow could be the following:
- anonymous survey 1 with an email address question
- afterSurveyComplete an email will be send with a link to that email address
- onClick on this link a token will be generated in survey 2
- token (participant) will be invited to survey 2

requires some plugin development knowledge

bismark wrote:

for me the workflow could be the following:

 

This workflow is begging for work. LimeSurvey has no way to resolve mail server issues (e.g. delays).
There is a risk of a bottleneck if an email needs to be sent at the end of the survey.
Delivery issues/greylisting of the mail server will cause a delay between the completion of the first survey and the second survey.
People will reach out and ask why they haven't got received an email.

The topic starter would like to ensure two points:
1.There will be two databases: one for the responses and one for the participants' emails
2.Preventing an anonymous survey from being run multiple times.

The solutions proposed here in this thread are to ensure that respondents do not bypass the first survey to enter the drawing with a valid entry.
As long as respondents only have one email address, you can ensure that they only enter the draw once. This may be the case if you limit the sweepstakes to one company, but not in the "wild". Everyone can have multiple email addresses.

So participants can enter the survey more than once, and as long as they complete the first survey and have an additional email address, they can enter the draw more than once.

Other survey tools offer a question type for personal data which will be saved in a separated database table without creating two surveys.