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

Field Evenly Over Time (FEOT)

Buyers have use cases that require them to collect an even number of completes over a period of time.
To use this functionality, the feature must be enabled by an operator in you buyer account. Please contact your account manager.
For more information on this feature, access the Field Evenly Over Time - Guide.
FEOT takes the desired number of completes and divides them evenly over the defined number of weeks, days and hours.
Example
If we want 1000 completes evenly spaced over 5 days: FEOT will allow a max of 200 completes per day for 5 days.
To enable FEOT on a survey, you must pass in the following extra request body parameters in either the POST /surveys or PUT /surveys/:surveyId endpoints.
Create survey endpoint reference
Update survey endpoint reference
{
    ...
    "is_feot_enabled": true,
    "feot": {
        "pacing": "hours",
        "interval": 12,
        "is_custom": true
    }
}
Use one of these values to change the pacing hours, days, weeks (7 days from launch date) with is_custom: true.
In case you use is_custom: false, the pacing used will be days.

Important Considerations#

The pacing interval cannot be bigger that field_time.
The system will recalculate the number of completes required at each interval automatically taking into consideration the remaining field time and the total number of completes required. The frequency of this recalculation is the same as the pacing and interval values.
Modified at 2025-07-19 21:10:41
Previous
Quotas on Clicks
Next
Quota Based Pricing (QBP)