Sampling Settings (Pulse)
What's on this page
About Sampling Settings
Once you’ve uploaded participants to your pulse, you can choose to sample them. Sampling lets you distribute surveys to a subset of your participants each pulse. One of the benefits of sampling is that you can avoid survey fatigue from your employee population, especially if you send pulses on a fairly regular basis.
Qtip: You cannot use metadata that was used to build a hierarchy to also sample your participants. For example, fields like manager ID and unique ID in a parent-child hierarchy cannot be used in sampling.
Attention: Whenever you need to make an update to the program schedule or sampling settings, you will have to temporarily stop the pulse program. When you stop the program, this will delete any future scheduled surveys that do not yet have responses collected. This is why it’s important to edit program survey templates rather than individual surveys, so edits to future surveys are preserved in the event you need to stop a program.
How Participants are Chosen for Each Survey
Qtip: Sampling automatically occurs 3 days before your project is scheduled to be distributed.
Participant sampling is based on a few different inputs.
Setting Up Sampling
- Select randomly from all participants
- Select proportionally based on metadata Qtip: Learn more about Random vs. Metadata Sampling.
Qtip: You can use the dropdown to the right of a metadata to remove it.
Qtip: Once you’ve completed your sampling settings, you can launch your pulse.
Choosing a Subset of Program Participants
You can choose which participants, of all of the participants uploaded to the program, that you want to invite to the pulse.
Often, you won’t use a subset, and will just include all participants in the program. When this happens, participants will be sampled for each survey until every participant has had their turn, and the cycle starts over.
If you do choose a subset of participants, you’ll have to set up metadata conditions that define which participants you want to include. From there, only your chosen subset will be sampled for each survey.
Example: You have separate pulses for each region to address location-specific needs. You filter your program by Region = North America. If participants move and their location is updated in the employee directory, their inclusion in the pulse will adjust accordingly, so long as the pulse has a participant automation.
Qtip: Multiple values for the same field are always joined by “either/or.” For example, in this screenshot, participants from either the EMEA or the APAC region will be included.
Qtip: You can only include up to 10 different metadata fields in your conditions.
Qtip: For more guidance on building conditions, see Any vs. All. Although this support page is for a different product, the principles are the same.
Random Sampling vs. Metadata Sampling
In this section, you’ll learn about how participants are chosen to participate in each pulse survey. The ultimate goal is to sample all of your chosen participants by the end of a given timeframe; this step determines how each participant gets sampled before the end of the pulse cycle.
Example: You have 900 participants. You are sending 1 survey every month. You have set it so that every participant should receive the survey every 3 months. That means that every month when a survey goes out, it will always be 300 participants that are chosen. What varies is whether these participants are chosen by random or data-based sampling.
Random Sampling
As implied by the name, sampled participants are chosen at random.
Example: You have 900 participants. You are sending 1 survey every month. You have set it so that every participant should receive the survey every 3 months.
That means that every month when a survey goes out, 300 participants will be chosen at random, since 900 / 3 = 300.
Sampling based on metadata
Participants are chosen from every value of the chosen metadata on the chosen timeframe.
For example, if you choose to send a pulse every week for the “Department” field, then participants are chosen from every department every week proportionally based on the percentage of participants in each department.
If you choose to send a pulse every month for the “Department” and “Country” fields, then participants are chosen from all combinations of every department and every country every month, based on the percentage of participants in each department and country combination.
Example: You have 900 participants. You are sending 1 survey every month. You have set it so that every participant should receive the survey every 3 months.
Since 900 / 3 = 300, then 300 participants will be chosen every month. These participants will be chosen proportionally from all combinations of every country and every department.
The number of countries and departments in your organization does not factor into the total number of participants receiving distributions every month.
Qtip: If all participants from the chosen metadata field (e.g., Department) are selected before the all participants are surveyed, then that department will not be represented in the remaining surveys.
Warning: If the number of unique metadata groups is greater than the number of participants in your sample, then participants will be unable to be sampled. For example, if the total number of departments represented in your program participant list is 20 and the number of participants in each sample is 10, then it is not possible to select a sample that will be representative of all 20 departments.
FAQs
What happens to my hierarchy if I delete a program participant?
What happens to my hierarchy if I delete a program participant?
What happens to my hierarchy if I delete participants in one of my surveys?
What happens to my hierarchy if I delete participants in one of my surveys?
That's great! Thank you for your feedback!
Thank you for your feedback!