April 2026

We've moved! Release notes for April 2026 monthly and onward can be found at releases.eightfold.ai.

All previous release notes remain accessible on this site. For more information on the new release site, read the Eightfold Community post Introducing Our New Release Notes Experience: Streamlined, Useful, and Designed for You.

Jan 23, 2026

Filled Positions Tab (Formerly All Positions)

• Renaming & Scope Alignment: Renamed the tab to Filled Positions and updated the sheet title to Positions with hires to provide immediate clarity on data scope and prevent confusion between active and completed recruitment cycles.
  
• Refined Visual Logic: Updated the funnel and visuals to filter specifically on hire date (except for Offer Acceptance Rate), ensuring that metrics align with real-world hiring outcomes rather than general application activity.
  
• Embedded Candidate Details: Added an application-level data table (Candidate Name, Recruiter, Hiring Manager, and Stage), providing a seamless "drill-to-detail" experience that allows users to see the people behind the numbers without switching screens.
  
• Simplified Requisition Grouping: Introduced Position ID and ATS Job ID filters, making it easier for users to reconcile data in environments where multiple requisitions are tied to a single position.
  
• Improved Visual Hierarchy: Standardized all visual headers and moved "EF Missing Stage" to the bottom of the funnel to prioritize actionable data and ensure the most relevant stages are seen first.

Open Positions Tab

• Proactive Aging Controls: Replaced static date filters with a new 'Open for more than N days' control, shifting the user experience from manual filtering to proactive "at-risk" management of stalled requisitions.
  
• Advanced Drill-Down Capabilities: Added Position ID, ATS Job ID, and Evergreen flag filters to allow TA Leaders to instantly isolate high-volume roles from niche roles, ensuring more accurate reporting on specific hiring strategies.
  
• Contextual Data Integration: Added an application-level data table directly beside the funnel to provide immediate context on candidates and hiring managers, reducing the "time-to-insight" for active roles.
  
• Interactive "Point-and-Click" Exploration: Enabled interactive filtering so that clicking a funnel stage automatically updates the adjacent data table, significantly reducing the "click-fatigue" required to investigate specific stage bottlenecks.
  
• Streamlined Interface: Removed the Conversion table and updated the title to 'Open Positions' to reduce visual clutter and "scroll-fatigue," focusing the user’s attention on the most critical pipeline data.

Nov 14, 2025

Enhanced TA Leaders Dashboard

Key TA Metrics Tab

• The funnel was modified to represent all positions for which a hire was made, enabling the customer to understand the number of applicants needed to achieve a target number of hires.
  
• Color scaling changes were implemented on relevant visuals, improving the readability and impact of the data displayed.
  
• The ordering of the drill-down stages was corrected, and the ‘EF Missing Stage’ will now be shown at the bottom of the funnel, ensuring a logical stage progression.
  
• The titles of the 'Applications across interview stage trend' and 'Applications across interview stage by {{drop-down selection}} tables were updated to 'Applications & Conversions for positions with hires trend' and 'Applications & Conversions for positions with hires by {{drop-down selection}}', respectively, to clearly communicate the data represented.
  
• The header was changed from stage_group_display_name to 'Stage group' for the 'Applications & Conversions for positions with hires trend' and 'Applications & Conversions for positions with hires by {{drop-down selection}}’ tables, improving clarity and standardization.
  
• The tables were adjusted to represent all positions for which a hire was made, allowing the customer to understand the applicant-to-hire ratio.

Read TA Leaders Dashboard for more information.

Aug 27, 2025

Customizable Time to Fill

Align your hiring analytics with your specific workflows by setting a custom start date for the Time to Fill metric. A manual data backfill is necessary to apply this change. Read Time to Fill for more details.

July 30, 2025

AI interviewer usage and outcome

The AI Interviewer Analytics Dashboard, gives recruiters and talent acquisition leaders a centralized view to track AI Interviewer performance and ROI. It provides key metrics on usage, candidate engagement, and efficiency gains while helping teams monitor adoption rates and identify process bottlenecks. The dashboard demonstrates productivity benefits from automating initial screening interviews. Users need perm_manage_ai_interviewer_dashboard permission added to their corresponding role by their admin to access it.

Read AI Interviewer Dashboard to know about this dashboard in detail.

Diversity Analytics Dashboard for TA & TM

The diversity metrics from the standard TA & TM dashboards are being moved to a new dedicated TA & TM Diversity dashboard. This consolidation serves two key purposes: maintaining all TA diversity-related metrics in the TA Diversity dashboard and all TM diversity-related metrics in the TM Diversity dashboard and providing customers with greater control over who can access diversity data within their organization.

As part of this transition, the existing native Diversity dashboard (built within the Eightfold UI) will be deprecated and replaced by the new Diversity dashboard, which is built using QuickSight technology like other dashboards in the system. The new dashboard offers enhanced customization options through the Dashboard console, providing the same flexibility available with other QuickSight dashboards.

Both the removal of diversity metrics from TA & TM dashboards and the deprecation of the native Diversity dashboard will occur simultaneously when the new Diversity dashboard becomes available. If you have any concerns about that, please reach out to your Customer Success Manager.

The new dashboard requires specific setup steps to provision. Please refer to the document on how to provision (make available) this dashboard in the Admin Console for detailed instructions.

For specific metrics information, read the Talent Acquisition Diversity Dashboard for talent acquisition diversity metrics and the Talent Management Diversity Dashboard documentation for talent management diversity metrics. Read Migrated Diversity metrics to know how the visuals from the existing TA & TM dashboards to the new diversity dashboards.

Talent Management Diversity Dashboard:

Talent Acquisition Diversity Dashboard:

Jan 7, 2025

Career Site (2.0) dashboard

Candidate Portal

Sign ups used to include only the event for password sign up. Now new sign up methods are introduced (OTP & SSO) and we have updated the calculated field to include the relevant events

Previous logic

distinct_countIf({vs_cookie}, namespace="career_signup" AND in(event, ['candidate_signup_create_account']))

Updated logic

distinct_countIf({vs_cookie}, namespace="career_signup" AND (in(event, ['candidate_signup_create_account', 'candidate_signup_otp']) OR locate(event, 'candidate_signup_create_account_') > 0))

---

Sep 29, 2024

TM Feature Usage and Outcomes (2.0) dashboard

Overview - Careerhub Visits

Careerhub visits used to only include the events relevant to the modules included in the dashboard, now we’ve updated the logic to include all TM events irrespective of the modules available on the dashboard

All career hub visits are counted based on the number of events recorded, even in a single session can trigger multiple events leading the visit count to be very high. We updated the logic to dedupe the multiple events and now only one visit is recorded per user per day

Previous logic

sumIf({event_count},isNotNull({profile_activated_ts}) 
AND (event='home_view' 
OR {Project marketplace indicator}=1 
OR {Profile and goals indicator}=1 
OR {Networking indicator}=1 
OR {course marketplace indicator}=1 
OR {job marketplace indicator}=1 ))

Updated logic

distinct_countIf( concat(toString({profile_id}), toString({log_ts})), isNotNull({profile_activated_ts}) 
AND namespace = 'career_hub' /*AND event = 'home_view'*/)

Overview - Percent of returning users

Similar logic as the “Careerhub visits” metric has been implemented here as well to include all the relevant events irrespective of the modules available on the dashboard

Previous logic

distinct_countIf( 
concat({user_email}, toString(truncDate('MM',{log_ts}))), MM=1 ) / distinct_count(concat({user_email}, toString(truncDate('MM',{log_ts}))) 
)

Updated logic

distinct_countIf( 
concat(toString({profile_id}), toString(truncDate('MM',{log_ts}))), MM=1 ) / distinct_count(concat(toString({profile_id}), toString(truncDate('MM',{log_ts}))) 
)

Overview - Current Employees Using Careerhub

The logic for current employees using career hub has been updated to exclude employees whose profiles are not activated to exclude some edge cases

Previous logic

distinct_countIf({user_email},event='home_view')

Updated logic

distinct_countIf({profile_id}, isNotNull({profile_activated_ts}) 
AND namespace = 'career_hub' AND event = 'home_view')

Profile and Goals - Average Profile Completeness

Profile completeness for an employee whose profile is not activated yet can be greater than zero as the previously available employee information can be pulled into eightfold

Previously the profile completeness logic included all employees irrespective of the profile activation, now the logic has been modified to include only the employees whose profile has been activated

Previous logic

Average profile completeness = avg({profile_completeness})/100

Updated logic

Average profile completeness = avgIf(({profile_completeness})/100, isNotNull({profile_activated_ts}))

Profile and Goals - Average Goal Completeness

Goal completeness for an employee whose profile is not activated yet can be greater than zero as the previously available employee information can be pulled into eightfold

Previously the goal completeness logic included all employees irrespective of the profile activation, now the logic has been modified to include only the employees whose profile has been activated

Previous logic

avg({goal_completeness})/100

Updated logic

avgIf({goal_completeness}, isNotNull({profile_activated_ts}))/100

Job Marketplace - Job Views

All the job views are included irrespective of the same user viewing the job multiple times, the logic is updated to remove the dedupes i.e., only one view is considered for one unique user and a unique job

Previous logic

sumIf({event_count},event='position_view')

Updated logic

distinct_countIf(concat(toString({profile_id}), toString({position_id})), event='position_view')

Job Marketplace - Job Applications

The logic for job applications has been updated to remove dedupes in case the user is applying to the same job multiple times and the relevant events have been updated based on the latest instrumentation

Previous logic sumIf({event_count},event='position_apply_position')

Updated logic

distinct_countIf(concat(toString({profile_id}), toString({position_id})), event = 'apply_to_job')

Job Marketplace - Unique Applicants

The logic for unique applicants has been updated to reflect the relevant events based on the latest instrumentation

Previous logic

distinct_countIf({user_email},event='position_apply_position')

Updated logic

distinct_countIf({profile_id}, event = 'apply_to_job')

Project Marketplace - Project Marketplace Active Users

The logic for PMP active users has been updated to include additional events based on new workflows

Previous logic

distinct_countIf({user_email}, (event='view_project_details' or event='project_console_view') AND isNotNull({project_status}) AND {project_status} <> 'done_off_pmp')

Updated logic

distinct_countIf({profile_id}, in(event, ['view_project_details','project_console_view', 'profile_my_projects', 'project_view']) AND isNotNull({profile_activated_ts}))

Project Marketplace - Total Project Applications

The logic for PMP active users has been updated to include additional events based on new workflows

Previous logic

distinct_countIf(concat(toString({user_email}), '-', toString({project_id})), event="project_applied")

Updated logic

distinct_countIf(concat(toString({project_id}), toString({profile_id})), isNotNull({employee_id}) AND {employee_id} <> '' AND {stage_value} = 'applied')

Project Marketplace - Total Project Staffing

The logic for project staffing was previously based on staffing events, we have now moved to a project stage based formula making it more efficient

Previous logic

distinct_countIf(concat(toString({profile_id}), '-', toString({project_id})), event="project_invite_accepted" or event="project_assigned" or event="project_teammember_added" or event="project_manager_added" or event="confirm_create_project")

Updated logic

distinct_countIf(concat(toString({project_id}), toString({profile_id})), isNotNull({employee_id}) AND {employee_id} <> '' AND {stage_value} = 'hired' AND {stage_rank} = 1)

Project Marketplace - Unique Users Who Applied For a Project

The logic for project applicants was previously based on staffing events, we have now moved to a project stage based formula making it more efficient

Previous logic

distinct_countIf({user_email},event="project_applied")

Updated logic

distinct_countIf(concat(toString({project_id}), toString({profile_id})), isNotNull({employee_id}) AND {employee_id} <> '' AND {stage_value} = 'applied')

Recruitment Effectiveness (2.0) Dashboard

Tabular View - Adding ats_job_id

We’ve added an additional column “ats_job_id” to the raw data visuals on the dashboard to enable users to be able to compare the with the ATS data if needed

Open positions - New Tabular Views

To ensure a smooth transition from Talent Analytics Dashboard (deprecated) to Recruitment effectiveness (2.0) dashboard we’ve added two new tabular views

• Recruitment activities for open positions by recruiter

* Recruitment activities for open positions by position ID

All positions

• The closed positions tab has been changed to “All positions” now. Thais tab will give an overview of all positions instead of closed positions
  
• Recruitment funnel and Between stage conversion rates
  
  • Recruitment funnel now provides the customers with the stage groups that they defined instead of the the standard stage groups from eight fold
    
  • Due to the introduction of custom stage group mapping, the average days between the stages metric is no longer possible to calculate, but this can be extracted via the Data hub, a curated query has been added in the Eightfold Curated Queries section with the name “Report on Days to advance for dynamic stage groups”

TA Feature Usage and Outcomes (2.0) Dashboard

Sourcing - Chrome Extension Events update

Chrome extension sourcing is previously considered the “extension_click” event to track the sourcing, which tracked any and all clicks on the chrome extension. We’ve updated the logic to include only the sourcing activity, leaving out the additional clicks

Previous logic

event = 'extension_click'

Updated logic

event = 'add_to_pipeline' and source = 'extension'

Community - Overview

The overview section of the community tab has been updated to include the current community stages so that you can have a more accurate view of the community pipeline

Community - Candidates outreached

The events for candidate outreach has been updated to reflect the right candidate outreach activity

Previous logic

distinct_countIf(concat(toString({profile_id}),toString(title)), event='contact' OR event='sms_send_success' OR event='whatsapp_send')

Updated logic

distinct_countIf(concat(toString({profile_id}),toString(title)), event='contact' OR event='sms_send_success' OR event='whatsapp_send_success')

Engagement - Days from Contact to Response, Submission and Hire

The old formula for “Days between Contact & Hired” was having duplication issue, we modified the logic to dedupe the entries by filtering for only the first contact record before the metric computation

Days taken to respond

Previous logic

dateDiff({First Contact Date},{First Reply Date},'DD')

Updated logic

avg(dateDiff({First Contact Date},{First Reply Date},'DD'), [{active_user_id}, {profile_id}, {position_id}])

Days between Contact and Application submission

Previous logic

dateDiff({First Contact Date},{min_application_ts},'DD')

Updated logic

dateDiff({First Contact Date},{First application date},'DD')

First application date = minOver({min_application_ts}, [{active_user_id}, {profile_id}, {position_id}], PRE_AGG)

// Added {First Contact Indicator} in the filter section

Days between Contact & Hired

Previous logic

dateDiff({First Contact Date},{min_hired_date},'DD')

Updated logic

dateDiff({First Contact Date},{First hired date},'DD')

First hired date:
minOver({min_hired_date}, [{active_user_id}, {profile_id}, {position_id}], PRE_AGG)

// Added {First Contact Indicator} in the filter section

January 31, 2024

Referral Activity Report

A drill down feature has been included in the Referral Activity Report.

To get this change in your Referral Activity dashboard, navigate to Admin Console > Datawarehouse & Dashboards > Provision Dashboards.

TA Leaders Dashboard

Stage group mapping

• A Stage Mapping tab has been included in the TA Leader Dashboard.
• A drill down feature has been added to the recruitment funnels. Users can also move to the Stage Mapping tab by clicking from the funnel chart Stage group to stage mapping.

‘Director + ‘ and ‘Director below’ related metrics have been removed

Highlights tab
• removed ‘% ‘Director +' Positions with 1+ Diverse Candidate advanced to Phonescreen’ metric
• removed ‘% Below Director US requisitions with 1+ diverse candidates advanced to Phonescreen’ metric

Diversity metrics tab

• removed ‘% ‘Director +' Positions with 1+ Diverse Candidate advanced to Phonescreen’ metric
• removed ‘% Below Director US requisitions with 1+ diverse candidates advanced to Phonescreen’ metric
• removed the whole 'Director Slate Aspiration’ section

Removed all filter controls on ‘Position status’

Recruitment Effectiveness Dashboard

Stage group mapping

• To make it easier to see how different stages in the recruitment process relate to each other, Eightfold has added a new tab called 'Stage Mapping' to the Recruitment Effectiveness Dashboard. You can find this tab by clicking on it from either the 'Open Positions' or 'Filled Positions' tabs.
• Drill down feature has been added to both the Recruitment funnels in Filled positions and Open positions tab.

Position status

• Previously, we used ‘position_status’ as an identifier to determine whether a position was open or closed. To improve accuracy, we will now use the ‘is_open’ flag from the positions table. This adjustment should address any inconsistencies on the dashboard.
  • If ‘is_open’ is true - open position
  • If ‘is_open’ is false - closed position
• ‘Filed positions’ tab is changed to ‘Closed positions’ based on the logic above. ‘Closed positions’ would include filled positions as well as positions that have never had a hire but closed.
  • ‘Total filled positions in selected time period’ is changed to ‘total closed positions | all-time since 2022’
• ‘Open positions’ tab: ‘Open positions’ KPI is changed to ‘Currently open positions’ and date range filter is not applicable

Other changes

• Visualizations relying on ‘position_closed_at’ timestamp have been removed.
• All 'offer decline' metrics have been removed.

January 4, 2024

TA Leaders Dashboard

Improvement

Added Reporting year filter in the controls section of Highlights tab.

December 20, 2023

Project Marketplace Dashboard

Improvement

• Added ‘Project team members removed by project manager’ metric to the ‘Project Summary’ table.
• Removed ‘Total project staffing’ metric from the ‘Project Summary’ table.

December 13, 2023

TA Leader Dashboard & Source Analytics Dashboard

Improvement

• Changed underlying datasets for PCS related metrics to improve dashboard loading speed and to further filter out bot and test traffic
  • Old datasets name:
    • customername ta_leaders_career_site_metrics
    • customername source_analytics_career_site_metrics
  • New dataset name:
    • customername career_site_metrics
  • This new dataset is used across TA Leader Dashboard, Source Analytics Dashboard and Career Site Dashboard V2
• Added ‘Time Series Graphs Aggregation Level’ filter control on the Source Analytics Dashboard to enable users to choose and view time series chart by week/month/quarter/year.

December 4, 2023

Calibration Dashboard

Note: If the below change is not visible within the Dashboard, navigate to Admin Console > Data warehouse & Dashboards > Calibration Dashboard and click the ‘edit icon’ > Update.

Summary:

• Added Calibration% column to the dataset of the Calibration Dashboard
• Added Calibration% related views
• Updated Notes section based on the most recent definitions of the calibration status

Visuals added:

View 1: Position distribution across the Calibration%
In this graph, 43% of the positions have 100% calibration (all five components have been filled).

View 2: Positions across Calibration% by position creation
Considering Aug 2023, 50 positions were created and 17 of them have 100% calibration.

View 3
This view demonstrates how the filter on top of the next two visuals helps a user in viewing the positions distribution across calibration% by different position attributes.

View 4
Added Calibration% and the five components which determine the Calibration% to this table.

Updated notes section
The notes section is updated based on the most recent and accurate definitions.

November 15, 2023

Survey Dashboard

Candidate interview experience survey tab: to exclude repeat survey submission responses on the same position_id, NPS related metrics are updated to use the ‘first’ survey response only if the candidate submitted multiple survey responses to the survey associated with the same position id. For example:

• Candidate submitted the first response and rated 4 stars to ‘candidate interview experience survey’ on interview for position 123456
• Candidate then submitted the second response and rated 5 stars to ‘candidate interview experience survey’ on interview for position 123456
• Only the first response (rating 4 stars) is used in NPS calculated

The ‘non first’ responses are also not shown in the ‘raw data’ table.

However, if the survey link does not have ‘pids’ parameter configured, there will be no position_id associated with the survey, and the above changes do not apply.

November 02, 2023

Project Marketplace Dashboard

Improvement:

• Added ‘job function’ in ‘Breakdown variable’ filter control, so that dashboard users can now see metrics break down by ‘job function’
• Added ‘project total hours (commitment)’ to the ‘Project Summary’ table
• Added ‘project location’ to the ‘Project Summary’ table
• Added ‘# of project managers’ and ‘# of project team members’ to the ‘Project Summary’ table
• Removed ‘Project managers added directly’ and ‘Project team members added directly’ from the ‘Project Summary’ table these 2 metrics caused confusion and are not useful.

October 23, 2023

Succession Planning Dashboard

Improvement: Filter out employees who do not have a ‘business unit’ as a mechanism to filter out non-employee role profiles (non-employee role profiles, such as HRBP, would not have a ‘business unit’ associated with them)

October 9, 2023

TA Usage and Adoption Dashboard

Bug fix: Three events/actions (spam, bounce, tm_home_view) will be excluded from this dashboard since they are not events which are associated with Talent Acquisition. They were missed from being filtered from this dashboard.

Event definitions:

• Spam - This event is fired when contact email sent from EF is marked as spam by the recipient.
• Bounce - This event is fired when the contact email sent from Eightfold bounced.
• tm_home_view - This event is fired when a user views the TM Career Hub Home page.

Impact of event exclusion

• Spam, bounce: The number of users and positions with activity is expected to decrease by a smaller magnitude for few customers. In order to understand the magnitude of decrease, customers can use the user_analytics table (or the dataset used in this dashboard) and count (distinct user_id) where event IN (‘spam’,’bounce’) using SQL or within the dashboard authoring console or contact your Eightfold POC to get this information.

• tm_home_view: Only customers who are using our TA & TM product will be affected by this change. The active user count from April 25th (or the day when you started TM platform) might be affected in your TA usage dashboard. In order to understand the magnitude of decrease in users, you can use the user_analytics table (or the dataset used in this dashboard) and count (distinct user_id) where event IN (‘tm_home_view’) using SQL or within the dashboard authoring console or contact your Eightfold POC to get this information.

Calculated field modified to exclude these events:

Calculated field	Old formula	New formula
TA Event Filter	ifelse( (locate(event,'project')>0 OR locate(event,'employee')>0 OR event = 'click_apply_to_job' OR event = 'apply_to_job' OR event = 'apply_to_job_external' OR event = 'candidate_finish_onboarding' OR event = 'update_profile' OR locate(event, 'ijp')>0 OR locate(event, 'tm_')>0 OR event = 'use_career_planner' OR locate(event, 'career')>0 OR locate(event, 'course')>0), 'No','Yes')	ifelse( (locate(event,'project')>0 OR locate(event,'employee')>0 OR event = 'click_apply_to_job' OR event = 'apply_to_job' OR event = 'apply_to_job_external' OR event = 'candidate_finish_onboarding' OR event = 'update_profile' OR locate(event, 'ijp')>0 OR locate(event, 'tm_')>0 OR event = 'use_career_planner' OR locate(event, 'career')>0 OR locate(event, 'course')>0 OR locate(event, 'tm_home_view')>0 OR locate(event, 'spam')>0 OR locate(event, 'bounce')>0), 'No','Yes')

Note: This change will be pushed only to the standard dashboard. Kindly make sure you include the change in your custom dashboards too.

October 5, 2023

Source Analytics Dashboard - add ‘recruiter’ and ‘hiring manager’ to raw data. ‘Recruiter’ (email) and ‘hiring manager’ (email) are added to the ‘All source data by profile and application (last-touch attribution)’ table and ‘All source data by profile and application (multi-touch attribution)’ table on the ‘Raw data tab’.

October 2, 2023

Source Analytics Dashboard - calculated field update. ‘Source Group’ calculated field for the last-touch attribution model has been updated: when ‘source_type’ (raw data) is ‘job board’/’jobs2web’/’applied’/etc, The dashboard will show ‘source_name’ for next level of details in source.

Previously, only ‘source_type’ is shown and ‘source_name’ is not shown in those scenarios.

September 27, 2023

Source Analytics Dashboard - calculated field update. ‘Employee referral’ uploading candidate resumes is now removed from ‘Recruiter (importing applications)’ source group on the ‘(Recruiter) Sourcing Deep Dive’ tab.

Previously, ‘Recruiter (importing applications)’ number included ‘Employee referral’ uploading candidate resumes.

August 8, 2023

Career Site Dashboard - calculated fields update. Previous version of Career Site Dashboard split up ‘logged-out’ and ‘logged-in’ metrics in different tabs (first tab ‘Career Site Analytics’ and last tab ‘Logged-in PCS anALYTICS’). To better enable PCS customers who require candidates to log in before submitting the application, we now include ‘logged-in’ metrics on the first tab ‘Career Site Analytics’ as well.

• This change only impacts the PCS customers who require candidates to log in before submitting the application.
• No UI change.
• Several metrics now include ‘logged-in’ numbers:
  • # of visitors
  • # of career site applicants
  • # of application starts
  • # of application submits
  • Visitor to applicant conversion
  • Application completion rate
  • # of jobs viewed per visitor
• The change is in the calculated fields below:
  • ‘Is PCS’:
    • Previous: ifelse(namespace='smartapply', 1, 0)
    • Current: ifelse(namespace='smartapply' or namespace='career_hub_candidate', 1, 0)
  • ‘Visitors’:
    • Previous: distinct_countIf({vs_cookie}, Event = 'Visit)
    • Current: distinct_countIf({vs_cookie}, Event = 'Visit' or event = 'position_view')
  • ‘Career site jobs viewed’:
    • Previous: distinct_countIf(concat({vs_cookie}, toString({position_id})), event = 'api_get_job')
    • Current: distinct_countIf(concat({vs_cookie}, toString({position_id})), event = 'api_get_job' or event = 'position_view')

July 28

TA Leaders Dashboard - PCS survey NPS (net promoter score) calculation update. The same update in the Survey Dashboard on June 20, 2023 was applied to the TA Leaders Dashboard, PCS NPS related metrics.

No UI changes.

July 20, 2023

TM Usage dashboard update. Previously, fields on the People tab of the TM Usage dashboard were displaying inaccurate numbers due to a filter. To address this issue, the underlying logic has been updated for all fields on the People tab of the dashboard. There are no UI changes.

June 20, 2023

Survey Dashboard - PCS survey NPS (net promoter score) calculation update. For each PCS post apply survey, survey takers can change their rating of their application experience multiple times after submitting the initial answer (for example, they can select 5 stars, and then change to 4 stars, and then change to 3 stars). Technically, only the last rating submitted should be considered in the NPS calculation.

Previously, PCS post apply survey NPS calculation did not take into account multiple ratings submission of the same applicant (identified by vs_cookie) of the application to the same position (identified by the position_id), and would treat each rating submission as a different survey submission.

Previous calculation in Quicksight Survey Dashboard (nested calculated fields):

{Candidate Experience Score (NPS)} = {% Promoters} - {% Detractors}

{% Promoters}  = distinct_countIf({unique_id}, {is_promoter}=1 AND event = 'submit_survey') / {Survey participants}

{% Detractors} = distinct_countIf({unique_id}, {is_promoter}=-1 AND event = 'submit_survey' AND isNotNull({is last rating})) / {Survey participants}

{Survey participants} = distinct_countIf({unique_id}, isNotNull({is_promoter}) AND event = 'submit_survey')

After the change only the last rating submitted per application per application is used in the PCS post apply survey NPS calculation.

Current calculation in Quicksight Survey Dashboard (nested calculated fields):

{Candidate Experience Score - pcs survey} = {% Promoters - pcs survey} - {% Detractors - pcs survey}

{% Promoters - pcs survey}  = distinct_countIf(concat({vs_cookie}, toString({position_id})), {is_promoter}=1 AND isNotNull({is last rating})) / {Surveys taken - pcs_apply_thank_you_page}

{% Detractors - pcs survey} = distinct_countIf(concat({vs_cookie}, toString({position_id})), {is_promoter}=-1 AND isNotNull({is last rating})) / {Surveys taken - pcs_apply_thank_you_page}

{Surveys taken - pcs_apply_thank_you_page} = distinct_countIf(concat({vs_cookie}, toString({position_id})),
{embedding_id} = 'pcs_apply_thank_you_page' AND event = 'submit_survey')

{is last rating} = ifelse({t_create}=maxOver({t_create},[{embedding_id}, {vs_cookie}, {question_template_id}, {position_id}], PRE_AGG),rating, NULL)

The key change is adding {is last rating} calculated field, which ranks the rating submission order per applicant per application, and only includes the last one for NPS calculation.

No UI changes.