It would be a good idea to have background variables set in the 2CV Template.
From top of my head it would have to be DPANELID.
When you are running a client sample survey that you need short URLS, you cannot append anything on them as the links dont work. So if you wanted &PID=XXX it is not possible.
A way around this is to have BGPANELID variable in place in your sample file as well as PANELID and copy the id into both, making sure it is the same id, so that if you are running long links, with &PID=XXX then the id captures, but if you use short URLS, then the BGPANELID is recording the data as well.
My NFL client was a good example, where they didnt like the long links. Shorter links to look better, and the respondent is less likely to be able to tamper with the links.
You can also do this for DMARKET (BGDMARKET) DSAMPLE (BGDSAMPLE) etc.... i guess you just need to think about the top 5 used variables that are commonly used to identify a respondent.
It would be a good idea to have background variables set in the 2CV Template. From top of my head it would have to be DPANELID.
When you are running a client sample survey that you need short URLS, you cannot append anything on them as the links dont work. So if you wanted &PID=XXX it is not possible.
A way around this is to have BGPANELID variable in place in your sample file as well as PANELID and copy the id into both, making sure it is the same id, so that if you are running long links, with &PID=XXX then the id captures, but if you use short URLS, then the BGPANELID is recording the data as well.
My NFL client was a good example, where they didnt like the long links. Shorter links to look better, and the respondent is less likely to be able to tamper with the links.
You can also do this for DMARKET (BGDMARKET) DSAMPLE (BGDSAMPLE) etc.... i guess you just need to think about the top 5 used variables that are commonly used to identify a respondent.
Sanj