This feature is currently in open beta.
Information in this article may not reflect the most up-to-date changes, as the product is actively being updated.
This glossary explains the standard fields available in the new Greenhouse Analytics experience, which uses an updated data model. Use it to understand what each field means, what kind of data it contains, and how it can be used when building a data view (as a filter, group, or column).
Fields are organized by category, which reflects the type of object or record they belong to — such as applications, candidates, or jobs. The same field category may be available across multiple subjects. For example, Department fields appear in Applications, Jobs, Openings, and more.
Field types and uses
Greenhouse Analytics fields fall into two types:
- Dimension — A categorical or descriptive field used to group or segment data. Dimensions are used to break down measures. Examples: Offer created at, Job name, Is candidate work authorized?, Application stage ID
- Measure — A quantitative field that can be aggregated. Measures are numeric and can be summed, averaged, or counted. Examples: Applications, Closed jobs, Time to schedule interview (minutes)
Within an analytics data view, fields can be used as columns in a results table, as filters to narrow your data, or as groupings to aggregate it. For a step-by-step guide to building a data view, see Set up dashboards and data views in Analytics.
Fields are organized by category (e.g., Applications, Openings, Offer versions) and may include related data from other categories. For example, when using Applications, you also have access to Candidate fields like "Candidate full name."
Note: Not all fields support all three uses. Some may be visible in tables but not usable as filters or group-by values.
Subjects
The data view builder starts with a subject, which defines what kind of data to focus on. Below is a list of subjects currently available.
| Subject | Description | Category |
| Applications | Individual candidate applications to specific jobs, including status, source, and key milestones in the hiring process. | Record |
| Application stage changes | Each record represents a candidate moving from one stage to another in the pipeline. | Event |
| Approval flows | Approval flows for offers and jobs, with aggregated counts of approver groups, approvers, and end-to-end durations. | Record |
| Approver groups | Approver groups within an approval flow, with aggregated approver counts and group-level durations. | Record |
| Approver requests | Individual approver requests within an approval flow, including response status, reminders, and time to resolve. | Record |
| Confirmed fraud signals | Individual fraud signals confirmed for a candidate within a fraud report, including signal type, severity, and data domain. | Record |
| Daily employee engagement | Daily totals of engagement activity to track outreach volume and trends over time. | Summary |
| Fraud reports | Fraud detection reports and their outcomes for candidates, including severity, status, confirmed signals, and dismissal details. | Record |
| Hiring pipeline | Summary of application movement through the hiring pipeline, with one record per job, stage, and priority. | Summary |
| Identity verifications | Identity verification requests for candidates, including verification status, partner details, and individual check results. | Record |
| Interviewer activity | Individual interviewer records for each scheduled interview. | Record |
| Interviews | Scheduled interview sessions. Each event can have multiple participants. | Event |
| Jobs | Open roles and requisitions, including hiring targets, status, and associated job details. | Record |
| Offer versions | Details on offers and their revisions, including compensation details. | Record |
| Openings | Approved job openings associated with a job, including status and hiring progress. | Record |
| Scorecard attribute ratings | Individual attribute ratings interviewers give on a scorecard, with one row per rated scorecard attribute. | Record |
| Scorecard question responses | Individual interviewer answers to scorecard questions, with one row per question on a scorecard. | Record |
| Talent Matching scores | Talent Matching's AI-generated scores per candidate application, including match strength buckets, human overrides, and per-bucket counts. | Record |
Field definitions
Application fields
These fields describe individual applications. They are available when using: Applications, Openings, Offer versions, Interviews, Interviewer activity, and Application stage changes.
| Field name | Description | Field type |
| Application ID | Unique identifier for the application. | Dimension |
| Application created at | When the application was created. | Dimension |
| Application updated at | When the application was last updated. | Dimension |
| Application rejected at | When the application was rejected. | Dimension |
| Application last activity at | When the most recent activity on the application occurred. | Dimension |
| Applications | Number of applications submitted. | Measure |
| Active applications | Number of applications currently in progress (not hired or rejected). | Measure |
| Prospect applications | Number of applications submitted by prospects instead of direct candidates. | Measure |
| Hired applications per job | Number of applications that resulted in a hire. | Measure |
| Rejected applications | Number of applications that were rejected. | Measure |
Application stage change fields
These fields describe each time a candidate moves from one stage to another. They are available when using: Application stage changes.
| Field name | Description | Field type |
| Application ID | Unique identifier for the application. | Dimension |
| Application stage ID | Unique identifier for the application's stage. | Dimension |
| Application stage entered at | When the application entered this stage. | Dimension |
| Application stage exited at | When the application exited this stage. | Dimension |
| Application stage record created at | When the application stage record was created. | Dimension |
| Application stage record updated at | When the application stage record was last updated. | Dimension |
| Application stages | Number of stage entries for the application. | Measure |
| Active application stages | Number of stages the application is currently active in. | Measure |
| Time in stage (seconds) | Time the candidate spent in this stage, measured in seconds. | Measure |
| Time in stage (minutes) | Total time the application spent in the stage, measured in minutes. | Measure |
| Time in stage (hours) | Total time the application spent in the stage, measured in hours. | Measure |
| Time in stage (days) | Total time the application spent in the stage, measured in days. | Measure |
Application status fields
These fields describe the status of an application. They are available when using: Applications.
| Field name | Description | Field type |
| Application status code | Code assigned to the application's current status. | Dimension |
| Application status name | Name of the application's current status. | Dimension |
| Application status description | Description of the application's current status. | Dimension |
Approval flow fields
These fields describe offer approval flows and their outcomes. They are available when using: Approval flows.
| Field name | Description | Field type |
| Approval flow updated at | When the approval flow was last updated in the source system. | Dimension |
| Approval flow first request sent at | The earliest approval request sent timestamp across all approvers in this flow. | Dimension |
| Approval flow last group resolved at | When the last approver group was resolved, representing the flow's completion time. | Dimension |
| Approval flows | Number of approval flows. | Measure |
| Approver groups (total) | Total number of approver groups within the approval flow. | Measure |
| Approver groups requested | Number of approver groups that were requested. | Measure |
| Exception groups | Number of approver groups that only activate for out-of-range values. | Measure |
| Required approver groups | Number of approver groups that are always required, excluding exception-only groups. | Measure |
| Approvers required | Total number of approvers required to complete the approval flow. | Measure |
| Total approvers requested | Total number of approvers across all groups in the flow who were requested. | Measure |
| Approved approvers | Number of approvers who have approved within this flow. | Measure |
| Rejected approvers | Number of approvers who have rejected within this flow. | Measure |
| Pending approvers | Number of approvers still waiting to take action within this flow. | Measure |
| Approvers remaining | Number of additional approvers still needed to satisfy all group thresholds in this flow. | Measure |
| Approval flow duration (hours) | Time from when the first approval request was sent to when the last group was resolved, measured in hours. | Measure |
| Approval flow duration (days) | Time from when the first approval request was sent to when the last group was resolved, measured in days. | Measure |
Approver fields
These fields describe individual approver requests within an approval flow. They are available when using: Approver requests.
| Field name | Description | Field type |
| Approver request sent at | When the approver request was sent. | Dimension |
| Approver request resolved at | When the approver request was resolved (approved/rejected). | Dimension |
| Approver request reminder sent at | When the last approver request reminder was sent. | Dimension |
| Exception group | Whether this group activates only for exception (out-of-range) scenarios. | Dimension |
| Approver request sent | Whether a request was sent for this approver request. | Measure |
| Approved approver requests | Number of approver requests with an approved status. | Measure |
| Rejected approver requests | Number of approver requests with a rejected status. | Measure |
| Pending approver requests | Number of approver requests that are still pending (waiting or due). | Measure |
| Approver request response time (hours) | Time from when the approval request was sent to when the approver responded, measured in hours. | Measure |
| Approver request response time (days) | Time from when the approval request was sent to when the approver responded, measured in days. | Measure |
| Reminders sent | Number of manual reminders sent to the approver. | Measure |
| Auto-reminders sent | Number of automatic reminders sent to the approver. | Measure |
Approver group fields
These fields describe approver groups within an approval flow. They are available when using: Approver groups.
| Field name | Description | Field type |
| Approval flow updated at | When the approval flow was last updated in the source system. | Dimension |
| Approver group first request sent at | The earliest approval request sent timestamp across all approvers in this group. | Dimension |
| Approver group resolved at | When the approver group was resolved in the source system. | Dimension |
| Approvers required | Number of approvers needed to satisfy this group's requirement. | Dimension |
| Exception group | Whether this group activates only for exception (out-of-range) scenarios. | Dimension |
| Total approvers requested | Total number of approvers in this group who were requested. | Measure |
| Approved approvers | Number of approvers who have approved within this group. | Measure |
| Rejected approvers | Number of approvers who have rejected within this group. | Measure |
| Pending approvers | Number of approvers still waiting to take action within this group. | Measure |
| Approvers remaining | Number of additional approvers still needed to satisfy this group's threshold. | Measure |
| Approver group duration (hours) | Time from when the first approval request was sent to when the group was resolved, measured in hours. | Measure |
| Approver group duration (days) | Time from when the first approval request was sent to when the group was resolved, measured in days. | Measure |
Candidate education fields
These fields describe the education records associated with a candidate's application. They are available when using: Applications.
| Field name | Description | Field type |
| School name | Name of the school or institution listed on the candidate's education record. | Dimension |
| Degree | Degree earned or pursued at the school listed on the candidate's education record. | Dimension |
| Discipline | Field of study or major listed on the candidate's education record. | Dimension |
| Education records per application | Number of education records associated with a candidate on this application. | Measure |
Candidate fields
These fields describe individual candidates. They are available when using: Applications, Offer versions, Interviews, Interviewer activity, Confirmed fraud signals, Fraud reports, Identity verifications, Scorecard attribute ratings, and Scorecard question responses.
| Field name | Description | Field type |
| Candidate ID | Unique identifier for the candidate. | Dimension |
| Candidate first name | Candidate's first name. | Dimension |
| Candidate last name | Candidate's last name. | Dimension |
| Candidate full name | Candidate's full name. | Dimension |
| Candidate most recent company | Company where the candidate was most recently employed. | Dimension |
| Candidate most recent job title | Job title most recently held by the candidate. | Dimension |
| Candidate home address | Candidate's home address as originally entered during the application process. | Dimension |
| Can email candidate? | Whether the candidate can be emailed from Greenhouse. | Dimension |
| Is candidate migrated? | Whether the candidate record was created through a data migration. | Dimension |
| Is candidate work authorized? | Nonstandard field. Whether the candidate is authorized to work without visa sponsorship. NULL means the field is not configured for this organization or was not set on the candidate record. | Dimension |
| Candidate created at | When the candidate was created. | Dimension |
| Candidate updated at | When the candidate was last updated. | Dimension |
Candidate rating fields
These fields describe the rating an interviewer gave to a candidate. They are available when using: Interviewer activity.
| Field name | Description | Field type |
| Rating name | Name of the rating option. | Dimension |
Confirmed fraud signal fields
These fields describe individual confirmed fraud signals. They are available when using: Confirmed fraud signals.
| Field name | Description | Field type |
| Confirmed fraud signal created at | When the confirmed fraud signal was created. | Dimension |
| Confirmed fraud signal ID | Unique identifier for the confirmed fraud signal in the source system. | Dimension |
| Fraud report ID | Unique identifier for the parent fraud report in the source system. | Dimension |
| Application ID | Unique identifier for the application. | Dimension |
| Confirmed fraud signal severity | Severity of this confirmed fraud signal (for example, 'Weak' or 'Strong'). | Dimension |
| Fraud signal ID | Unique identifier for the fraud signal in the source system. | Dimension |
| Fraud signal name | Name of the fraud signal as defined in the source system (for example, 'PHONE_VOIP_DIGITAL' or 'IP_TIME_ZONE_MISMATCH'). | Dimension |
| Fraud signal class code | Code indicating the customer-facing signal class (for example, 'IDENTITY_VERIFYING', 'WEAK', or 'HIGH_RISK'). | Dimension |
| Fraud signal type code | Code indicating the type of fraud signal (for example, 'POSITIVE' or 'FRAUD'). | Dimension |
| Fraud signal data domain | Data domain examined by this fraud signal (for example, 'LOCATION' or 'EMAIL'). | Dimension |
| Fraud signal severity code | Code indicating the default severity of this fraud signal (for example, 'WEAK' or 'STRONG'). | Dimension |
| Fraud signal created at | When the fraud signal was created. | Dimension |
| Fraud signal updated at | When the fraud signal was last updated. | Dimension |
| Flagged fraud candidates | Number of distinct candidates with at least one confirmed fraud signal. | Measure |
| Confirmed fraud signals | Number of confirmed fraud signals with 'Weak' or 'Strong' severity. | Measure |
Coordinator fields
These fields describe the coordinator assigned to an application. They are available when using: Applications, Offer versions, Interviewer activity.
| Field name | Description | Field type |
| Coordinator first name | Coordinator's first name. | Dimension |
| Coordinator last name | Coordinator's last name. | Dimension |
| Coordinator full name | Coordinator's full name. | Dimension |
| Coordinator email address | Coordinator's email address. | Dimension |
| Is coordinator active? | Whether the coordinator is currently active. | Dimension |
| Coordinator created at | When the coordinator account was created. | Dimension |
| Coordinator updated at | When the coordinator account was last updated. | Dimension |
Current and last reached stage fields
These fields describe the current stage and the furthest stage an application has reached in the hiring process. They are available when using: Applications. Last reached stage name and Last reached stage milestone name are also available when using Talent Matching scores.
| Field name | Description | Field type |
| Current stage name | Name of the current stage in the hiring process (group-aware). | Dimension |
| Current stage milestone name | Milestone associated with the current stage (for example, application, assessment, offer). | Dimension |
| Last reached stage name | Name of the last reached stage in the hiring process (group-aware). | Dimension |
| Last reached stage milestone name | Milestone associated with the last reached stage (for example, application, assessment, offer). | Dimension |
Department fields
These fields describe the department associated with a job or application. They are available across most subjects. If your organization uses a department hierarchy, level-based fields let you group or filter by any level in the structure.
| Field name | Description | Field type |
| Department name | Name of the department. | Dimension |
| Department name path | The names of all departments from the top of the hierarchy down to this department, separated by |. | Dimension |
| Department level 1 name | Name of the top-level department in the hierarchy. | Dimension |
| Department level 2 name | Name of the department at hierarchy level 2. | Dimension |
| Department level 3 name | Name of the department at hierarchy level 3. | Dimension |
| Department level 4–10 name | Name of the department at hierarchy levels 4 through 10. | Dimension |
| Department created at | When the department record was created. | Dimension |
| Department updated at | When the department record was last updated. | Dimension |
| Departments | Number of departments. | Measure |
Fraud report fields
These fields describe fraud detection reports for candidates. They are available when using: Fraud reports.
| Field name | Description | Field type |
| Fraud report generated at | When the fraud report was generated. | Dimension |
| Fraud report signals resolved at | When all fraud report signals were resolved. | Dimension |
| Fraud report ID | Unique identifier for the fraud report in the source system. | Dimension |
| Application ID | Unique identifier for the application. | Dimension |
| Are fraud report signals resolved? | Whether fraud report signals are resolved. | Dimension |
| Fraud report outcome status | Status of the fraud report outcome (for example, 'Pending' or 'Success'). | Dimension |
| Fraud report outcome severity | Severity of the fraud report outcome (for example, 'Ok' or 'Strong Signals'). | Dimension |
| Flagged fraud candidates | Number of distinct candidates with at least one fraud report. | Measure |
| Fraud reports | Number of fraud reports. | Measure |
| Confirmed fraud signals | Number of confirmed fraud signals. | Measure |
| Average fraud report signals resolved time (seconds) | Average time from fraud report generation to resolution, measured in seconds. | Measure |
| Average fraud report signals resolved time (minutes) | Average time from fraud report generation to resolution, measured in minutes. | Measure |
| Average fraud report signals resolved time (hours) | Average time from fraud report generation to resolution, measured in hours. | Measure |
| Average fraud report signals resolved time (days) | Average time from fraud report generation to resolution, measured in days. | Measure |
Hiring manager fields
These fields describe the hiring manager associated with a job. They are available when using: Jobs, Applications, Openings, Approval flows, Approver requests, Approver groups, and Hiring pipeline.
| Field name | Description | Field type |
| Hiring manager first name | Hiring manager's first name. | Dimension |
| Hiring manager last name | Hiring manager's last name. | Dimension |
| Hiring manager full name | Hiring manager's full name. | Dimension |
| Hiring manager email address | Hiring manager's email address. | Dimension |
| Is hiring manager active? | Whether the hiring manager is currently active. | Dimension |
| Hiring manager created at | When the hiring manager account was created. | Dimension |
| Hiring manager updated at | When the hiring manager account was last updated. | Dimension |
| Hiring managers per application | Number of hiring managers associated with an application. | Measure |
| Average hiring managers per application | Average number of hiring managers associated with an application. | Measure |
Hiring pipeline fields
These fields describe application movement through the hiring pipeline. They are available when using: Hiring pipeline.
| Field name | Description | Field type |
| Job created at | When the hiring plan was created in the source system. | Dimension |
| Job updated at | When the hiring plan was last updated in the source system. | Dimension |
| Job opened at | When the hiring plan was opened. | Dimension |
| Job closed at | When the hiring plan was closed. | Dimension |
| Applications at or past stage | Count of applications that reached this stage or a higher-priority stage in the hiring plan. Stages at or below the highest priority an application reached are backfilled as counted, regardless of whether the application literally entered this specific stage. | Measure |
| Applications actually entered stage | Count of applications that literally entered this stage (one or more times). Does not backfill prior stages based on the application's highest priority reached. | Measure |
| Rejected applications | Count of rejected applications in the hiring pipeline. | Measure |
| Rejected by candidates | Count of applications rejected by candidates in the hiring pipeline. | Measure |
| Rejected by hiring team | Count of applications rejected by the hiring team in the hiring pipeline. | Measure |
| Hired applications | Count of hired applications in the hiring pipeline. | Measure |
Identity verification fields
These fields describe identity verification requests for candidates. They are available when using: Identity verifications.
| Field name | Description | Field type |
| Identity verification requested at | When the identity verification was requested. | Dimension |
| Identity verification completed at | When the identity verification was completed. | Dimension |
| Identity verification ID | Unique identifier for the identity verification record in the source system. | Dimension |
| Application ID | Unique identifier for the application associated with this verification. | Dimension |
| Identity verification dismissed? | Whether the identity verification was dismissed. | Dimension |
| Identity verification display status | Identity verification status as shown in the application (for example, 'VERIFIED' or 'FLAGGED'). | Dimension |
| Is last name matched? | Whether the candidate's last name matches Greenhouse records at the time of verification. | Dimension |
| Is email matched? | Whether the candidate's email matches Greenhouse records at the time of verification. | Dimension |
| Is phone number matched? | Whether the candidate's phone number matches Greenhouse records at the time of verification. | Dimension |
| Identity verification partner | Name of the identity verification partner (for example, Clear). | Dimension |
| Government ID type check performed? | Whether the verification partner performed the government ID type check for this verification. | Dimension |
| Government ID type verified? | Whether the government ID type check passed. | Dimension |
| Government ID expiry check performed? | Whether the verification partner performed the government ID expiry check for this verification. | Dimension |
| Government ID expiry verified? | Whether the government ID expiry check passed. | Dimension |
| Government ID name check performed? | Whether the verification partner performed the government ID name check for this verification. | Dimension |
| Government ID name verified? | Whether the government ID name check passed. | Dimension |
| Government ID authenticity check performed? | Whether the verification partner performed the government ID authenticity check for this verification. | Dimension |
| Government ID authenticity verified? | Whether the government ID authenticity check passed. | Dimension |
| Government ID image check performed? | Whether the verification partner performed the government ID image quality check for this verification. | Dimension |
| Government ID image verified? | Whether the government ID image check passed. | Dimension |
| Selfie match check performed? | Whether the verification partner performed the selfie match check for this verification. | Dimension |
| Selfie match verified? | Whether the selfie match check passed. | Dimension |
| Live selfie check performed? | Whether the verification partner performed the live selfie check for this verification. | Dimension |
| Live selfie verified? | Whether the live selfie check passed. | Dimension |
| Device check performed? | Whether the verification partner performed the device integrity check for this verification. | Dimension |
| Device verified? | Whether the device integrity check passed. | Dimension |
| VPN check performed? | Whether the verification partner performed the VPN detection check for this verification. | Dimension |
| VPN undetected? | Whether the VPN detection check passed (no VPN found). | Dimension |
| Identity verifications | Number of identity verifications requested. | Measure |
| Average identity verification completion time (seconds) | Average time from identity verification request to completion, in seconds. | Measure |
Interview attribute fields
These fields describe scheduling and format details for interviews. They are available when using: Interviewer activity.
| Field name | Description | Field type |
| Interview calendar type | Calendar type used for the interview (such as Outlook 365). | Dimension |
| Interview scheduling type | Scheduling type of the interview (such as offer, manual, or self-scheduled). | Dimension |
| Interview location type | Location of the interview (such as in person, phone call, or video conference). | Dimension |
| Interview video conference service | Video conferencing service used for the interview (such as Zoom, Google Meet, or Teams). | Dimension |
| Interview included video conferencing link? | Whether a video conferencing link was included for the interview. | Dimension |
| Interview scheduled with Calendly? | Whether Calendly was used to schedule the interview. | Dimension |
| Interview self-scheduled? | Whether self-scheduling was used for the interview. | Dimension |
| Interview scheduled using availability module? | Whether the availability module was used for the interview. | Dimension |
| Interview rescheduled? | Whether the interview was rescheduled. | Dimension |
| Interview scorecards required? | Whether interviewers are required to submit scorecards for the interview. | Dimension |
Interview fields
These fields describe scheduled interview sessions. They are available when using: Interviews.
| Field name | Description | Field type |
| Interview ID | Unique identifier for the interview record in the source system. | Dimension |
| Application ID | Unique identifier for the associated application record. | Dimension |
| Application stage ID | Unique identifier for the application stage linked to the interview. | Dimension |
| Interview created at | When the interview record was created. | Dimension |
| Interview updated at | When the interview record was last updated. | Dimension |
| Interview scheduled at | When the interview was scheduled. | Dimension |
| Interview availability confirmed at | When the candidate confirmed their availability for the interview. | Dimension |
| Interview started at | When the interview started. | Dimension |
| Interview ended at | When the interview ended. | Dimension |
| Interview application stage entered at | When the application entered the stage associated with this interview. | Dimension |
| Interview application stage exited at | When the application exited the stage associated with this interview. | Dimension |
| Interviews | Number of interviews conducted. | Measure |
| Interviewers | Number of distinct interviewers involved across the interviews. | Measure |
| Average interviewers per interview | Average number of interviewers assigned to each interview. | Measure |
| Interview duration (minutes) | Time spent in the interview, measured in minutes. | Measure |
| Average interview duration (minutes) | Average time spent in the interview, measured in minutes. | Measure |
| Interview duration by stage (minutes) | Time spent in interviews during a particular application stage, measured in minutes. | Measure |
| Time to schedule interview (minutes) | Time from when the candidate confirmed availability to when the interview was scheduled, measured in minutes. | Measure |
Interviewer activity fields
These fields describe individual interviewer records for each scheduled interview. They are available when using: Interviewer activity.
| Field name | Description | Field type |
| Interview ID | Unique identifier for the interview record in the source system. | Dimension |
| Scorecard ID | Unique identifier for the scorecard associated with the interview. | Dimension |
| Interview started at | When the interview started. | Dimension |
| Interview ended at | When the interview ended. | Dimension |
| Interview scorecard submitted at | When the interviewer submitted their scorecard. | Dimension |
| Interviewers | Number of distinct interviewers involved across the interviews. | Measure |
| Interview duration (minutes) | Time spent in the interview, measured in minutes. | Measure |
| Average interview duration (minutes) | Average time spent in interviews, measured in minutes. | Measure |
| Time to submit scorecard (minutes) | Time between the end of the interview and when the scorecard was submitted, measured in minutes. | Measure |
| Average time to submit scorecard (minutes) | Average time between interview end and scorecard submission, measured in minutes. | Measure |
| Time to submit scorecard (hours) | Total time between interview end and scorecard submission, measured in hours. | Measure |
| Average time to submit scorecard (hours) | Average time between interview end and scorecard submission, measured in hours. | Measure |
| Scorecard overall 'Definitely Not' recommendation | Count of overall 'Definitely Not' recommendations the interviewer gave on scorecards. | Measure |
| Scorecard overall 'No' recommendation | Count of overall 'No' recommendations the interviewer gave on scorecards. | Measure |
| Scorecard overall 'Strong Yes' recommendation | Count of overall 'Strong Yes' recommendations the interviewer gave on scorecards. | Measure |
| Scorecard overall 'Yes' recommendation | Count of overall 'Yes' recommendations the interviewer gave on scorecards. | Measure |
| Scorecard overall 'Mixed' recommendation | Count of overall 'Mixed' recommendations the interviewer gave on scorecards. | Measure |
| Scorecards | Number of interviews that have a scorecard in any status. | Measure |
| Edited scorecards | Number of scorecards that were edited after submission. | Measure |
| Scorecards with admin notes | Number of scorecards that included admin notes. | Measure |
| Scorecards with private notes | Number of scorecards that included private notes. | Measure |
| Scorecards with public notes | Number of scorecards that included public notes. | Measure |
| Scorecards with notes | Number of scorecards that included any note (admin, private, or public). | Measure |
| Scorecard focus attributes (total) | Total number of attributes designated as focus areas on the scorecard. | Measure |
| Completed scorecard focus attributes | Number of focus attributes on the scorecard that received a rating. | Measure |
| Scorecard attributes (total) | Total number of scorecard attributes on the scorecard. | Measure |
| Rated scorecard attributes | Number of scorecard attributes on the scorecard that received a rating. | Measure |
| Scorecard attribute rating score (total) | Total scorecard attribute rating score, on a scale where 1 is 'Definitely Not' and 5 is 'Strong Yes'. | Measure |
| Average scorecard attribute rating score | Average scorecard attribute rating score, on a scale where 1 is 'Definitely Not' and 5 is 'Strong Yes'. | Measure |
| Scorecard questions (total) | Total number of scorecard questions on the scorecard. | Measure |
| Scorecard question responses | Number of scorecard question responses recorded. | Measure |
| Scorecard question completion rate | Percentage of scorecard questions that received a response. | Measure |
| Outstanding scorecards | Number of scheduled interviews where no scorecard has been submitted. | Measure |
| Complete scorecards | Number of scorecards with a 'Complete' status. | Measure |
| Draft scorecards | Number of scorecards with a 'Draft' status. | Measure |
| Other scorecards | Number of scorecards with a status other than 'Complete' or 'Draft'. | Measure |
| Interviews requiring scorecard | Number of interviews that required a scorecard. | Measure |
Job fields
These fields describe jobs (also called hiring plans). They are available when using: Jobs, Applications, Openings, Offer versions, Interviews, Interviewer activity, Approval flows, Approver requests, Approver groups, Hiring pipeline, Confirmed fraud signals, Fraud reports, Identity verifications, Scorecard attribute ratings, Scorecard question responses, and Talent Matching scores.
| Field name | Description | Field type |
| Job ID | Unique identifier for the job. | Dimension |
| Job name | Name given to the job, usually matching the job title. | Dimension |
| Job requisition number | Unique identifier for the requisition associated with the job. | Dimension |
| Employment type | Employment type associated with the job (e.g., full-time, contract). | Dimension |
| Is job template? | Whether the job is a template. | Dimension |
| Is job confidential? | Whether the job is confidential. | Dimension |
| Job created at | When the job was created. | Dimension |
| Job updated at | When the job was last updated. | Dimension |
| Job opened at | When the job was opened. | Dimension |
| Job closed at | When the job was closed. | Dimension |
| Job first opening opened at | When the first opening for the job was opened. | Dimension |
| Job last opening opened at | When the most recent opening for the job was opened. | Dimension |
| Job first applied at | When the first application for the job was submitted. | Dimension |
| Job last applied at | When the most recent application for the job was submitted. | Dimension |
| Job last activity at | When the most recent activity on the job occurred. | Dimension |
| Reason for hire | Reason this job was opened (for example, Backfill, New Headcount). Non-standard custom field; value depends on how the organization configured it. | Dimension |
| Salary range min | Minimum of the salary range defined for this job. Non-standard custom field. | Dimension |
| Salary range max | Maximum of the salary range defined for this job. Non-standard custom field. | Dimension |
| Jobs | Number of jobs in the system. | Measure |
| Draft jobs | Number of jobs currently in draft status. | Measure |
| Open jobs | Number of jobs currently open and accepting applications. | Measure |
| Closed jobs | Number of jobs that have been closed. | Measure |
| Hired applications per job | Number of hired applications associated with a job. | Measure |
| Active stages per job | Number of active interview stages associated with a job. | Measure |
| Inactive stages per job | Number of inactive interview stages associated with a job. | Measure |
| Active openings per job | Number of active openings associated with a job. | Measure |
| Openings per job | Number of openings (active and closed) associated with a job. | Measure |
| Applications per job | Number of applications associated with a job. | Measure |
| Take-home tests started | Number of take-home tests that have been started for the job. | Measure |
| Take-home tests submitted | Number of take-home tests that have been submitted for the job. | Measure |
| Accepted offers per job | Number of offers accepted for the job. | Measure |
| Offers created per job | Number of offers created for the job. | Measure |
| Deprecated offers per job | Number of offer versions that were replaced by a newer version for the job. | Measure |
| Extended offers per job | Number of offers extended for the job. | Measure |
| Outstanding offers per job | Number of offers that are currently outstanding for the job. | Measure |
| Rejected offers per job | Number of offers rejected for the job. | Measure |
Job owner fields
These fields describe users who are part of a job's hiring team in a sourcer, recruiter, or coordinator capacity. They are available when using: Applications, Approval flows, Approver requests, and Approver groups.
| Field name | Description | Field type |
| Job hiring team role | Type of hiring team role assigned to the user, where 0 is sourcer, 1 is recruiter, and 2 is coordinator. | Dimension |
| Job hiring team role name | Name of the hiring team role assigned to the user (for example, Sourcer, Recruiter, or Coordinator). | Dimension |
| Is responsible recruiter or coordinator on this job? | Whether a recruiter or coordinator on a job's hiring team is the responsible person for this job's candidate tasks. | Dimension |
| Job owner first name | Job owner's first name. | Dimension |
| Job owner last name | Job owner's last name. | Dimension |
| Job owner full name | Job owner's full name. | Dimension |
| Job owner email address | Job owner's email address. | Dimension |
| Is job owner active? | Whether the job owner is currently active. | Dimension |
| Job owner created at | When the job owner account was created. | Dimension |
| Job owner updated at | When the job owner account was last updated. | Dimension |
| Job owners per application | Number of job owners associated with an application. | Measure |
| Average job owners per application | Average number of job owners associated with an application. | Measure |
Job role user fields
These fields describe users who have a job-level admin role (job admin or site admin) on a job. They are available when using: Applications, Approval flows, Approver requests, and Approver groups.
| Field name | Description | Field type |
| Job role | Name of the job role assigned to the user. | Dimension |
| Job role user first name | Job role user's first name. | Dimension |
| Job role user last name | Job role user's last name. | Dimension |
| Job role user full name | Job role user's full name. | Dimension |
| Job role user email address | Job role user's email address. | Dimension |
| Is job role user active? | Whether the job role user is currently active. | Dimension |
| Job role user created at | When the job role user account was created. | Dimension |
| Job role user updated at | When the job role user account was last updated. | Dimension |
| Job role users per application | Number of job role users associated with an application. | Measure |
| Average job role users per application | Average number of job role users associated with an application. | Measure |
Offer fields
These fields describe offer versions. They are available when using: Offer versions, Applications.
| Field name | Description | Field type |
| Offer ID | Unique identifier of the offer in the source system. | Dimension |
| Application ID | Unique identifier for the application associated with this offer version. | Dimension |
| Offer version number | Sequential version number of a specific offer, starting at 1 for the original version. | Dimension |
| Offer created at | When the offer version was created. | Dimension |
| Offer updated at | When the offer version was last updated. | Dimension |
| Offer sent at | When the offer version was sent. | Dimension |
| Offer resolved at | When the offer version was accepted or rejected. | Dimension |
| Offer start at | Start date specified in the offer. | Dimension |
| Offer versions | Number of versions that exist for a single offer. | Measure |
| Extended offer versions | Number of offer versions that were extended. | Measure |
| Outstanding offer versions | Number of offer versions that are currently outstanding. | Measure |
| Rejected offer versions | Number of offer versions that were rejected. | Measure |
| Accepted offer versions | Number of offer versions that were accepted. | Measure |
| Deprecated offer versions | Number of offer versions that were deprecated. | Measure |
Office fields
These fields describe the office associated with a job or application. They are available across most subjects. If your organization uses an office hierarchy, level-based fields let you group or filter by any level in the structure.
| Field name | Description | Field type |
| Office name | Name of the office. | Dimension |
| Office name path | The names of all offices from the top of the hierarchy down to this office, separated by |. | Dimension |
| Office level 1 name | Name of the top-level office in the hierarchy. | Dimension |
| Office level 2 name | Name of the office at hierarchy level 2. | Dimension |
| Office level 3 name | Name of the office at hierarchy level 3. | Dimension |
| Office level 4–10 name | Name of the office at hierarchy levels 4 through 10. | Dimension |
| Office created at | When the office was created. | Dimension |
| Office updated at | When the office was last updated. | Dimension |
| Offices | Number of offices. | Measure |
Opening fields
These fields describe approved job openings. They are available when using: Openings.
| Field name | Description | Field type |
| Opening ID | Unique identifier for the opening in the source system. | Dimension |
| User-defined opening ID | Identifier for the opening provided by a user, if one was added. | Dimension |
| Opening created at | When the opening was created. | Dimension |
| Opening updated at | When the opening was last updated. | Dimension |
| Opening opened at | When the opening was opened. | Dimension |
| Opening closed at | When the opening was closed. | Dimension |
| Opening target start at | Target date for the opening to be filled. | Dimension |
| Application created at | When the application used to fill the opening was created. | Dimension |
| Offer sent at | When the offer used to fill the opening was sent. | Dimension |
| Offer decision made at | When the offer used to fill the opening was accepted or rejected. | Dimension |
| Target start at | When the hired candidate is expected to start. | Dimension |
| Opening | Number of openings. | Measure |
| Open openings | Number of openings that are currently open. | Measure |
| Closed openings | Number of openings that are closed. | Measure |
| Pending openings | Number of openings that are pending. | Measure |
| Hired openings | Number of openings that were closed due to a hire. | Measure |
| Average time to hire (days) | Average number of days from application creation to offer resolution. | Measure |
| Average time to fill (days) | Average number of days from opening creation to target start. | Measure |
Prospect fields
These fields describe the prospect associated with a prospect-type application. They are available when using: Applications.
| Field name | Description | Field type |
| Prospect first name | Prospect's first name. | Dimension |
| Prospect last name | Prospect's last name. | Dimension |
| Prospect full name | Prospect's full name. | Dimension |
| Prospect most recent company | Company where the prospect was most recently employed. | Dimension |
| Prospect most recent job title | Job title most recently held by the prospect. | Dimension |
| Can email prospect? | Whether the prospect can be emailed from Greenhouse. | Dimension |
| Prospect created at | When the prospect was created. | Dimension |
Recruiter fields
These fields describe the recruiter assigned to an application. They are available when using: Applications, Offer versions.
| Field name | Description | Field type |
| Recruiter first name | Recruiter's first name. | Dimension |
| Recruiter last name | Recruiter's last name. | Dimension |
| Recruiter full name | Recruiter's full name. | Dimension |
| Recruiter email address | Recruiter's email address. | Dimension |
| Is recruiter active? | Whether the recruiter is currently active. | Dimension |
| Recruiter created at | When the recruiter account was created. | Dimension |
| Recruiter updated at | When the recruiter account was last updated. | Dimension |
Rejection reason fields
These fields describe why a candidate was rejected. They are available when using: Applications and Talent Matching scores.
| Field name | Description | Field type |
| Candidate rejection reason | Specific reason provided for why a candidate was rejected. | Dimension |
| Candidate rejection type | Category of rejection reason, such as 'We rejected them' or 'They rejected us.' | Dimension |
Scorecard attribute rating fields
These fields describe individual attribute ratings on a scorecard. They are available when using: Scorecard attribute ratings.
| Field name | Description | Field type |
| Scorecard submitted at | When the interviewer submitted their scorecard. | Dimension |
| Scorecard attribute name | Name of the scorecard attribute (for example, ownership or leadership). | Dimension |
| Is scorecard attribute active? | Whether the scorecard attribute is active. | Dimension |
| Scorecard attribute category | Name of the category the scorecard attribute belongs to. | Dimension |
| Is scorecard attribute category active? | Whether the scorecard attribute category is active. | Dimension |
| Rating name | Name of the rating option. | Dimension |
| Scorecard attribute priority number | Number assigned to a scorecard attribute, used to indicate the order shown on a scorecard (1 is higher than 2). | Dimension |
| Scorecard attribute category priority number | Number assigned to a scorecard attribute category, used to indicate the order shown on a scorecard (1 is higher than 2). | Dimension |
| Scorecard attributes | Number of scorecard attributes on a submitted scorecard. | Measure |
| Rated scorecard attributes | Number of scorecard attributes where the interviewer selected a rating. | Measure |
| Scorecard attributes with notes | Number of scorecard attributes that included a note. | Measure |
| Scorecard attributes with additional context | Number of scorecard attributes that included additional context. | Measure |
| Scorecard attribute rating score (total) | Total scorecard attribute rating score, on a scale where 1 is 'Definitely Not' and 5 is 'Strong Yes'. | Measure |
| Average scorecard attribute rating score | Average scorecard attribute rating score, on a scale where 1 is 'Definitely Not' and 5 is 'Strong Yes'. | Measure |
Scorecard question response fields
These fields describe individual interviewer answers to scorecard questions. They are available when using: Scorecard question responses.
| Field name | Description | Field type |
| Scorecard submitted at | When the interviewer submitted their scorecard. | Dimension |
| Scorecard question ID | Unique identifier for the scorecard question in the source system. | Dimension |
| Scorecard question | Text of the scorecard question as it appears on the interview kit. | Dimension |
| Scorecard question response type code | Code indicating the type of response expected for the scorecard question (for example, yes/no or text). | Dimension |
| Is scorecard question required? | Whether the scorecard question requires a response. | Dimension |
| Is scorecard question active? | Whether the scorecard question is active. | Dimension |
| Scorecard questions | Number of scorecard questions recorded across submitted scorecards. | Measure |
| Scorecard question responses | Number of scorecard question responses recorded across submitted scorecards. | Measure |
| Scorecard question 'Yes' responses | Number of scorecard yes/no responses recorded as 'Yes'. | Measure |
| Scorecard question 'No' responses | Number of scorecard yes/no responses recorded as 'No'. | Measure |
Scorecard status fields
These fields describe the status of an interviewer's scorecard. They are available when using: Interviewer activity.
| Field name | Description | Field type |
| Scorecard status name | Name of the scorecard's current status. | Dimension |
| Scorecard status description | Description of the scorecard's current status. | Dimension |
Source fields
These fields describe where an application originated. They are available when using: Applications, Offer versions, Confirmed fraud signals, Fraud reports, and Identity verifications.
| Field name | Description | Field type |
| Source public name | Public name of the source as displayed in Greenhouse. | Dimension |
| Source candidate-facing name | Source name shown to candidates. | Dimension |
| Source internal name | Internal name of the source, not shown to candidates. | Dimension |
| Is source displayed? | Whether the source is visible in Greenhouse. | Dimension |
| Is job board free? | Whether the source is a free job board. | Dimension |
| Source created at | When the source was created. | Dimension |
| Source updated at | When the source was last updated. | Dimension |
| Sourcing strategy name | Name of the sourcing strategy associated with the source. | Dimension |
| Sourcing strategy public name | Public name of the sourcing strategy. | Dimension |
| Sourcing strategy reporting name | Name of the sourcing strategy used for tracking purposes. | Dimension |
| Sourcing strategy internal name | Internal name of the sourcing strategy. | Dimension |
| Is sourcing strategy displayed? | Whether the sourcing strategy is visible in Greenhouse. | Dimension |
| Is sourcing strategy reportable? | Whether the sourcing strategy is available for use in analytics. | Dimension |
| Is sourcing strategy active? | Whether the sourcing strategy is currently active. | Dimension |
| Sourcing strategy created at | When the sourcing strategy was created. | Dimension |
| Sourcing strategy updated at | When the sourcing strategy was last updated. | Dimension |
Stage fields
These fields describe where a candidate is in the hiring pipeline. They are available when using: Application stage changes, Interviews, Hiring pipeline, Confirmed fraud signals, Fraud reports, Identity verifications, Interviewer activity, Scorecard attribute ratings, and Scorecard question responses.
| Field name | Description | Field type |
| Stage name | Name of the stage in the hiring process. | Dimension |
| Stage milestone name | Milestone associated with the stage (for example, Application, Assessment, Offer). | Dimension |
Talent Matching score fields
These fields describe AI-generated match scores per candidate application. They are available when using: Talent Matching scores.
| Field name | Description | Field type |
| Application match score created at | When the application match score was created. | Dimension |
| Application match score updated at | When the application match score was last updated. | Dimension |
| AI match score | AI match score on a scale of 0 to 100. | Dimension |
| Match strength override reason | Free-form override reason provided by the recruiter. | Dimension |
| Current match strength | Current match strength applied to the application (for example, strong, good, partial, or needs manual review). | Dimension |
| Current match strength code | Code indicating the current match strength (4 is 'Strong', 3 is 'Good', 2 is 'Partial', 1 is 'Limited', 0 is 'Needs Manual Review'). | Dimension |
| AI match strength | AI-assigned match strength (for example, strong, good, partial, or needs manual review). | Dimension |
| AI match strength code | Code indicating the AI-assigned match strength (4 is 'Strong', 3 is 'Good', 2 is 'Partial', 1 is 'Limited', 0 is 'Needs Manual Review'). | Dimension |
| Match strength override | Match strength override applied by the recruiter (for example, strong, good, partial, or needs manual review). | Dimension |
| Match strength override code | Code indicating the match strength override (4 is 'Strong', 3 is 'Good', 2 is 'Partial', 1 is 'Limited', 0 is 'Needs Manual Review'). | Dimension |
| Match strength override user full name | Match strength override user's full name. | Dimension |
| Match strength override user email address | Match strength override user's email address. | Dimension |
| Application scores | Number of application scores. | Measure |
| Rejected applications | Number of scored applications that were rejected. | Measure |
| Hired applications | Number of scored applications that resulted in a hire. | Measure |
| Active applications | Number of scored applications currently active in the pipeline. | Measure |
| Overridden match scores | Number of scored applications where the AI match score was overridden by a recruiter. | Measure |
| Strong match applications | Number of applications with a current 'Strong' match strength. | Measure |
| Good match applications | Number of applications with a current 'Good' match strength. | Measure |
| Partial match applications | Number of applications with a current 'Partial' match strength. | Measure |
| Limited match applications | Number of applications with a current 'Limited' match strength. | Measure |
| Needs manual review match applications | Number of applications with a current 'Needs Manual Review' match strength. | Measure |
| Average AI match score | Average AI match score on a scale of 0 to 100. | Measure |
Time-based fields
The following date and time fields appear across subjects and are commonly used for date-based filtering or trend analysis. Use these to filter or group by date — for example, offers sent by month or hires by quarter.
Application dates
- Application created at
- Application updated at
- Application rejected at
- Application last activity at
Application stage dates
- Application stage entered at / Application stage exited at
Approval flow dates
- Approval flow updated at
- Approval flow first request sent at
- Approval flow last group resolved atJob dates
- Job created at / Job updated at
- Job opened at / Job closed at
- Job first opening opened at / Job last opening opened at
- Job first applied at / Job last applied at
- Job last activity at
Candidate dates
- Candidate created at / Candidate updated at
Confirmed fraud signal dates
- Confirmed fraud signal created at
- Fraud signal created at / Fraud signal updated at
Fraud report dates
- Fraud report generated at
- Fraud report signals resolved at
Identity verification dates
- Identity verification requested at / Identity verification completed at
Interview dates
- Interview created at / Interview updated at
- Interview scheduled at
- Interview availability confirmed at
- Interview started at / Interview ended at
- Interview scorecard submitted at
Offer dates
- Offer created at / Offer updated at
- Offer sent at
- Offer resolved at
- Offer start at (proposed start date)
Opening dates
- Opening created at / Opening updated at
- Opening opened at / Opening closed at
- Opening target start at
- Target start at (hired candidate's expected start date)
Scorecard dates
- Scorecard submitted at
Talent Matching score dates
- Application match score created at / Application match score updated at
Filtering and grouping tips
- You can combine multiple filters using AND/OR logic.
- Grouping by fields like Department name or Office name helps break down metrics by team or location.
- Use Department level 1 name to group by top-level department, or use lower-level fields to drill deeper into sub-departments.
- Department name returns the lowest-level department only, while Department path returns the full hierarchy (for example, Engineering > Frontend > Web).
- Date fields can be grouped by day, week, month, quarter, or year.
- Measure fields (counts and averages) cannot be used as filters or group-by values — they appear in field selection only.
Custom fields
Your organization's custom fields are available in the data view builder, but they won't appear listed by their specific names. Instead, you can select Custom field name and Custom field value together, which will return all of your custom fields as rows in the results table, where each row represents one custom field and its value.
You can also add measure fields alongside your custom field columns (such as Applications or Active applications) to see counts broken down by each custom field.
Some standard Greenhouse fields, such as Employment Type, may also appear under custom fields in the builder. For more on the difference between system default fields and custom fields, see System default fields vs. custom fields.
Note: Full custom field support, including your organization's actual custom field names and values, is planned for a future update.