Page Comparison

...

• While you may call the keyname as you wish (e.g. “gender”, “gen”, “sex”), the value returned in the keyname will always use the PureSpectrum condition code. Please refer to the attributes API Endpoint to determine your qualification and condition codes: Looking Up Attributes

• We can always append Gender & Age of a respondent, and can also append any audience criteria that is defined in the survey.

  • If the survey is screening on ethnicity, then race can be added to the live link using “&race=[%%214%%]

  • If a qualification is added that is not present in the survey, the entry link for the respondent may contain “null” in the query string parameter, which may break your survey. (e.g. “https://mysurvey.com/survey?transaction_id=abc123&race=null”)

  • In the event that a question is a multi-select (aka multi-punch), where more than one answer is permitted, the answers will be appended as a comma-separated string (e.g. &pets=111,112)

• Income and age questions return an integer. If you need to place these respondents into a bucket, like ages 55-64, you will need to account for this in your survey when processing the respondent’s profile.

Common Demographics and their Qualification ID’s

...