Survey Throttling


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.

Survey throttling options

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)

Throttle per user

After using Refiner for a while, you might run into a situation where you are running multiple surveys with overlapping target audiences.

In this scenarios, you might want to make sure that a single user doesn’t get solicited too often. For example, limit the number of surveys one user should see within one month.

Throttle per survey

Similar to throttling surveys globally, you can also define limits for each survey individually.

This option is useful when you are running multiple survey campaigns (e.g. one NPS survey campaign for each country), and you want to make sure that you get the same number of responses for each survey.

Enable survey throttling

Navigate to “Settings > Survey Throttling” in your Refiner dashboard. Then, activate the throttling option that fits your use-case. All options can be activated individually or in parallel.

The following parameters are available for all 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.

Please note that the global and per survey throttling options should be considered as approximate methods. On high traffic websites and apps, it can happen that you’ll see slightly more survey views and responses than indicated in your settings. We recommend to start throttling with lower numbers and work your way up.

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