PureSpectrum
PureSpectrum websiteHelp center
PureSpectrum websiteHelp center
  1. Guides
  • Intro
  • API Overview
  • Definitions
  • Survey Lifecycle
  • Create Your First Survey
  • Redirect URLs
  • Changelog
  • HTTP Status Codes
  • General Reference Codes
    • Survey Status Codes
    • Respondent Status Codes
    • Survey Category Codes
    • Age Unit Codes
    • Currency Codes
    • Survey Localization Codes
  • Guides
    • Getting Started
    • Create Survey Examples
    • Multi-Country Surveys
    • Children Age & Gender
    • Append Respondent Demographics to the Survey Entry Link
    • Test Survey Flow
    • Supplier Blends & Groups
    • Respondent Exclusion / Recontact
    • Survey Exclusion Group
    • Quotas on Clicks
    • Field Evenly Over Time (FEOT)
    • Quota Based Pricing (QBP)
    • Quota Level Complete (QLC)
    • Quota Throttling
    • Templates
    • Bypassing Automatic Variable Mapping
    • Research Defender's Predupe
    • Subscriber Emails
    • Real-Time Notifications (SNS)
  • API Reference
  • Schemas
    • Feasibility
      • Feasibility request schema
      • Feasibility response schema
    • Surveys
      • Create survey full request schema
      • Create survey minimum request schema
      • Create survey response schema
      • Update survey status request schema
      • Update survey status response schema
      • Get survey status response
    • Qualifications
      • Qualification Schema
      • Create qualification request schema
    • Quotas
      • Quota Schema
      • Create quota request schema
      • Create quota response schema
    • Attributes
      • Get attributes response
    • Supplier management
      • Supplier
      • List of all suppliers response
      • List of all suppliers per survey response
      • Update the list of suppliers for a Survey request
      • Update the list of suppliers for a Survey response
    • Other
      • Generic error response
  1. Guides

Quotas on Clicks

In order to count quotas on clicks instead of completes, also known as Click Balancing, you can use the click_balancing parameter during survey creation via Create survey endpoint.
If click_balancing is set to 1, the required_count for the quotas will reflect clicks required instead of completes required.
In the API request, completes_required still refers to the total number of completes you are looking for.
Once a survey is launched, you may not change the value of click_balancing.
Example:
{
  "survey_title": "Test count quotas on clicks",
  "survey_category_code": 231,
  "survey_localization": "en_US",
  "completes_required": 300,
  "offer_price": 3.25,
  "expected_ir": 50,
  "expected_loi": 10,
  "live_url": "https://my.survey.com?survey_id=1234",
  "test_url": "https://my.survey.com?survey_id=1234&test=1",
  "field_time": 10,
  
  "click_balancing":1,
  
  "qualification":[
    {
      "qualification_code": 211,
      "condition_codes": ["111", "112"]
    }
  ],
  "quotas":[
    {
      "buyer_quota_id": "qb12",
      "required_count": 300,
      "criteria": [{"qualification_code": 211, "condition_codes": ["111"]}]
    },
    {
      "buyer_quota_id": "qb13",
      "required_count": 300,
      "criteria": [{"qualification_code": 211, "condition_codes": ["112"]}]
    }
  ]
}
The request above will create a draft survey, looking for 300 completes, at 50% IR, or an estimated total 600 valid clicks.
There is a quota for Males, with 300 clicks, and a quota for Females with 300 clicks.
Modified at 2025-07-19 21:09:59
Previous
Survey Exclusion Group
Next
Field Evenly Over Time (FEOT)