Survey throttling: Control the speed and frequency of user surveys

Soliciting your users with too many surveys within a short time frame is definitely something you want to avoid.

Besides providing a bad user experience, surveying users too often ultimately leads to low response rates and poor data quality.

The same is true for your team.

Receiving too many survey responses at once might overwhelm your team and they might struggle to handle all received user feedback timely.

Survey throttling is a great way to prevent spamming your users while still making sure that you get all the data you need at the right speed.

Throttle surveys on a “per user” basis (prevent spamming users)

Like most of our customers, you’ll probably run into a situation where you want to launch a new user survey right after finishing your last survey campaign.

You also might want to run two or more survey campaigns in parallel with overlapping target audiences. In fact, most of our customers are running more than one survey campaign.

In both scenarios, you want to make sure that a single user doesn’t get solicited too often. For example, not survey a user more often than once per month.

Throttle surveys globally

Throttling surveys is not just useful for providing a good experience to your users. Throttling also allows you to control the speed of data collection globally.

Two popular use-case for slowing down survey responses globally:

  • You want to stop surveying your users after N responses because you estimate that it is enough data to make an informed decision
  • You want to make sure that your team is not getting overwhelmed and can act timely on each survey response (e.g. feedback received from a NPS survey)

How to throttle your surveys

Navigate to “Settings > Survey Settings” in your Refiner dashboard. Then, activate either the option to slow down surveys globally or by user. Both options can be activated at once and work great in parallel.

Screenshot showing survey throttling options of Refiner

The following parameters are available for both options:

  • Time Frame: This parameter defines how far we will look into the past when determining if a survey can be shown or if we wait a little longer
  • Max. survey responses: Determines how many survey responses you want to collect in the given time frame.
  • Max. survey views: Determines after how many survey views in the given time frame we should stop serving surveys.

The “per user” throttling has the following additional parameter

  • Min. delay between surveys: This parameters defines how much minutes need to pass between two surveys.

Was this helpful? Let us know with a quick a vote