Frequency and quarantine
Frequency and quarantine protect visitor experience while you collect in-product feedback. Set them before a wide production launch.
Frequency options
Section titled “Frequency options”| Option | Behavior |
|---|---|
| Once ever | Show this survey a single time to a visitor |
| Once per session | Allow one show per browser session |
| Custom interval | Allow another show after a period you define |
Frequency applies per survey. Quarantine coordinates across surveys.
Quarantine
Section titled “Quarantine”Quarantine adds a cooldown between surveys. After a visitor sees one in-product survey, other surveys wait until the quarantine window passes. Use it when multiple teams publish surveys on the same website.
Configure
Section titled “Configure”- Open the in-product survey.
- Open frequency settings.
- Choose once ever, once per session, or custom interval.
- Set quarantine according to your organization’s research guidelines.
- Preview with a fresh browser profile when you need to see the survey again during QA.
Recommended defaults
Section titled “Recommended defaults”| Program type | Frequency | Quarantine idea |
|---|---|---|
| Rare milestone feedback | Once ever | Multi-day cooldown |
| Session micro-pulse | Once per session | Shorter cooldown |
| Recurring CSAT | Custom interval (for example weekly) | Align with interval |
Exact interval controls depend on what the builder exposes for custom intervals. Choose the least aggressive setting that still answers your research question.
QA tips
Section titled “QA tips”- Use a private window to reset cookie-based frequency during testing.
- Document for teammates that production frequency will hide surveys they already saw.
- Confirm impressions still increment when a survey is eligible. See Impressions and results.
Example
Section titled “Example”Three Live surveys on production:
- Onboarding modal: once ever.
- Feature toast: once per session.
- Quarterly CSAT: custom interval.
Quarantine ensures a visitor who just completed onboarding does not immediately get CSAT on the next page.
Limitations
Section titled “Limitations”- Frequency tracking depends on browser storage. Cleared data can allow another show.
- Quarantine cannot fix poorly timed triggers. Still avoid login and payment pages in targeting.
- Admins should publish a simple internal policy so product teams do not stack Live surveys.
Related
Section titled “Related”Common questions
What does once ever mean?
The visitor should see that survey only one time across visits, based on FromUsers frequency tracking in the browser context.
What is quarantine?
Quarantine is a cooldown between different in-product surveys so one visitor is not shown another survey too soon.
Can I survey power users more often?
Use a custom interval when you need repeats, and tighten audience rules so only the right users are eligible.