Check how test submissions affect usage
Do not assume a submission through a respondent link is exempt from plan usage because its answers are synthetic.
Select a screenshot to enlarge it.
Steps
- Check the workspace’s current Plan & usage before testing.
- Use builder Preview to inspect wording and layout first. When persistence needs testing, submit only the synthetic records needed for that check.
Set the intended date and device filters. These empty-demo metrics are not a performance benchmark. - Compare the usage and Results afterward. Confirm the current counting and reset rules with support if they affect your campaign capacity.
Review the offered export and its scope. Verify the resulting file or destination separately.
Check before you rely on it
Deleting a response is not proof that quota is restored. Keep testing on a development workspace where possible.
If you need help
Ask support about counting behavior instead of relying on a historical free-test allowance.
Contact support with the relevant screen, time, and a redacted description. Keep credentials and private respondent information out of screenshots.