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, together with Calibration and Profile Tag — is tracked as distinct events, which roll up into the metrics below. The dashboard is organized into tabs matching the main modules; this guide follows the same structure. Calibration and Profile Tag do not have a tab of their own and appear only in the Overall Metrics tab.

Overall

TA Module Reference

How each TA module is derived from underlying product events. This is described once here and applies to every tab.

• Sourcing — Chrome Extension (adding a candidate from the Chrome sourcing extension), Import Resume (importing a profile) or LinkedIn CRM (exporting a candidate to an external CRM). Covers candidate-sourcing actions performed outside the normal application flow.
• Calibration — Position Calibration (calibration 80% complete, confirmed, 100% complete). Tracks progress through setting up a position's location, skills, titles, work experience and similar-candidate criteria.
• Scheduling — any scheduling event other than interviewer-specific events, split into four types by priority: Interview Plan, Open Scheduling, Event Scheduling and Standard Scheduling. Each scheduling request is assigned exactly one type by priority, so a request that touches several event types is counted once.
• Engagement — Email, SMS or WhatsApp messages sent by a recruiter to a candidate, limited to message types contact, sms_send and whatsapp_send with no campaign attached. Covers one-off, non-campaign outreach.
• Campaigns — messages that carry a campaign, or applications whose source is a campaign link (this second path attributes an application to the campaign even without a message record).
• Feedback — any feedback request record. Quick Feedback and Interview Feedback are shown by name; any other feedback type is shown under its raw type value.
• Profile Tag — tags applied manually by a user (system tags are not included).
• Community — events on community (sourcing) positions, split by channel into Email, SMS, WhatsApp or Other, plus each community application's current stage (the most recent stage per candidate per community position).
• Recruiting Events — candidate activity uploaded from career fairs, campus visits and similar events.

How Applications and Hires Are Attributed

These rules apply to Total Applications, Total Hires, Hire Rate %, Applied Rate % and the Recruitment Funnel, and to the application and hire metrics on each module tab.

• Matching — activity is matched to an application from the same candidate on the same position. Profile Tag and Community activity is matched on the candidate alone.
• Activity before application — for Engagement, Profile Tag, Scheduling, Feedback, Sourcing, Campaigns, Calibration and Recruiting Events, an application is attributed only when the TA activity occurred on or before the application date.
• Community — the application's most recent stage must fall after the candidate's most recent stage in that community.
• Date range — the date filter applies to the activity, not to the application or the hire. An application or hire that happens outside the selected range still counts if the activity driving it falls inside the range.
• Hires — an application counts as a hire when it has a recorded hire date. Positions are not restricted to closed positions.
• Application Attribution Within N days breakdown — this breakdown shows how the counted applications/hires are distributed by the number of days between the TA module activity and the application submission.

Note: For Hire Rate % and Applied Rate % and Recruitment Funnel, only those community applications/hires are considered for which the application's most recent stage falls within 90 days of the candidate's most recent stage in that community.

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 listed in the TA Module Reference.

How it is calculated: Counts the number of distinct users with activity recorded in any module.

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. The slices are Recruiter, Hiring Manager, Recruiter + Hiring Manager (users holding both roles), Employee, and Others.

Positions Worked On

Definition: Positions Worked On measures the count of distinct positions that were touched by at least one activity within the selected reporting period, filtered by activity date.

How it is calculated: Counts each distinct position with recorded activity in Calibration, Campaigns, Community, Engagement, Feedback, Recruiting Events, Scheduling or Sourcing. A position is counted once regardless of how many activities or users were involved.

Note: Profile Tag activity is not counted toward positions worked on.

Total Applications

Definition: Total Applications measures the count of distinct applications that were submitted as a direct result of TA module activity, filtered by activity date.

How it is calculated: Counts distinct applications tied to TA module activity under the attribution rules above.

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 in any module.

Note: Every activity record is counted, including Community reply events.

Total Hires

Definition: Total Hires measures the count of distinct applications that resulted in a hire due to TA module activity, filtered by activity date.

How it is calculated: Counts distinct hired applications attributable to TA module activity under the attribution rules above.

Note: The date filter applies to the activity date, not the hire date.

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 attributed to TA activity by all applications attributed to TA activity.

Note: Numerator and denominator are scoped to the same set of attributed applications, so this is a conversion rate within the attributed applications, not a rate against all candidates touched by TA activity. For Community, the numerator also requires the activity to have occurred on or before the application date; the denominator does not apply that extra check, so the numerator is the stricter of the two.

Applied Rate %

Definition: Applied Rate % measures the percentage of candidates touched by any TA module activity who went on to submit an application, filtered by activity date.

How it is calculated: Divides distinct candidates whose application is attributed to TA activity (following the attribution rules above) by all distinct candidates with any TA activity in the period.

Note: The denominator is not split by module or by the Community timing rule; it includes every candidate with a recorded activity, including Community replies.

Recruitment Funnel

Definition: Recruitment Funnel measures the count of distinct applications attributed to TA module activity that passed through each hiring stage group, filtered by activity date.

How it is calculated: Counts distinct attributed applications per hiring stage group, under the attribution rules above. An application appears in every stage group it has reached, so the same application is counted in several bars.

Note: The bars show how many applications reached each stage, not where applications currently sit. Only stages mapped to a stage group are included, and the rejection stage group is not shown as a bar. An application rejected at a later stage still counts in the stage groups it reached before. Applications with no mapped stage are reported in the card that follows.

Recruitment Funnel - Applications without any Stage Group Data

Definition: Measures the count of distinct applications, attributed to TA module activity, that have no recognized funnel stage mapped to them, filtered by activity date. These are applications the funnel cannot place on any bar because the stage data is missing or unmapped.

How it is calculated: Counts distinct attributed applications that have no stage group recorded.

Note: This is a data-quality signal and should always be 0. If it is not, configure the stage mapping in Admin Console → Product Setup → Analytics → Map unmapped Stages.

Recruitment Funnel - Rejected Applications

Definition: Measures the count of distinct applications, attributed to TA module activity, that have reached a rejection stage group, filtered by activity date. This is the rejected bucket alongside the funnel.

How it is calculated: Counts distinct attributed applications that have reached a stage group whose name contains "reject."

Note: A rejected application is identified only if a reject stage is configured in Stage Group Mapping under Analytics in Product Setup. An application counted here also appears in the funnel bars for the stages it reached before rejection.

Monthly Trend of Active Users

Definition: 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: 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 whose previous active month was exactly one calendar month earlier by all active users that month. The result is rounded to a whole number.

Monthly Trend of Active Recruiters

Definition: Measures the count of distinct recruiters who performed any activity on any TA module, broken down by month, filtered by activity date.

How it is calculated: Counts distinct active users who hold a recruiter role, per calendar month.

Monthly Trend of Repeat Recruiters %

Definition: Measures the percentage of monthly active recruiters who were also active in the prior month, broken down by month, filtered by activity date.

How it is calculated: For each month, divides recruiters whose previous active month was exactly one calendar month earlier by all active recruiters that month. The result is rounded to a whole number.

Overall User Activity by Active User

Definition: A pivot table with one row per active user and one column per TA module. Each cell shows how many activity records that user logged in that module during the selected date range, filtered by activity date. It shows who is using the platform, which modules each person works in, and where usage is concentrated or missing.

How it is calculated: Counts activity records per user and per module, with row totals, column totals and subtotals. Every module and every user with an activity record is included.

Engagement

Covers one-off direct messages (Email, SMS, WhatsApp) sent by a recruiter to a candidate outside of a bulk campaign.

Total Applications - Engagement

Definition: 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 the outreach occurred on or before the application date.

Note: Also available as a weekly trend (Total Applications - Engagement by Week). Each application is placed in the week its qualifying message was sent, not the week it was submitted, and the chart is not split by channel.

Total Hires - Engagement

Definition: Measures the count of distinct applications that resulted in a hire, attributed to Engagement module activity, filtered by message sent date.

How it is calculated: Counts distinct hired applications where the outreach occurred on or before the application date.

Note: The date filter applies to the message sent date, not the hire date. Also available as a weekly trend (Total Hires - Engagement by Week), which is not split by channel.

Applied Rate % - Engagement

Definition: 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 the outreach occurred on or before the application date) by all candidates reached out to in the period.

Note: Also available broken down by channel (Applied Rate % - Engagement by Channel). A candidate reached on two channels appears in both bars, so the bars are not additive.

Hire Rate % - Engagement

Definition: 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 by all applications from Engagement activity, where the outreach occurred on or before the application date in both cases.

Note: Positions are not restricted to closed positions. Also available broken down by channel (Hire Rate % - Engagement by Channel).

Total Messages Sent - Engagement

Definition: 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: Only one-off messages are counted; campaign messages are excluded. Also available broken down by channel and week (Total Messages Sent - Engagement by Channel).

Total Candidates Reached Out - Engagement

Definition: 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. A candidate is counted once however many messages or channels were used.

Note: Also available broken down by channel and week (Total Candidates Reached Out - Engagement by Channel). A candidate contacted on two channels, or in two weeks, appears in each, so the lines do not add up to the card.

Response Rate % - Engagement

Definition: Measures the percentage of candidates contacted via WhatsApp, Email, or SMS who replied, filtered by message sent date.

How it is calculated: Divides distinct candidates with a recorded reply by all distinct candidates contacted.

Note: All Engagement contacts are included. There is no requirement that the candidate applied, so this is the reply rate across all outreach. A candidate counts as having replied when a reply time is recorded, even if the reply came after the selected range. Also available broken down by channel (Response Rate % - Engagement by Channel) and by day of week the message was sent (Response Rate % - Engagement by Day of Week).

Average Days to Respond - Engagement

Definition: Measures the average number of days between the first time a candidate was contacted and their first reply, filtered by message sent date.

How it is calculated: Averages the whole 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: Candidates who never replied are not included, so this reflects how fast responders answer, not how many answer. First contact and first reply are taken across all of that candidate's messages from the recruiter on the position, over all channels and including campaign messages, and across all time, so the first contact can fall before the selected range. The average is taken over records, so a combination with several message records counts once per record. A same-day reply is 0 days. 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), where each record is placed by the day its own message was sent.

Campaigns

Covers bulk outreach messages sent as part of a named campaign, and applications sourced through a campaign link.

Total Applications - Campaigns

Definition: 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 that were submitted on or after the campaign contact. Applications that predate the outreach are excluded.

Note: The date filter applies to the campaign contact, not the application.

Total Hires - Campaigns

Definition: Measures the count of distinct applications that resulted in a hire from candidates who were reached out to using the Campaigns feature, filtered by message sent date.

How it is calculated: Counts distinct hired applications where the campaign contact occurred on or before the application date.

Note: The date filter applies to the campaign contact, not the hire date. Positions are not restricted to closed positions.

Campaigns with Activity

Definition: 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: 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: 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 campaign contact and application date, only where the contact occurred on or before the application.

Note: Candidates who were contacted but never applied are not included, so this reflects conversion speed among those who applied.

Average Days from Contact to Hire - Campaigns

Definition: Measures the average number of days between the first campaign contact date and the hire date, for hired candidates whose application is attributable to the campaign contact, filtered by first contact date.

How it is calculated: Averages the days between campaign contact and hire date, only where the contact occurred on or before the application and the application has a recorded hire date.

Note: Candidates who were contacted but never hired are not included.

Scheduling

Covers interview scheduling: interview plans, self-scheduling links, and standard scheduling invites, whether initiated by the recruiter or the candidate.

How Scheduling Is Counted

These rules apply to the request counts and response metrics under Activities & Insights, and are described once here.

• Unit counted — a scheduling request (one calendar event) can hold several interview slots, for example one per interview in a loop. Each slot is counted, once, however many interviewers or candidate actions it has.
• Included requests — only requests that currently have a scheduled meeting time. A time is recorded when a time slot is chosen or preset and is cleared when the whole request is cancelled. Requests still waiting for a time and fully cancelled requests are therefore not counted, and a slot with no interviewer listed does not appear.
• Dates — Activities & Insights metrics are filtered by the date the request was created. Candidate assistance requested meetings and the Outcomes metrics are filtered by the date of the underlying activity.
• Schedule category — Candidate Self-Scheduled (candidateChoice, openScheduling), Recruiter Scheduled (suggestedTimes, specificTime) or Other / Unknown for any other method.
• Candidate status — taken from the latest candidate event on the request, so every slot of a request shares it: CONFIRMED (candidate confirm, calendar confirm or open scheduling confirm), CANCELLED (cancel or calendar decline), RESCHEDULED, REQUESTED_ASSISTANCE, otherwise PENDING_CANDIDATE_ACTION.
• Interviewer status — taken from the interviewer whose most recent action is latest: CONFIRMED (confirm or calendar confirm), DECLINED, REQUESTED_ASSISTANCE, otherwise PENDING_INTERVIEWER_CONFIRMATION. If the person who scheduled the request is also an interviewer, their scheduled event counts as confirmed automatically.
• Responded — a slot counts as responded when its status is anything other than pending. For interviewers, one interviewer acting is enough.

Average Days to Interview - Scheduling

Definition: Measures the average number of days taken from the scheduling request to the interview, filtered by activity date.

How it is calculated: Averages the days recorded on 'days to interview' scheduling events.

Note: A request that logs more than one such event, for example after a reschedule, contributes more than once. Also available broken down by scheduling type (Avg. Days to Interview - Scheduling Type).

Avg. Days to Interview - Scheduling Type

Definition: Measures the average number of days between a scheduling request and the interview, broken down by how the request was scheduled, filtered by activity date.

How it is calculated: Averages the days recorded on 'days to interview' events, grouped by scheduling type. Each request is assigned the highest-priority type among its events (1 is highest), and every event on the request is reported under that one type.

Note: Interview Plan (1) — scheduled from an interview plan template. Open Scheduling (2) — a self-scheduling link is sent and the candidate picks a slot. Event Scheduling (3) — a panel or group-style interview is scheduled or rescheduled. Standard Scheduling (4) — a basic invite is sent, put on hold, requested, or confirmed by the candidate. Bars are sorted from highest to lowest average.

Total Scheduling Requests

Definition: Measures the number of interview slots in scheduling requests created in the selected date range.

How it is calculated: Counts distinct interview slots.

Recruiter-Led Scheduled

Definition: Measures the number of interview slots, in requests created in the selected date range, where the recruiter chose the times.

How it is calculated: Counts distinct interview slots where the schedule category is "Recruiter Scheduled" (suggested times or a specific time).

Note: Slots with any other scheduling method are in neither this card nor Candidate Self-Scheduled, so the two may not add up to Total Scheduling Requests.

Candidate Self-Scheduled

Definition: Measures the number of interview slots, in requests created in the selected date range, where the candidate picks their own time from the options offered.

How it is calculated: Counts distinct interview slots where the schedule category is "Candidate Self-Scheduled" (candidate choice or open scheduling).

Note: A self-scheduled request for which the candidate has not yet picked a time is not counted.

Interviewer Response Rate %

Definition: Measures the percentage of interview slots where an interviewer has taken an action, for requests created in the selected date range.

How it is calculated: Divides slots whose interviewer status is not pending by all distinct slots.

Note: Recruiter-led and candidate self-scheduled requests are both included. Also available broken down by the day of the week the request was created (Interviewer Response Rate % by Day of Week); the day label carries a number prefix so it sorts Sunday to Saturday.

Candidate Response Rate %

Definition: Measures the percentage of interview slots where the candidate has taken an action, for requests created in the selected date range.

How it is calculated: Divides slots whose candidate status is not pending by all distinct slots.

Note: Requests the candidate never acted on and that never got a time are not in the data, so the rate reads higher than the true response rate. Also available broken down by the day of the week the request was created (Candidate Response Rate % by Day of Week).

Candidate - Type of Response

Definition: Measures the count of distinct interview slots, broken down by the candidate's response type, for requests created in the selected date range.

How it is calculated: Counts distinct slots grouped by candidate status. Each slot falls in exactly one slice: CONFIRMED, CANCELLED, RESCHEDULED, REQUESTED_ASSISTANCE or PENDING_CANDIDATE_ACTION.

Note: Recruiter-led and candidate self-scheduled requests are both included. The PENDING and CANCELLED slices are understated because requests still waiting for a time, and fully cancelled requests, are not in the data.

Interviewer - Type of Response

Definition: Measures the count of distinct interview slots, broken down by the interviewers' response type, for requests created in the selected date range.

How it is calculated: Counts distinct slots grouped by interviewer status. Each slot falls in exactly one slice: CONFIRMED, DECLINED, REQUESTED_ASSISTANCE or PENDING_INTERVIEWER_CONFIRMATION.

Note: Recruiter-led and candidate self-scheduled requests are both included.

Candidate Assistance Requested Meetings

Definition: Measures the count of distinct scheduling requests where the candidate requested assistance, filtered by the date the assistance was requested.

How it is calculated: Counts distinct scheduling requests with a candidate assistance request event.

Note: A request where the candidate later confirmed is still counted here, although it does not appear in the REQUESTED_ASSISTANCE slice of Candidate - Type of Response, which shows only the latest action.

Avg. Time to Schedule a Request by Coordinator

Definition: Measures the average number of hours between a scheduling request being created and that request being scheduled, filtered by request creation date. It is the coordinator turnaround figure — how long a request waits before someone acts on it.

How it is calculated: Averages the hours between the earliest 'request created' event and the earliest 'request scheduled' event on each request.

Note: Requests that were never scheduled are not included, so this reflects completed work only, not outstanding backlog. Also available per coordinator (Avg Time to Schedule a Request by each Coordinator), where the coordinator is the user who created the request.

Requests Scheduled by Coordinator

Definition: Measures the count of distinct scheduling requests in the scheduling-requests flow, filtered by request creation date. It supplies the volume context for the turnaround averages.

How it is calculated: Counts distinct scheduling requests, whether or not they were ever scheduled.

Note: Also available per coordinator (Requests Scheduled by each Coordinator). This count is not directly comparable to Total Scheduling Requests, which counts individual interview slots.

Avg. Time to Confirm - Scheduling

Definition: Measures the average number of hours from a request being scheduled — the point the invite goes out — until the interview is confirmed, filtered by the date the request was scheduled.

How it is calculated: Averages the hours from the scheduled time to the confirmation time, where confirmation is the later of the candidate's confirmation and the last interviewer calendar confirmation (if only one occurred, that one is used).

Note: A request counts as confirmed as soon as those confirmations exist; it does not require every interviewer to have confirmed. The result is rounded to whole hours, and requests still awaiting confirmation are not included. Also available by type of scheduling (Avg. Time to Confirm - Type of Scheduling), by candidate (Avg. Time to Confirm by Candidate - Scheduling) and by interviewer (Avg. Time to Confirm by Interviewer - Scheduling), which ends at the last interviewer calendar confirmation.

Governance (Feedback)

Covers feedback requested from and submitted by interviewers and reviewers — both quick feedback forms and structured post-interview feedback.

How Feedback Is Counted

These rules apply to every Feedback metric and are described once here.

• Date — every Feedback metric is filtered by the date the feedback was requested.
• Status — SUBMITTED means the reviewer responded. REQUESTED and AI_RECOMMENDED are treated as pending.
• Feedback type — Quick Feedback or Interview Feedback; any other type is shown under its raw value.
• Response time — measured in whole calendar days, so a same-day submission is 0. A feedback request is joined to the candidate's applications on that position, so a candidate with more than one application to the same position makes the request count more than once in an average.

Average days to respond - Feedback

Definition: Measures the average number of days between the feedback request date and the feedback submission date.

How it is calculated: Averages the days between request and submission, for submitted feedback only.

Note: Requests still waiting have no response time and are left out. 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). Seniority comes from the employee record of the reviewer; reviewers with no employee record, typically external interviewers, are grouped under a blank value.

Feedback requesters

Definition: Measures the count of distinct users who requested feedback on a candidate.

How it is calculated: Counts distinct users who raised a feedback request.

Note: Every requester is counted whatever their role; there is no recruiter-role restriction.

Feedback responders

Definition: Measures the count of distinct reviewers (hiring managers and interviewers) named on feedback requests.

How it is calculated: Counts distinct reviewers feedback was assigned to.

Note: A reviewer is counted whether or not they submitted anything, so this is the number of reviewers feedback was requested from, not the number who responded. Use Response Rate % - Feedback for the responded share.

Feedbacks Requested

Definition: Measures the count of distinct feedback requests raised.

How it is calculated: Counts distinct feedback requests, whether or not the reviewer has responded.

Note: Also available broken down by feedback type and week (Type of Feedbacks Requested).

Response Rate % - Feedback

Definition: Measures the percentage of feedback requests that were submitted.

How it is calculated: Divides submitted feedback requests by all feedback requests, whatever their status.

Note: Also available broken down by feedback type and week (Response Rate % - Type of Feedback).

Positive Feedback Rate %

Definition: Measures the percentage of submitted feedbacks that were rated as positive.

How it is calculated: Divides submitted feedbacks with a positive overall rating by all submitted feedbacks.

Note: Pending requests are excluded from both sides. Also available broken down by feedback type and week (Positive Rate % - Type of Feedback).

Feedbacks Pending

Definition: Measures the count of distinct feedback requests that have not yet received a response from the feedback reviewer.

How it is calculated: Counts distinct feedback requests with a status of REQUESTED or AI_RECOMMENDED.

Note: A request stays pending for as long as it is unanswered, so older requests inside the range keep appearing here. Also available broken down by feedback type and week (Type of Feedbacks Pending).

Hiring Manager - Type of Feedbacks

Definition: Provides a breakdown of feedback activity per hiring manager. Only responders who hold a hiring manager role are included; the role is checked on the person feedback was assigned to, not on the user who requested it.

How it is calculated: For each hiring manager: Feedbacks Requested (count of requests), Feedbacks Pending (count still unanswered), Unique Positions (distinct positions covered), Response Rate % and Positive Feedback Rate % (calculated as above, per manager), Feedbacks Pending % and Feedbacks with Follow Up Enabled %.

Note: Percentages are rounded to whole numbers.

Feedback Funnel - All Responders

Definition: Provides the same per-reviewer breakdown for every feedback responder, without the hiring manager restriction.

How it is calculated: For each responder: Feedbacks Requested, Feedbacks Pending, Unique Positions, Response Rate %, Positive Feedback Rate %, Feedbacks Pending % and Feedbacks with Follow Up Enabled %, calculated per responder.

Note: Percentages are rounded to whole numbers.

Community

Covers outreach and responses tied to sourcing communities/talent pools (position records with a sourcing type), via Email, SMS, or WhatsApp.

How Community Is Counted

These rules apply to the Community metrics and are described once here.

• Outreach events — contact (Email), sms_send_success (SMS) and whatsapp_send_success (WhatsApp).
• Reply events — reply (Email), sms_reply (SMS) and whatsapp_reply (WhatsApp).
• Date — Community metrics are filtered by activity date: the message sent date for outreach and the response date for replies.
• Application attribution (Total Applications and Total Hires) — an application counts toward Community when its most recent stage is on or after the candidate's most recent stage in that Community. The Application Attribution Within N Days breakdown shows how long after the Community stage the application's most recent stage fell. The bars up to the 90-day bracket correspond to the 90-day rule below and also reflect the number shown in the product.
• 90-day attribution window (Applied Rate % and Hire Rate %) — an application counts only when its most recent stage falls within 90 days of the candidate's most recent stage in that Community.

Note: Both rules are measured against the application's most recent stage, not its submission date, and Community rows are matched to applications on the candidate alone, so the application may sit in a different position from the Community.

Total Applications - Community

Definition: Measures the count of distinct applications attributable to Community activity, filtered by activity date.

How it is calculated: Counts distinct applications for which application last stage was after the community last stage.

Total Hires - Community

Definition: Measures the count of distinct applications attributable to Community activity that resulted in a hire, filtered by activity date.

How it is calculated: Counts distinct applications for which application last stage is after community last stage and have a recorded hire date.

Applied Rate % - Community

Definition: Measures the percentage of candidates touched by Community activity whose application falls within the 90-day attribution window, filtered by activity date.

How it is calculated: Divides distinct candidates who meet the attribution rule by all distinct candidates with any Community activity in the period.

Note: The denominator includes outbound contacts, replies and any other Community activity, not only candidates who were contacted.

Hire Rate % - Community

Definition: Measures the percentage of Community-attributable applications that resulted in a hire, filtered by activity date.

How it is calculated: Divides applications that meet the 90-day attribution rule and are hired by all applications that meet the 90-day attribution rule.

Note: The numerator also requires the community activity to have occurred on or before the application date; the denominator does not, so the numerator is the stricter of the two.

Community Application Attribution by Days Since Activity

Definition: Measures the count of distinct applications attributable to Community activity, grouped by the number of days between the candidate's last Community stage change and the application's last stage change, filtered by activity date.

How it is calculated: Counts distinct applications whose last stage change occurred on or after the candidate's last Community stage change, bucketed by the days between the two.

Note: An application can appear in more than one bucket if the candidate belongs to several Communities, so the buckets can add up to more than the total number of applications.

Community Hire Attribution by Days Since Activity

Definition: Measures the count of distinct applications attributable to Community activity that resulted in a hire, grouped by the number of days between the candidate's last Community stage change and the application's last stage change, filtered by activity date.

How it is calculated: Counts distinct hired applications whose last stage change occurred on or after the candidate's last Community stage change, bucketed by the days between the two.

Note: A hire can appear in more than one bucket if the candidate belongs to several Communities, so the buckets can add up to more than the total number of hires.

Communities with Activities

Definition: Measures the count of distinct communities that had any recorded activity in the selected date range. Each community is represented by a distinct position record.

How it is calculated: Counts distinct community (sourcing) positions with activity.

Note: A community that was created earlier but had no activity in the range is not counted.

Current community stages

Definition: Shows the count of distinct candidates at their current community stage.

How it is calculated: Counts distinct candidates per current stage, for community (sourcing) positions. Stages, in order: 1st Contact, Added, Interested, Responded, Not Interested, Follow up Later, Recruiter Screen, HM Screen.

Note: This table is a current snapshot; the date range does not apply. Only candidates in these eight stages are shown; a candidate in any other stage is not counted. A candidate in more than one community is counted once in each community stage they sit in.

Candidates Outreached - Community

Definition: 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. A candidate contacted several times, or on several channels, is counted once.

Note: Also available broken down by channel (Candidates Outreached - Community by Channel). A candidate contacted on two channels is counted once per channel, so the slices do not add up to the card.

Candidates Responded - Community

Definition: 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: Measures the percentage of candidates who responded to outreach sent via Email, SMS, or WhatsApp from the Community UI, within the selected date range.

How it is calculated: Divides distinct candidates with a reply event by all distinct candidates contacted via outbound events.

Note: Replies and outreach are each placed by their own activity date. 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.

Sourcing Features

Metrics on this tab are filtered by sourcing activity date and are limited to three features, described once here.

• Chrome Extension — a recruiter adds a candidate from the Chrome sourcing extension while browsing externally.
• Import Resume — a recruiter imports a profile into the platform.
• LinkedIn CRM — a recruiter exports a candidate to LinkedIn CRM.

Total Hires - Sourcing

Definition: Measures the count of distinct applications from candidates sourced via the sourcing features that resulted in a hire.

How it is calculated: Counts distinct hired applications where the sourcing activity occurred on or before the application date.

Note: The date filter applies to the sourcing activity, not the hire date. Positions are not restricted to closed positions. Also available broken down by sourcing feature type (Total Hires - Sourcing by Feature Type).

Total Candidates Sourced

Definition: Measures the count of distinct candidates sourced via the sourcing features.

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: Measures the percentage of sourced candidates who went on to submit an application on or after being sourced.

How it is calculated: Divides distinct candidates whose application date falls on or after the sourcing activity by all distinct candidates sourced.

Note: Also available broken down by sourcing feature type (Applied Rate % - Sourcing by Feature Type).

Avg Match Score of Applied Candidates

Definition: 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. A position is calibrated when at least four of its five calibration criteria are set (location, skills, titles, similar candidates, work experience).

Note: A score of 3.5 or above indicates good fit alignment with position requirements. The average is taken across sourcing activity records, so a candidate sourced more than once for the same position contributes more than once.

Application Velocity

Definition: 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: Applications are classified by priority — Internal, then Referral, then Career site, otherwise Recruiter/sourced — so internal applicants and referrals who applied through the career site are excluded. The first-sourced date is the earliest sourcing activity for that candidate, on that position, via that sourcing feature; a candidate sourced through more than one tool has a separate baseline per tool. Also available broken down by sourcing feature (Application Velocity by Sourcing Feature) and as a weekly trend (Application Velocity Trend). Trend points are placed by the week of the sourcing activity. Industry benchmark: ~20 days.

Application Velocity by Sourcing Feature

Definition: 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: Lower values indicate the tool is driving faster candidate engagement. Industry benchmark: ~20 days.

Application Velocity Trend

Definition: 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: A declining trend indicates improving sourcing-to-engagement speed.

Hiring Velocity

Definition: 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 after being sourced, regardless of application source.

Note: No career site restriction applies. Also available broken down by sourcing feature as a weekly trend (Hiring Velocity Trend). Industry benchmark: ~50 days.

Hiring Velocity Trend

Definition: 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. Each point is placed by the week of the sourcing activity, not the hire. Industry benchmark: ~50 days.

Recruiting Events

Covers career fairs, campus visits, and similar events — candidate activity uploaded from the event, and downstream outcomes (application, offer, hire).

How Recruiting Events Are Counted

These rules apply to every Recruiting Events metric and are described once here.

• Date — filtered by event start date, which is when the event takes place, not when it was set up.
• Records — each row is one candidate activity on an event. An event with no candidate activity still has one row with no activity type, so every event is counted, including events that have no candidate activity yet.
• Stages are not a strict funnel — the stage counts are independent activity records; a later stage is not limited to candidates who appear in an earlier one, so counts need not decrease from stage to stage and must not be summed.
• Applied, Offered and Hired — these combine outcomes on event-associated positions with outcomes on any enterprise position, with no time limit between the candidate joining the event and the outcome.

Recruiting Events Created

Definition: Measures the count of distinct recruiting events 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, including events that have no candidate activity yet.

Candidates - Recruiting Events

Definition: Measures the count of distinct candidates who were associated with any recruiting event within the selected reporting period, filtered by event start date.

How it is calculated: Counts distinct candidates linked to any recruiting event. A candidate is counted once regardless of how many events or activities they are linked to.

Recruiting Events - Activity

Definition: Measures the count of distinct candidate-event pairs recorded against recruiting events, broken down by activity type, filtered by event start date.

How it is calculated: Counts distinct candidate-event pairs per activity type. A candidate who progressed through several stages of the same event appears in more than one bar.

Note: Activity types: ADDED_TO_EVENT, INVITED, INVITED_TO_EVENT, RESPONDED (Yes, No and Maybe RSVPs all fall in this bar), REGISTERED, ATTENDED, ASSESSED, APPLIED, OFFERED, HIRED, ADDED_TO_POSITION, SCHEDULED, ARCHIVED, and NO_CANDIDATE_ACTIVITY_RECORDED (an event with no candidate activity recorded against it). The bars count candidate-event pairs, so an event with no candidate adds nothing to that last bar.

Recruiting Events: Candidates across stages

Definition: 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 stage counted as distinct candidate-event pairs at that stage.

Note: Candidates counts distinct candidates, while every stage column counts distinct candidate-event pairs. Added to Event, Registered, Assessed and Attended come from the raw activity type; Applicants, Offered and Hired come from the mapped activity type. Rows are ordered by event start date, ascending.