By default, PureSpectrum throttles survey traffic based on survey incidence, and number of completes remaining. If your survey is set up to use quotas, we will take those quotas into consideration, so that the number of people in progress will not exceed the number of completes remaining divided by the incidence rate.
If there are 10 completes remaining, and the survey is converting at 10% IR, we will allow up to 100 respondents into the quota/survey at one time.
In the event that your survey requires more aggressive quota throttling, you may enable this setting via Buy API. By setting quota_throttling:true, we will override our default throttling ratio above so that for every complete remaining, we will only send one respondent.
Aggressive Quota Throttling Example
If there are 10 completes remaining, and the survey is converting at 10% IR, we will allow up to 10 respondents into the quota/survey at one time.
To enable the more aggressive quota throttling, you may pass in “quota_throttling”:true in either the POST /surveys or PUT /surveys/:surveyId endpoints.
By default, “quota_throttling” is set to false.
The value of this parameter may be modified at any point when the project is in Draft, Live, or Paused statuses.
We would only recommend setting “quota_throttling”:true in extreme circumstances. For most users, our default quota_throttling will provide a superior experience for the Respondent, the Supplier, and you as the Buyer.
It may make sense to use the more aggressive quota throttling if your survey platform has aggressive throttling rules, or if your survey platform does not set caps on quotas.
We would recommend using the more aggressive quota throttling if your survey is programmed in Decipher. If you are already using the Decipher integration offered by PureSpectrum, you do not need to worry about toggling this setting, as it will happen automatically.
POST (or PUT) $apihost/$basepath/surveys
($apihost is the environment against which you are testing, and $basepath is the base path with the api version. All Buy API calls will require access-token parameter in the header)