Hi,
sorry, I do not understand your concern.
As you are a panel company you usually deal with several research platforms, like SoSci Survey, firm, NeBu, LimeSurvey, whatever.
So you only append some parameters - like "projectID" and "memberID" - to the generic link
Code:
https://www.myserver.de/limesurvey/index.php/912938?pid=123456AXY&mid=6b5db5d3&m
Now there is a "landing" page on your sever that collects the results of your members.
And of course you have to distinguish between the outcomes.
Therefore you provide different URLs that contain this outcome, like
Code:
https://gateway.haifish.com/routings/[projectid]/[memberid]/finish/completed
https://gateway.haifish.com/routings/[projectid]/[memberid]/finish/screenout
https://gateway.haifish.com/routings/[projectid]/[memberid]/finish/quota_full
So the creator of the survey has to
- capture the two parameters
- create the end-url for completes in "text elements", like
Code:
https://gateway.haifish.com/routings/{pid}/{mid}/finish/completed
- create the end-url for "quotafull", "screenout", "bad quality", or whatever in "quota management", like
Code:
https://gateway.haifish.com/routings/{pid}/{mid}/finish/screenout
Well, this structure is taken from a real panel provider. Each one has its own way.
But this is not your obligation.
You only provide the name of the parameter(s) you add to the generic link and the structure of your end-links.
And the survey creator has to make sure to generate a correct link.
Joffm
