Skip to main content
Version: v2

Survey campaigns

A survey campaign recruits respondents for your survey. Your project supplies the test and live survey links; RapidoReach handles respondent eligibility, quotas, redirects, and the funded campaign review flow.

What the product provides​

The dashboard has a six-step wizard: Project Details, Audience Sourcing, Audience, Quota Allocation, Test, and Pricing & Schedule (also shown as Checkout & Schedule). You can create a draft, connect source types, use profiling questions and custom screeners, set respondent quotas, test result exits, allocate funds from the shared balance, and follow review and delivery. The advertiser API exposes draft creation, campaign reads and updates under route policy, quotas, custom questions, qualifications, clone, and supporting market or profile reads. API creation alone does not make a funded or active survey.

Your survey platform remains responsible for hosting the questionnaire, storing the transaction ID supplied on entry, applying its own qualification and quota decisions, and returning each respondent to the correct RapidoReach outcome URL. Plan who will own redirect configuration and reconciliation before you buy traffic.

Before you start​

Have the survey's target market and language, expected length of interview (LOI), expected conversion rate, cost per interview (CPI), target completes, field dates, and test/live links ready. Your survey must redirect respondents back for success, disqualification, overquota, and screenout outcomes.

The dashboard workflow is:

  1. Project Details: save the project to unlock later steps.
  2. Audience Sourcing, Audience, and Quota Allocation: choose supply and define who can qualify.
  3. Survey links and result testing: verify accepted and rejected exits.
  4. Pricing & Schedule: review cost, fund from the shared advertiser balance, and submit for review.

A draft is not live. Funding and review are required before delivery. Active campaigns cannot be edited in the same way as drafts; check status controls before changing a running project.

For a worked plan and final verification, use the survey launch checklist. API integrations should treat the survey API reference as the request contract and use the dashboard flow to verify the same business rules in development.

For delivery or result mismatches, use the survey troubleshooting guide. Developers using the signed external campaign API should start at the survey API reference.