Skip to content
English
Contact the Effectory Helpdesk
Go to my.effectory.com
  • There are no suggestions because the search field is empty.

Understanding and using segments in My Effectory

What are segments?

In My Effectory, segments are a way to view survey results by specific groups of employees based on shared characteristics. Segments are also known as data segmentation, crossings, or data cuts.
 
Commonly used segments include:
  • Gender
  • Age
  • Tenure
By applying segmentation, you can go beyond the overall organizational results and identify trends, patterns, and differences between groups. This deeper insight can help you make better decisions and take targeted action.
 

Why use data segmentation?

Think of your organizational structure (e.g., departments) as one type of segmentation. Adding other segmentation layers, such as gender, age, or tenure, can help uncover what drives certain groups and where there are differences in experience.
 
Key benefits of using segmentation include:
  • Deeper insights: Spot trends that are hidden in aggregated data.
  • Tailored interventions: Focus attention and resources where they will have the greatest impact.
  • Benchmarking: Compare group performance to identify strengths and areas for improvement.
  • Proactive problem solving: Identify and address issues in specific groups before they affect the wider organization.
  • Increased engagement: Employees feel valued when their unique perspectives are recognized and addressed.
Example: You may see strong engagement overall, but by segmenting results by tenure, you might find that long-serving employees are less engaged than newer hires. This can, in turn, help in more targeted initiatives or policies to improve engagement.
 

Use cases

Segmentation is particularly useful for:
  • Hypothesis testing: Validate assumptions about differences between groups.
  • Spotting patterns: Identify whether certain characteristics (e.g., length of service) influence results.
  • Targeted action planning: Design interventions that address specific needs rather than applying one-size-fits-all solutions.

How segmentation works in My Effectory

Automated segments

This automated feature is currently available for customers without integrations and not part of InternetSpiegel.

Effectory automatically provides three standard data segments based on available data generated from specific columns in your employee data set. These segments, that are set up for the entire account, will be automatically assigned to all levels within your inviting structure for each survey.
 
 

If you do not want to make use of Segments within My Effectory, you can disable the feature by clicking on the three dots on the top right and disabling Segments. It can always be re-enabled at a later date.

  • Gender → The data is based on column Gender. Default categories: Male, Female, Non-Binary.
  • Age → The data is based on column BirthDate. Default ranges are:
    • 24 years and younger
    • 25 to 35 years
    • 35 to 45 years
    • 45 to 55 years
    • 55 to 65 years
    • 65 years and older
    • Tenure → The data is based on columns DateInService. Default ranges are:
      • Less than a year
      • 1 to 3 years
      • 3 to 6 years
      • 6 to 11 years
      • 11 to 21 years
      • 21 years and longer

    Note: The upper boundary of each range is exclusive. For example, someone aged 35 belongs to the “35 to 45 years” category, not “25 to 35 years.”

    Note: You can edit the date ranges for Age and Tenure to match your organization’s needs.

    If no column is mapped to the relevant Effectory field, the segment will be empty and unavailable for upcoming surveys.
     

    Visibility rules

    Net 5 response rule
    If any category within a segment has fewer than 5 respondents, the entire segment is hidden.
    • Example: 10 male, 10 female, 2 non-binary responses → Gender segment hidden because one category is below 5.

    Note: Avoid having categories with fewer than 5 employees to prevent an entire segment from being hidden (if there is not enough response).

    No response rule
    If a category has 0 responses, only that category is hidden — other categories remain visible.
    • Example: 10 male, 10 female, 0 non-binary → Male and Female shown, Non-binary hidden.

    Non-automated segments

    It is possible to provide additional data in your employee dataset for other segments of your results. These are will need to be discussed with your Customer Success Manager as they will need to be added manually. Please note that these do not follow the net 5 response rule nor are they automatically assigned to all levels. Data segmentation is only applied to the top level of your survey's inviting structure. For confidentiality and data segmentation, please refer to this article: Confidentiality and data segmentation.
     

    Business rules for using segmentation

    1. Map the correct columns (Gender, Birthdate, DateInService) before survey setup.
    2. Check category sizes to avoid having groups with fewer than 5 respondents.
    3. Merge small categories to meet the 5-response threshold.
    4. Review categories annually to reflect organizational changes.
    5. Use consistent naming across HR systems and Effectory to prevent mapping errors.

    Tips for effective segmentation

    • Keep categories meaningful - avoid excessive splitting that leads to hidden results.
    • Communicate category definitions to employees for accurate self-identification.
    • Be strategic - focus on segmentations that lead to actionable insights.
    • Monitor regularly - if a segment frequently fails the 5-response rule, consider adjusting it.
     
    By applying segmentation thoughtfully in My Effectory, you can uncover meaningful differences, tailor your actions to specific groups, and ultimately strengthen engagement and performance across your organization.
     

    Where can I find the results for segments?

    The results for segments can be found on your Scores page. You can click on Comparisons: Groups and benchmarks and click on the respective segment.