TA Feature Usage and Outcomes
Overview
This dashboard tracks how Talent Acquisition features are being used and the outcomes they drive. Activity across each TA module — Engagement, Campaigns, Scheduling, Feedback, Community, Sourcing, and Recruiting Events — is tracked as distinct events, which roll up into the metrics below. The dashboard is organized into tabs matching these modules; this guide follows the same structure.
TA Module Reference
How each TA module is derived from underlying product events — useful context for interpreting the metrics below.
- Sourcing — feature_usage = 'Chrome Extension' (event add_to_pipeline with source extension), 'Import Resume' (event import_profile), or 'Linkedin CRM' (event export_to_crm). Reflects candidate-sourcing actions performed outside the normal application flow.
- Calibration — feature_usage = 'Position Calibration' (events calibration_80_percent_complete, calibration_confirmed, calibration_100_percent_complete). Tracks progress through position calibration (location/skills/titles/work-experience/similar-candidate criteria).
- Scheduling — any event matching %scheduling% (excluding interviewer-specific events), split into four feature_usage sub-types by priority: Interview Plan, Open Scheduling, Event Scheduling, Standard Scheduling. Each scheduling request is assigned exactly one type by priority ranking, so a request touching multiple event types still counts once.
- Engagement — feature_usage = 'Email', 'SMS', or 'WhatsApp' (from customer_views.user_messages, restricted to messages with no campaign attached). Covers one-off, non-campaign outreach to candidates.
- Campaigns — feature_usage = 'Campaigns', either from a user_messages row carrying a user_campaign_id, or from application_source rows where source_type = 'Campaign' (attributes an application back to the campaign that sourced it, even without a message row).
- Feedback — any row from customer_views.profile_feedback (identified because feedback_status is populated), with feature_usage = 'Quick Feedback', 'Interview Feedback', or the raw feedback_type value for anything else.
- Profile Tag — feature_usage = 'Profile Tag' (from customer_views.profile_tags where tag_type = 'user' — manually applied tags, not system tags).
- Community — feature_usage = 'Communities', from two places: (a) user_analytics events on positions where system_id = 'sourcing', split by channel into Email, SMS, WhatsApp, or Other; and (b) each community application's current stage (most recent stage per candidate per community position).
Overall
Active Users
Definition: Active Users measures the count of distinct users who have performed any activity across any Talent Acquisition module within a given time period, filtered by activity date. A user is considered "active" if they appear in at least one of the modules: Engagement, Scheduling, Campaigns, Sourcing, Feedback, Community, Recruiting Events, and Profile Tags.
How it is calculated: Counts the number of distinct users with activity recorded in any of the modules above.
Active Recruiters
Definition: Active Recruiters measures the count of distinct users who hold a recruiter role and have performed at least one activity within any TA module during a given time period, filtered by activity date.
How it is calculated: Counts distinct active users whose assigned role contains the word "recruiter."
Note:
- Recruiter status is identified by the role assigned to the user in your Admin Console user groups, not a separate field.
Active Hiring Managers
Definition: Active Hiring Managers measures the count of distinct users who hold a hiring manager role and have performed at least one activity within any TA module during a given time period, filtered by activity date.
How it is calculated: Counts distinct active users whose assigned role contains the phrase "hiring manager."
Note:
- Hiring manager status is identified by the role assigned to the user in your Admin Console user groups.
Active Users by User Role
Definition: Active Users by User Role measures the count of distinct users who have performed any activity across any TA module within a given time period, segmented by their assigned user role, filtered by activity date.
How it is calculated: Counts distinct active users, grouped by role.
Note:
- Role is identified by the role defined in your Admin Console user groups.
Positions Worked On
Definition: Positions Worked On measures the count of distinct positions that were touched by at least one activity across any TA module within the selected reporting period, filtered by activity date.
How it is calculated: Counts each distinct position with recorded activity. A position is counted once regardless of how many activities or users were involved.
Total Applications
Definition: Total Applications measures the count of distinct applications that either recorded activity on a TA module or were submitted as a direct result of such activity, filtered by activity date.
How it is calculated: Counts distinct applications tied to TA module activity.
Note:
- Scheduling and Feedback modules aren't linked to applications and are excluded.
- For Engagement, only applications where the activity occurred before or on the application date are counted.
- For Community, only reply events (not outbound messages) are counted. All other modules count applications directly.
Total Candidates Acted Upon
Definition: Total Candidates Acted Upon measures the count of distinct candidates who had any activity recorded against them across any TA module, filtered by activity date.
How it is calculated: Counts distinct candidates with recorded activity.
Note:
- For Community, only outbound contact events are counted — reply events are excluded. All other modules count all candidate interactions directly.
Total Hires
Definition: Total Hires measures the count of distinct applications that resulted in a hire due to any TA module activity, filtered by hire date.
How it is calculated: Counts distinct hired applications attributable to TA module activity.
Note:
- Scheduling and Feedback modules are excluded, as they aren't linked to applications.
- For Engagement, only applications where the activity occurred before or on the application date are counted.
- For Community, only reply events are counted.
- Only closed positions with a recorded hire are included.
Hire Rate %
Definition: Hire Rate % measures the percentage of applications attributed to TA module activity that resulted in a hire, filtered by activity date.
How it is calculated: Divides hired applications (on closed positions) attributed to TA activity by all applications attributed to TA activity.
Note:
- Scheduling and Feedback modules are excluded.
Applied Rate %
Definition: Applied Rate % measures the percentage of candidates acted upon through any TA module activity who went on to submit an application, filtered by activity date.
How it is calculated: Divides distinct candidates who applied (following TA activity) by all distinct candidates acted upon.
Note:
- Scheduling and Feedback modules are excluded.
- For Engagement, only activity occurring before or on the application date counts toward the numerator. For Community, only reply events with an application on file count.
Recruitment Funnel
Definition: Recruitment Funnel measures the count of distinct applications affected by any TA module activity, broken down by application stage, filtered by activity date.
How it is calculated: Counts distinct applications per hiring stage group, for applications tied to TA module activity.
Note:
- Scheduling and Feedback modules are excluded, as they aren't linked to applications.
- For Engagement, only activity occurring before or on the application date is counted. For Community, only reply events are counted.
Monthly Trend of Active Users
Definition: Monthly Trend of Active Users measures the count of distinct users who performed any activity on any TA module, broken down by month, filtered by activity date.
How it is calculated: Counts distinct active users per calendar month.
Monthly Trend of Repeat Users %
Definition: Monthly Trend of Repeat Users % measures the percentage of monthly active users who were also active in the prior month, broken down by month, filtered by activity date.
How it is calculated: For each month, divides users who were also active exactly one calendar month earlier by all active users that month.
Engagement
Covers one-off direct messages (Email, SMS, WhatsApp) sent by a recruiter to a candidate outside of a bulk campaign.
Data Sources & Event Reference
| Source | When it's triggered |
| Email message (no campaign) | A recruiter sends a one-off direct email to a candidate |
| SMS message (no campaign) | A recruiter sends a one-off direct SMS to a candidate |
| WhatsApp message (no campaign) | A recruiter sends a one-off WhatsApp message to a candidate |
How to refer in product: Contact option after selecting applicants under Positions.
[Insert screenshot: engagement-how-to-refer-1.png]
[Insert screenshot: engagement-how-to-refer-2.png]
Total Applications - Engagement
Definition: Total Applications - Engagement measures the count of distinct applications from candidates who were reached out to via WhatsApp, Email, or SMS, filtered by message sent date.
How it is calculated: Counts distinct applications where outreach occurred before or on the application date.
Total Hires - Engagement
Definition: Total Hires - Engagement measures the count of distinct applications that resulted in a hire, attributed to Engagement module activity, filtered by hire date.
How it is calculated: Counts distinct hired applications where outreach occurred before or on the application date.
Note: Also available broken down by week (Total Hires - Engagement by Week) and as a weekly trend for applications (Total Applications - Engagement by Week).
Applied Rate % - Engagement
Definition: Applied Rate % - Engagement measures the percentage of candidates who were reached out to via WhatsApp, Email, or SMS and went on to submit an application, filtered by message sent date.
How it is calculated: Divides candidates who applied (where outreach occurred before or on the application date) by all candidates reached out to.
Note: Also available broken down by channel (Applied Rate % - Engagement by Channel).
Hire Rate % - Engagement
Definition: Hire Rate % - Engagement measures the percentage of applications attributed to Engagement activity that resulted in a hire, filtered by message sent date.
How it is calculated: Divides hired applications on closed positions by all applications from Engagement activity.
Note: Also available broken down by channel (Hire Rate % - Engagement by Channel).
Total Messages Sent - Engagement
Definition: Total Messages Sent - Engagement measures the count of distinct messages sent to candidates via WhatsApp, Email, or SMS through the Engagement module, filtered by message sent date.
How it is calculated: Counts distinct messages sent.
Note: Also available broken down by channel (Total Messages Sent - Engagement by Channel).
Total Candidates Reached Out - Engagement
Definition: Total Candidates Reached Out - Engagement measures the count of distinct candidates who were contacted via WhatsApp, Email, or SMS through the Engagement module, filtered by message sent date.
How it is calculated: Counts distinct candidates contacted.
Note: Also available broken down by channel (Total Candidates Reached Out - Engagement by Channel).
Response Rate % - Engagement
Definition: Response Rate % - Engagement measures the percentage of candidates who responded to outreach sent via WhatsApp, Email, or SMS through the Engagement module, filtered by message sent date.
How it is calculated: Divides distinct candidates who replied (where outreach occurred before or on the application date) by all distinct candidates contacted under the same condition.
Note: Also available broken down by channel (Response Rate % - Engagement by Channel) and by day of week (Response Rate % - Engagement by Day of Week).
Average Days to Respond - Engagement
Definition: Average Days to Respond - Engagement measures the average number of days taken by a candidate to respond to an outreach message, filtered by activity date.
How it is calculated: Averages the number of days between first contact and first reply, per candidate-recruiter-position combination. Only records where both a reply and a contact are recorded are included.
Note: Also available broken down by channel (Avg Days to Respond - Engagement by Channel) and by day of week (Avg. Days to Response - Engagement by Day of Week).
Campaigns
Covers bulk outreach messages sent as part of a named campaign, and applications sourced through a campaign link.
Data Sources & Event Reference
| Source | When it's triggered |
| Message with user_campaign_id set | A recruiter sends a message as part of a bulk outreach campaign |
| application_source with source_type = 'Campaign' | A candidate applies through a campaign link (sourcing timestamp recorded) |
How to refer in product:
[Insert screenshot: campaigns-how-to-refer-1.png]
[Insert screenshot: campaigns-how-to-refer-2.png]
[Insert screenshot: campaigns-how-to-refer-3.png]
Total Applications - Campaigns
Definition: Total Applications - Campaigns measures the count of distinct applications from candidates who were reached out to using the Campaigns feature, filtered by message sent date.
How it is calculated: Counts distinct applications tied to campaign activity.
Total Hires - Campaigns
Definition: Total Hires - Campaigns measures the count of distinct applications that resulted in a hire from candidates who were reached out to using the Campaigns feature, filtered by hire date.
How it is calculated: Counts distinct hired applications, on closed positions, tied to campaign activity.
Applied Rate % - Campaigns
Definition: Applied Rate % - Campaigns measures the percentage of candidates who were reached out using the Campaigns feature and went on to submit an application, filtered by message sent date.
How it is calculated: Divides distinct candidates with a recorded application by all distinct candidates reached out to via campaign.
Hire Rate % - Campaigns
Definition: Hire Rate % - Campaigns measures the percentage of applications attributed to the Campaigns feature that resulted in a hire, filtered by message sent date.
How it is calculated: Divides distinct hired applications (on closed positions) by all distinct applications from campaign activity.
Campaigns with Activity
Definition: Campaigns with Activity measures the count of distinct campaigns where at least one candidate was reached out to, filtered by message sent date.
How it is calculated: Counts distinct campaigns with recorded outreach.
Note: Also available broken down by month (Campaigns with Activity by Month).
Total Candidates Reached Out - Campaigns
Definition: Total Candidates Reached Out - Campaigns measures the count of distinct candidates who were contacted using the Campaigns feature, filtered by message sent date.
How it is calculated: Counts distinct candidates contacted via campaign.
Note: Also available broken down by month (Total Candidates Reached Out - Campaigns by Month).
Average Days from Contact to Application - Campaigns
Definition: Average Days from Contact to Application - Campaigns measures the average number of days between the first campaign contact date and the application submission date, for candidates who applied, filtered by first contact date.
How it is calculated: Averages the days between first campaign contact and application date, per campaign and candidate.
Average Days from Contact to Hire - Campaigns
Definition: Average Days from Contact to Hire - Campaigns measures the average number of days between the first campaign contact date and the hire date, for candidates on closed positions who were hired, filtered by first contact date.
How it is calculated: Averages the days between first campaign contact and hire date, per campaign and candidate, for hired candidates on closed positions.
Scheduling
Covers interview scheduling: interview plans, self-scheduling links, and standard scheduling invites, whether initiated by the recruiter or the candidate.
Data Sources & Event Reference
User Action Events (from user_analytics) — track what the recruiter did in the UI:
| Event(s) | Feature | When it's triggered |
| scheduling_scheduled_with_interview_plan | Interview Plan | Recruiter schedules an interview using a structured interview plan template |
| scheduling_open_event | Open Scheduling | Recruiter sends a self-scheduling link so the candidate picks their own time slot |
| scheduling_event_scheduling_send / scheduling_event_scheduling_reschedule | Event Scheduling | A panel/group-style interview is scheduled or rescheduled |
| scheduling_send / scheduling_send_hold / scheduling_requests_schedule / open_scheduling_candidate_confirm | Standard Scheduling | A basic interview invite is sent, put on hold, requested, or confirmed by the candidate |
Calendar Events (from user_calendar_events) — track the actual interview records created in the calendar system:
| scheduling_method | schedule_category | When it's triggered |
| candidateChoice / openScheduling | Candidate Self-Scheduled | The candidate picked the interview slot themselves via a self-scheduling link |
| suggestedTimes / specificTime | Recruiter Scheduled | The recruiter proposed or set a specific time for the interview |
Interview statuses tracked (after filtering out DELETED, DRAFT, CANDIDATE_ASSISTANCE_REQUESTED): PENDING (invite sent, not yet confirmed), CONFIRMED (candidate accepted the slot), CANCELLED (cancelled after being scheduled). Each calendar event record also captures the first time the interview was created (activity_timestamp) and the latest status (final_status), so the full lifecycle from scheduling to outcome is visible.
How to refer in product:
[Insert screenshot: scheduling-how-to-refer-1.png]
[Insert screenshot: scheduling-how-to-refer-2.png]
Total Scheduling Requests
Definition: Total Scheduling Requests measures the count of distinct scheduling requests sent to candidates, filtered by scheduling request date.
How it is calculated: Counts distinct scheduling requests.
Average Days to Interview - Scheduling
Definition: Average Days to Interview - Scheduling measures the average number of days taken from the scheduling request to the interview, filtered by scheduling request date.
How it is calculated: Averages the number of days between the scheduling request and the interview.
Note: Also available broken down by scheduling type (Avg. Days to Interview - Scheduling Type).
Interviewer Scheduled
Definition: Interviewer Scheduled measures the count of distinct scheduling requests that were initiated by a recruiter or interviewer, filtered by scheduling request date.
How it is calculated: Counts distinct scheduling requests where the schedule category is "Recruiter Scheduled."
Candidate Self-Scheduled
Definition: Candidate Self-Scheduled measures the count of distinct scheduling requests that were initiated by the candidate themselves, filtered by scheduling request date.
How it is calculated: Counts distinct scheduling requests where the schedule category is "Candidate Self-Scheduled."
Interviewer Response Rate %
Definition: Interviewer Response Rate % measures the percentage of candidate self-scheduled interviews where the interviewer responded (i.e. did not remain in pending status), filtered by scheduling request date.
How it is calculated: Divides candidate-self-scheduled requests that moved out of pending status by all candidate-self-scheduled requests.
Note: Also available broken down by day of week (Interviewer Response Rate % by Day of Week).
Candidate Response Rate %
Definition: Candidate Response Rate % measures the percentage of recruiter- or interviewer-led scheduling requests that received a response from the candidate, filtered by scheduling request date.
How it is calculated: Divides recruiter-scheduled requests that moved out of pending status by all recruiter-scheduled requests.
Note: Also available broken down by day of week (Candidate Response Rate % by Day of Week).
Candidate - Type of Response
Definition: Candidate - Type of Response measures the count of distinct recruiter-led scheduling requests, broken down by the candidate's response type, filtered by scheduling request date.
How it is calculated: Counts distinct recruiter-scheduled requests, grouped by final response status.
Interviewer - Type of Response
Definition: Interviewer - Type of Response measures the count of distinct candidate self-scheduled interviews, broken down by the interviewer's response type, filtered by scheduling request date.
How it is calculated: Counts distinct candidate-self-scheduled requests, grouped by final response status.
Candidate assistance requested meetings
Definition: Candidate Assistance Requested Meetings measures the count of distinct scheduling requests where the candidate requested assistance, filtered by scheduling request date.
How it is calculated: Counts distinct scheduling requests flagged with a candidate assistance request.
Governance (Feedback)
Covers feedback requested from and submitted by interviewers and reviewers — both quick feedback forms and structured post-interview feedback.
Data Sources & Event Reference
| feedback_type | When it's triggered |
| quick_feedback | A reviewer submits a quick form on a candidate |
| interview_feedback | An interviewer submits structured post-interview feedback |
How to refer in product:
[Insert screenshot: feedback-how-to-refer-1.png]
[Insert screenshot: feedback-how-to-refer-2.png]
[Insert screenshot: feedback-how-to-refer-3.png]
[Insert screenshot: feedback-how-to-refer-4.png]
[Insert screenshot: feedback-how-to-refer-5.png]
[Insert screenshot: feedback-how-to-refer-6.png]
Average days to respond - Feedback
Definition: Average Days to Respond - Feedback measures the average number of days between the feedback request date and the feedback submission date, filtered by feedback request date.
How it is calculated: Averages the days between request and submission, for submitted feedback only.
Note: Also available broken down by day of week (Avg. Days to respond - Feedback by Day of Week) and by responder seniority (Avg. Days to respond - Feedback by Responder Seniority).
Feedback requesters
Definition: Feedback Requesters measures the count of distinct users who requested feedback on a candidate, filtered by feedback request date.
How it is calculated: Counts distinct users who submitted a feedback request.
Feedback responders
Definition: Feedback Responders measures the count of distinct users who responded to a feedback request, filtered by feedback request date.
How it is calculated: Counts distinct reviewers who responded to a feedback request.
Feedbacks Requested
Definition: Feedbacks Requested measures the count of distinct feedback requests submitted, filtered by feedback request date.
How it is calculated: Counts distinct feedback requests.
Note: Also available broken down by feedback type (Type of Feedbacks Requested).
Response Rate % - Feedback
Definition: Response Rate % - Feedback measures the percentage of feedback requests that were submitted, filtered by feedback request date.
How it is calculated: Divides submitted feedback requests by all feedback requests.
Note: Also available broken down by feedback type (Response Rate % - Type of Feedback).
Positive Feedback Rate %
Definition: Positive Feedback Rate % measures the percentage of submitted feedbacks that were rated as positive, filtered by feedback request date.
How it is calculated: Divides feedbacks with a positive overall rating by all submitted feedbacks.
Note: Also available broken down by feedback type (Positive Rate % - Type of Feedback).
Feedbacks Pending
Definition: Feedbacks Pending measures the count of distinct feedback requests that have not yet received a response from the feedback reviewer, filtered by feedback request date.
How it is calculated: Counts distinct feedback requests still in "requested" status.
Note: Also available broken down by feedback type (Type of Feedbacks Pending).
Hiring Manager - Type of Feedbacks
Definition: Hiring Manager - Type of Feedbacks provides a breakdown of feedback activity per hiring manager, filtered by feedback request date. Only users identified as hiring managers are included.
How it is calculated: For each hiring manager: Feedbacks Requested (count of requests), Feedback Pending (count still unanswered), Unique Positions (distinct positions covered), Response Rate % and Positive Feedback Rate % (calculated as above, per manager), and Feedbacks with Follow Up Enabled %.
Community
Covers outreach and responses tied to sourcing communities/talent pools (position records with a sourcing type), via Email, SMS, or WhatsApp.
Data Sources & Event Reference
| Event(s) | Channel | When it's triggered |
| contact / reply | A recruiter contacts or receives a reply from a candidate in a sourcing community via email | |
| sms_send_success / sms_reply | SMS | SMS sent or reply received in a sourcing community |
| whatsapp_send_success / whatsapp_reply | WhatsApp message sent or reply received in a sourcing community |
Community events are specifically tied to positions where system_id = 'sourcing'.
How to refer in product:
[Insert screenshot: community-how-to-refer-1.png]
[Insert screenshot: community-how-to-refer-2.png]
[Insert screenshot: community-how-to-refer-3.png]
[Insert screenshot: community-how-to-refer-4.png]
Total Applications - Community
Definition: Total Applications - Community measures the count of distinct applications from candidates who responded via Email, SMS, or WhatsApp to messages sent from the Community UI, filtered by response date.
How it is calculated: Counts distinct applications where the candidate had a reply event.
Applied Rate % - Community
Definition: Applied Rate % - Community measures the percentage of candidates who responded to Community outreach and went on to submit an application, filtered by activity date.
How it is calculated: Divides distinct candidates who replied and applied by all distinct candidates contacted (outbound events).
Total Hires - Community
Definition: Total Hires - Community measures the count of distinct applications from candidates who responded to Community outreach and were ultimately hired, filtered by hire date.
How it is calculated: Counts distinct hired applications (on closed positions) among candidates who replied to Community outreach.
Hire Rate % - Community
Definition: Hire Rate % - Community measures the percentage of applications from candidates who responded to Community outreach that resulted in a hire, filtered by activity date.
How it is calculated: Divides hired applications (on closed positions) by all applications tied to TA activity, restricted to Community reply events.
Communities Created
Definition: Communities Created measures the count of distinct communities created, filtered by activity date. Each community is represented by a distinct position record.
How it is calculated: Counts distinct community (sourcing) positions created.
Candidates Outreached - Community
Definition: Candidates Outreached - Community measures the count of distinct candidates who were contacted via Email, SMS, or WhatsApp from the Community UI, filtered by message sent date.
How it is calculated: Counts distinct candidates contacted via outbound events.
Note: Also available broken down by channel (Candidates Outreached - Community by Channel).
Candidates Responded - Community
Definition: Candidates Responded - Community measures the count of distinct candidates who responded via Email, SMS, or WhatsApp to messages sent from the Community UI, filtered by response date.
How it is calculated: Counts distinct candidates with a reply event.
Note: Also available broken down by channel (Candidates Responded - Community by Channel).
Response Rate % - Community
Definition: Response Rate % - Community measures the percentage of candidates who responded to outreach sent via Email, SMS, or WhatsApp from the Community UI, filtered by message sent date.
How it is calculated: Divides distinct candidates who replied by all distinct candidates contacted via outbound events.
Note: Also available broken down by channel (Response Rate % - Community by Channel).
Sourcing
Covers candidates sourced via the Chrome Extension, LinkedIn CRM export, or direct resume import.
Data Sources & Event Reference
| Event | When it's triggered |
| add_to_pipeline (source = 'extension') | A recruiter adds a candidate while browsing externally (e.g., LinkedIn) via the Chrome Extension |
| export_to_crm | A recruiter exports a candidate to LinkedIn CRM |
| import_profile | A recruiter imports profile into the EF Platform |
How to refer in product:
[Insert screenshot: sourcing-how-to-refer-1.png]
[Insert screenshot: sourcing-how-to-refer-2.png]
[Insert screenshot: sourcing-how-to-refer-3.png]
[Insert screenshot: sourcing-how-to-refer-4.png]
Total Hires - Sourcing
Definition: Total Hires - Sourcing measures the count of distinct applications from candidates sourced via sourcing features (Chrome Extension, Referrals, Import Resume) that resulted in a hire, filtered by hire date.
How it is calculated: Counts distinct hired applications, on closed positions, among sourced candidates.
Note: Also available broken down by sourcing feature type (Total Hires - Sourcing by Feature Type).
Total Candidates Sourced
Definition: Total Candidates Sourced measures the count of distinct candidates sourced via sourcing features (Chrome Extension, Referrals, Import Resume), filtered by activity date.
How it is calculated: Counts distinct candidates sourced.
Note: Also available broken down by sourcing feature type (Total Candidates Sourced by Feature Type).
Applied Rate % - Sourcing
Definition: Applied Rate % - Sourcing measures the percentage of sourced candidates who went on to submit an application, filtered by activity date.
How it is calculated: Divides distinct candidates who applied by all distinct candidates sourced.
Note: Also available broken down by sourcing feature type (Applied Rate % - Sourcing by Feature Type).
Hire Rate % - Sourcing
Definition: Hire Rate % - Sourcing measures the percentage of applications from sourced candidates that resulted in a hire, filtered by activity date.
How it is calculated: Divides distinct hired applications (on closed positions) by all distinct applications from sourced candidates.
Note: Also available broken down by sourcing feature type (Hire Rate % - Sourcing by Feature Type).
Avg Match Score of Applied Candidates
Definition: Avg Match Score of Applied Candidates measures the average match score (0–5 scale) of candidates sourced via sourcing tools who subsequently submitted an application. A higher score indicates sourcing tools are attracting high-fit talent.
How it is calculated: Averages the match score of sourced candidates who applied, restricted to calibrated positions so scores are meaningful.
Note:
- A score of 3.5 or above indicates good fit alignment with position requirements.
- Filtered by sourcing activity date.
Application Velocity
Definition: Application Velocity measures the average number of days from when a candidate is first sourced via a sourcing tool to when they submit an organic career site application.
How it is calculated: Averages the days between first-sourced date and career site application date, for candidates who applied via the career site after being sourced.
Note:
- Only candidates who applied via the career site after being sourced are included.
- Also available broken down by sourcing feature (Application Velocity by Sourcing Feature) and as a weekly trend (Application Velocity Trend).
- Filtered by sourcing activity date.
Application Velocity by Sourcing Feature
Definition: Application Velocity by Sourcing Feature breaks down the average days from sourcing to career site application by each sourcing tool, showing which tools drive the fastest candidate engagement.
How it is calculated: Averages the days between first-sourced date and career site application date, grouped by sourcing feature.
Note:
- Only candidates who applied via the career site after being sourced are included.
- Lower values indicate the tool is driving faster candidate engagement.
- Industry benchmark: ~20 days.
- Filtered by sourcing activity date.
Application Velocity Trend
Definition: Application Velocity Trend tracks the weekly average number of days from sourcing to career site application, broken down by sourcing feature.
How it is calculated: Averages the days between first-sourced date and career site application date each week, grouped by sourcing feature.
Note:
- Only candidates who applied via the career site after being sourced are included.
- A declining trend indicates improving sourcing-to-engagement speed.
- Filtered by sourcing activity date.
Hiring Velocity
Definition: Hiring Velocity measures the average number of days from when a candidate is first sourced via a sourcing tool to when a hire decision is made.
How it is calculated: Averages the days between first-sourced date and hire date, for all sourced candidates who were hired, regardless of application source.
Note:
- Filtered by sourcing activity date.
- Industry benchmark: ~50 days.
- Also available broken down by sourcing feature as a weekly trend (Hiring Velocity Trend).
Hiring Velocity Trend
Definition: Hiring Velocity Trend tracks the weekly average number of days from sourcing to hire decision, broken down by sourcing feature.
How it is calculated: Averages the days between first-sourced date and hire date each week, grouped by sourcing feature, for all sourced candidates who were hired.
Note:
- A declining trend indicates improving end-to-end sourcing cycle speed.
- Industry benchmark: ~50 days.
- Filtered by sourcing activity date.
Recruiting Events
Covers career fairs, campus visits, and similar events — candidate activity uploaded from the event, and downstream outcomes (application, offer, hire).
Data Sources & Event Reference
Recruiter Action (from planned_event_activity):
| activity_type | When it's triggered |
| uploaded | A recruiter uploads candidate interaction data collected at a recruiting event (e.g., career fair, campus visit) |
Full Candidate Lifecycle (from recruiting_events):
| activity_type | activity_type_mapped | When it's triggered |
| uploaded | ADDED_TO_EVENT | Candidate's resume/profile was scanned or uploaded at the event |
| applied / all_applied | APPLIED | Candidate applied for a role at or after the event |
| offered / all_offered | OFFERED | Candidate received a job offer following the event |
| hired / all_hired | HIRED | Candidate was hired as a result of the event |
| NULL | NO_CANDIDATE_ACTIVITY_RECORDED | Candidate attended but no downstream activity was recorded |
Additional context per event: event type (event_type, event_category, event_bucket); location format — in-person, virtual, or hybrid (event_location_type); institution — university or school name for campus events; event state (is_published, is_cancelled, event_status); hierarchy — parent_id links sub-events back to a parent event.
[Insert screenshot: recruiting-events-how-to-refer-1.png]
[Insert screenshot: recruiting-events-how-to-refer-2.png]
[Insert screenshot: recruiting-events-how-to-refer-3.png]
[Insert screenshot: recruiting-events-how-to-refer-4.png]
Recruiting Events Created
Definition: Recruiting Events Created measures the count of distinct recruiting events that were created within the selected reporting period, filtered by event start date. Each event is counted once regardless of how many candidates or activities are associated with it.
How it is calculated: Counts distinct recruiting events created.
Candidates - Recruiting Events
Definition: Candidates - Recruiting Events measures the count of distinct candidates who were associated with any recruiting event within the selected reporting period, filtered by event start date. A candidate is counted once regardless of how many events or activities they are linked to.
How it is calculated: Counts distinct candidates linked to any recruiting event.
Candidates added to Recruiting Events
Definition: Candidates Added to Recruiting Events measures the count of distinct candidate-event combinations where a candidate was added to a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate was uploaded/added to the event. Each candidate is counted once per event they were added to.
Registered Candidates to Recruiting Events
Definition: Registered Candidates to Recruiting Events measures the count of distinct candidate-event combinations where a candidate registered for a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate registered. Each candidate is counted once per event they registered for.
Assessed Candidates - Recruiting Events
Definition: Assessed Candidates - Recruiting Events measures the count of distinct candidate-event combinations where a candidate was assessed during a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate was assessed. Each candidate is counted once per event they were assessed in.
Candidates Attended - Recruiting Events
Definition: Candidates Attended - Recruiting Events measures the count of distinct candidate-event combinations where a candidate attended a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate attended. Each candidate is counted once per event they attended.
Applicants - Recruiting Events
Definition: Applicants - Recruiting Events measures the count of distinct candidate-event combinations where a candidate applied for a position associated with a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate applied. Each candidate is counted once per event they applied through.
Offered - Recruiting Events
Definition: Offered - Recruiting Events measures the count of distinct candidate-event combinations where a candidate received an offer for a position associated with a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate was offered. Each candidate is counted once per event they were offered through.
Hired - Recruiting Events
Definition: Hired - Recruiting Events measures the count of distinct candidate-event combinations where a candidate was hired for a position associated with a recruiting event, filtered by event start date.
How it is calculated: Counts distinct candidate-event pairs where the candidate was hired. Each candidate is counted once per event they were hired through.
Recruiting Events: Candidates across stages
Definition: Recruiting Events: Candidates Across Stages provides a per-event breakdown of candidate progression through all recruiting event stages, filtered by event start date. Results are split by event name, event ID, creator, start date, and event type.
How it is calculated: For each event: Candidates (total distinct candidates), Added to Event, Registered, Assessed, Attended, Applicants, Offered, and Hired — each counted as distinct candidate-event combinations at that stage.