Overview
In the interest of reducing respondent fatigue and improving the respondent experience, you may bypass the respondent screener in PureSpectrum by passing in the respondent's qualification/condition codes in the query string parameters. You must use the PureSpectrum values for these qualification codes and condition codes.
For singlepunch single punch questions like gender, you should pass in a single value e.g. &211=111. For questions that are multipunchmulti punch, you may pass in multiple, comma separated values e.g. &1031=111,112.
Respondent Qualification Usage
In the example where you are sending a white(214|111) male(211|111) respondent, 34 years old(212|34) earning 50,000 household income(214|50000), with both a dog and a cat(1031|111,112), your entry link would be:
...
| Info |
|---|
...
Profiling for deviceProfiling for DevicePureSpectrum supports different devices for profiling respondents; Desktop/Laptop, Mobile, Tablet. In all cases, PureSpectrum uses internal tools to auto detect respondent's device and appends the relevant device. Therefore, there is no need to append this to the survey entry link. Device profiling can be done internally on suppliers end and only the profiles matching the device requirements of the survey can be sent in. The qualification you can expect to see returned in surveys targeting specific devices is the following: |
| Info |
|---|
Profiling for geographyProfiling for GeographyPureSpectrum supports many different geographical regions for profiling respondents; Nationally Representative, Census Region, Census Division, State, DMA, CBSA, MSA, County and Zip. In all cases, PureSpectrum uses zip codes to map all respondents to the relevant geographic region. Therefore, the only survey entry link attribute necessary for geographic qualification is zip code. ExampleSurveys with the criteria: "qualification_code": 225, (state) Would have an entry like passing a zip code in Oregon: |
More information about PureSpectrum Qualification and Condition codes can be found here:
Qualifications and Conditions Codes
Required Variables
Variable | Syntax | Required | Description | Example |
|---|---|---|---|---|
Supplier ID | supplier_id | y | The Supplier's id to PureSpectrum. The value will be included in the link generated by PureSpectrum. | |
Survey ID | survey_id | y | The survey id the respondent is to complete. The value will be included in the link generated by PureSpectrum. | |
Session ID | ps_supplier_sid | y | The unique session id for a given entry. Should always be unique. | |
Respondent ID | ps_supplier_respondent_id | y | The persistent supplier member id. This should never change for a given respondent. |
Mapping Variables
If the name for these variables differs from PureSpectrum's name, you can map them via the user interface to simplify the integration.
Considerations
Please note that we will ignore qualification codes with condition code=null, and any additional condition codes beyond the first condition code for singlepunch questions.
...