Survey campaign troubleshooting
| Symptom | Check | Next step |
|---|---|---|
| Later wizard steps are disabled | Project Details save and campaign ID. | Fix validation and save the project first. |
| No quota allocation available | Quota created in Audience → Respondent Targeting. | Add a target-completes quota, then allocate supply. |
| Funding or submission disabled | Success redirect test, target completes, available balance, schedule, and required fields. | Fix the blocking step before checkout. |
| Low or no delivery | Campaign approval, field dates, source selection, country/language, device rules, screeners, quota caps, supplier allocation, and balance. | Broaden only the rules your study can accept; inspect source allocation. |
| Too many screenouts | Survey entry criteria versus RapidoReach audience and custom screeners. | Align both systems; test accepted and rejected paths. |
| Completes disagree | Transaction IDs, live versus test traffic, success and overquota redirects, reporting window. | Reconcile individual outcomes before increasing spend. |
| Broken live survey | Survey platform response and device compatibility. | Pause delivery or contact support, repair the link, then retest. |
Use the dashboard's status and quota progress first. Record a campaign ID, approximate time, result type, and non-sensitive transaction reference when contacting support. Never send a raw API secret or respondent personal data in a ticket. A cloned study needs its own test, dates, quotas, pricing, and funding review.