Community tab’s filter controls

Dashboard filter controls can be used to refine or subset the data shown in the dashboard. For example, to select a certain date range or select a particular feature.

Filter controls are located at the top of the dashboard. Filter controls have to be read with context based on the type of tab.

Sections

• Overview: This section highlights the communities created, outcomes and the overall adoption across all the employees
• User Activity: This section highlights the average weekly and monthly active users, their respective retention percent and how that trends with time
• Outreach Efficiency: This section highlights the profiles outreached through community and their response rate
• Community Pipeline: This section highlights the recruitment funnel.

Metric Definitions

Overview

Communities created

• Description: This refers to the total number of communities created in the selected time frame
• Dataset(s): community_applications_and_stages

Advanced to 'Added'

• Description: Total Unique prospects, who were advanced to the 'Added' stage in the Community UI (if the same prospect is added to two different communities, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id}, stage='Added')

• Dataset(s): communityapplicationsand_stages

Advanced to 'Contacted'

• Description: Total Unique prospects, who were advanced to the 'Contacted' stage in the Community UI (if the same prospect is contacted via two different communities, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id}, stage='1st Contact')

• Dataset(s): communityapplicationsand_stages

Advanced to 'Responded'

• Description: Total Unique prospects, who were advanced to the 'Responded' stage in the Community UI (if the same prospect is advanced to 'responded' stage in two different communities, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id},stage='Responded')

• Dataset(s): community_applications_and_stages

Advanced to 'Recruiter Screen'

• Description: Total Unique prospects, who were advanced to Recruiter Screen stage in the Community UI (if the same prospect is advanced to recruiter screen in two different communities, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id},stage='Recruiter Screen')

• Dataset(s): community_applications_and_stages

Advanced to 'HM Screen'

• Description: Total Unique prospects, who were advanced to Hiring Manager Screen stage in the Community UI (if the same prospect is advanced to HM screen in two different communities, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id},stage='HM Screen')

• Dataset(s): community_applications_and_stages

Offered

• Description: The unique prospects who were sourced via community and advanced to the Offer Stage for any position (this position does not have to be associated with the community) within 90 days of being added to the Community (if the same prospect is advanced to offer stage for 2 different positions, we will count it only once)
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id},stage='offered')

• Dataset(s): community_applications_and_stages

Hired

• Description: The unique prospects who were sourced via community and advanced to the Hired Stage for any position (this position does not have to be associated with the community) within 90 days of being added to the Community
• Formula in Quicksight calculation:
  • distinct_countIf({profile_id},stage='hired')

• Dataset(s): community_applications_and_stages

% Active Employees

• Description: The share of current employees (excluding alumni) using the EF community features.
• Dataset(s): ta_feature_community_breadth_of_usage

% Active Recruiters

• Description: The share of current recruiters (excluding alumni) using the EF community features.
• Dataset(s): ta_feature_community_breadth_of_usage

% Active Sourcers

• Description: The share of current employees (excluding alumni) using the EF community features.
• Dataset(s): ta_feature_community_breadth_of_usage

User Activity

Weekly Adoption

• Avg Weekly Active users: It is the average number of Weekly active users performing any of the actions in the Community UI in the selected time frame
  • YoY metric: denotes the % change in Average Weekly Active Users compared to the previous year

• Avg Weekly Retention (Repeat Users) %: It denotes the percentage of users in a given week who were active in the previous week as well

  • YoY metric: denotes the change in Average Weekly Repeat Users % compared to the previous year

• Dataset(s): tafeaturecommunityadoptionby_week

Monthly Adoption

• Avg monthly Active users: It is the average number of monthly active users users performing any of the actions in the Community UI in the selected time frame
  • YoY metric: denotes how the Avg monthly Active Users has changed compared to the previous year.

• Avg monthly Retention (Repeat Users) %: It denotes the percentage of users in a given month who were active in the previous month as well

  • YoY metric: denotes how the Avg monthly Repeat users % has changed compared to the previous year.

• Dataset(s): tafeatureengagementadoptionby_month

Total Active Users

• Description: refers to unique active users who perform any activity on the Community UI in the selected time frame.
• Dataset(s): ta_feature_community_activity_log

Trend in Active Users and their associated activity

• Description: This view shows the activity count of all active users and how that trends with time.
• Dataset(s): ta_feature_community_activity_log

Communities with activities

• Description: The unique number of communities with any activity performed on the Community UI.
• Dataset(s): ta_feature_community_activity_log

Outreach Efficiency

Candidates Outreached

• Description: The number of unique candidates outreached via Email, SMS or Whatsapp from the Community UI (if a candidate is outreached twice for 2 different communities, they will be accounted twice in order to give credit for the outreach activity)
• Formula in Quicksight calculation:
  • distinct_countIf(concat(toString({profile_id}),toString(title)), event='contact' OR event='sms_send_success' OR event='whatsapp_send')

• Dataset(s): tafeaturecommunityactivitylog

Profiles Outreached by Timestamp and Medium Of Contact

• Description: Trend in the number of unique candidates outreached via Email, SMS or Whatsapp from the Community UI across different mediums of contact (if a candidate is outreached twice for 2 different communities, they will be accounted twice in order to give credit for the outreach activity).
• Dataset(s): ta_feature_community_activity_log

Profiles Outreached by User_id and Timestamp

• Description: Trend in the number of unique candidates outreached via Email, SMS or Whatsapp from the Community UI breakdown by Active user name (if a candidate is outreached twice for 2 different communities, they will be accounted twice in order to give credit for the outreach activity)
• Dataset(s): ta_feature_community_activity_log

Candidates Responded

• Description: The number of unique candidates responded via Email, SMS or Whatsapp to the messages sent from the Community UI (if a candidate responds for 2 different communities, they will be accounted twice in order to give credit for the outreach activity)
• Formula in Quicksight calculation:
  • distinct_countIf(concat(toString({profile_id}),toString(title)), event='reply' OR event='sms_reply' OR event='whatsapp_reply')

• Dataset(s): tafeaturecommunityactivitylog

Candidates Responded by Timestamp and Medium Of Contact

• Description: Trend in the number of unique candidates responded via Email, SMS or Whatsapp to the messages sent from the Community UI (if a candidate responds for 2 different communities, they will be accounted twice in order to give credit for the outreach activity).
• Dataset(s): ta_feature_community_activity_log

Candidates Responded by User_id and Timestamp

• Description: Trend in the number of unique candidates responded via Email, SMS or Whatsapp to the messages sent from the Community UI breakdown by Active User Name (if a candidate responds for 2 different communities, they will be accounted twice in order to give credit for the outreach activity).
• Dataset(s): ta_feature_community_activity_log

Response Rate

• Description: The ratio of the candidates responded to the candidates outreached (Note: This just gives you a rough estimate of the response rate since it's not cohort based. This calculates all the candidates outreached and candidates responded in a certain time range and takes the ratio of those metrics. The candidates who responded does not necessarily have to be a subset of the candidates outreached in a selected period of time. So this ratio can even be > 100% when candidates outreach in a week is less than candidates who responded in that week).
• Formula in Quicksight calculation:
  • {Candidates responded}/{Candidates outreached}

• Dataset(s): tafeaturecommunityactivitylog

Response Rate by Timestamp and Medium Of Contact

• Description: Trend in the ratio of the candidates responded to the candidates outreached (Note: This just gives you a rough estimate of the response rate since it's not cohort based. This calculates all the candidates outreached and candidates responded in a certain time range and takes the ratio of those metrics. The candidates who responded does not necessarily have to be a subset of the candidates outreached in a selected period of time. So this ratio can even be > 100% when candidates outreached in a week is less than candidates who responded in that week).
• Dataset(s): ta_feature_community_activity_log

Response Rate by User_id and Timestamp

• Description: Trend in the ratio of the candidates responded to the candidates outreached breakdown by User name who would have received the responses.
• Dataset(s): ta_feature_community_activity_log

Activity Summary by Community - User

• Description: This view gives you the visibility into the breakdown of outreach activity, response rate % across all medium of contacts by Community - User level.
• Dataset(s): ta_feature_community_activity_log

All activities of the Community User and the frequency of usage (Raw Data)

• Description: This view gives you visibility into all the activities performed by all active community users in the selected time range. In order to understand the event names, please refer to the ‘Events Description’ under glossary section
• Dataset(s): ta_feature_community_activity_log

Communities Pipeline

Communities created and the Recruitment funnel

• Description: The metrics in here are the same as defined in the Overview section. These metrics are broken down by Community Name

Candidates advanced to different interview stages by Community Name

• Description: All stages configured by the customer will be displayed on the x-axis and the Communities on the y-axis