Purpose of this document

Note: To maintain optimal dashboard performance, data displayed is limited to 2023 and onward. Information from before 2023 is not available on the dashboards.

This article introduces users to the Eightfold (EF) Talent Acquisition (TA) Career Site Dashboard, including a general overview of the dashboard, information about each dashboard feature, and benefits of using the dashboard.

Audience

This article is directed toward the intended users of the dashboard, including the head of talent acquisition, talent ops (of career site), and recruitment marketing managers.

Background: Dashboard purpose

The Career Site Dashboard is designed to provide data and insights on:

• Eightfold Personal Career Site (‘PCS’) outcomes and values
  • Applications and hires from PCS
  • Diversity driven by PCS

• PCS conversion efficiency

  • Traffic to PCS

  • Visitor converting into applicants

  • Visitor conversion funnel

• PCS feature usage and aided conversions

  • PCS job search functions

  • PCS job alert

  • Candidate portal (logged-in PCS)

• Traffic and conversions by source to PCS

Accessing the dashboard

To access the dashboard, sign in to your Eightfold account, open the Insights tab, and select Career Site Analytics.

For first-time users

If you are a first-time user of the Career Site Dashboard, you will need to provision. Here’s how to provision the dashboard:

1. After signing in, go to More > Admin Console > Data Warehouse & Dashboards > Provision Dashboards.
2. In the Career Site Analytics row, select the Actions icon.
3. Select Create and then Submit. Once you’ve provisioned the dashboard, it will appear as an option in the Dashboards tab.

On the other hand, if you have used Career Site Dashboard before, but not the V2.0 version (this is a documentation on Career Site Dashboard V2.0, and the older version will be phased out), you also need to provision it.

Tabs overview

• PCS performance overview: Top level outcomes driven by PCS, including hires from PCS, gender diversity of PCS hires, and hires quality (measured by match score) on PCS.
• Key conversion metrics: Conversions of the core PCS funnel: visit (job view) - application start - application submit. This tab provides activity and user numbers at each step of the funnel, and the conversion rates throughout the funnel. It also lets dashboard users slice and dice the conversion metrics by different dimensions: locations, languages, devices, position business units/job functions, etc.
• Traffic sources: Visitors and applicants by PCS traffic source. This tab shows which traffic source (e.g. different job boards) delivers the most visitors and application conversions.
• Job search: This tab provides usage and conversion insights on the key job search functions on PCS: AI match (from resume uploads), keyword search, location search, chatbot and map.
• Re-engagement (job alerts): This tab provides usage and conversion insights on a re-engagement feature: job alerts. It shows how many users are receiving job alerts, and the visits and conversions driven by job alerts.
• Candidate portal (logged-in PCS): For customers who have enabled Candidate Portal, this tab reports on the sigp-ups, usage and application conversions in Candidate Portal.
• Glossary : This is a list of terminologies used on the Career Site Dashboard.

Filter Controls

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

Filter controls are located at the top of the dashboard. Filter controls can be different on different tabs.

The following filter controls are applied to the Career Site Dashboard:

Application Date (from - to)

Application date is the date on which the application was submitted. ‘Application date From - To’ filter controls the date range of all charts on the tab.

Activity Date (from - to)

Activity date is the date on which the activity happened (‘activities’ include visits, job search, submit application, etc.). ‘Activity date From - To’ filter controls the date range of all charts on the tab.

Time Series Graph Aggregation Level

This filter control applies to the time series charts and has 4 options ‘Week’, ‘Month’, ‘Quarter’, and ‘Year’ (the default option is ‘Month’). The time series charts will aggregate by week/month/quarter/year based on the selection of this filter control. For example, if ‘Month’ is selected, the following chart will show ‘Unique visitors & unique positions viewed by month’:

If ‘Quarter’ is selected, the same chart will show ‘Unique visitors & unique positions viewed by quarter’:

Table Breakdown Variable

For some tables on the dashboard, the aggregation variable (the first column in the table) can be changed based on the ‘Table Breakdown Variable’ filter control selection. For example, the following table is showing ‘job views by user location country’ if ‘user location country’ is selected:

The same table will show ‘job views by device’ if ‘device’ is selected.

Position Location Country

Position location country refers to the country associated with the position. This could be different from the country location of the applicant (for example, if an applicant living in the US applied for a position in Canada, the position location country is Canada).

This filter control will filter for the positions in the selected country.

Business Unit

Job function refers to the business units associated with the position: sales, engineering, finance, etc. The values vary for different companies.

This filter control will filter for the positions of the selected business units.

Job function

Job function refers to the job function associated with the position: account management, customer service, etc. The values vary for different companies.

This filter control will filter for the positions of the selected job functions.

ATS Job ID

This refers to the job IDs in the ATS.

This filter control will filter for the applications or user activities of the selected ATS Job IDs.

Logged-out Vs Logged-in PCS (if applicable)

If the customer has enabled Candidate Portal (logged-in PCS), there will be PCS user activities in 2 places: logged-out PCS and logged-in PCS. This filter control will filter for either one of the places, or both.

User Location Country

User location country refers to the country associated with the user’s location. This could be different from the country location of the position (for example, if an applicant living in the US applied for a position in Canada, the user location country is US).

This filter control will filter for the users in the selected country.

User location country could be ‘unknown’ if user disabled location tracking on their device.

Device

The device on which the user visited PCS: mobile, desktop or tablet.

Operation System

The operation system of the device on which the user visited PCS; for example, iOS, windows, linux.

User Portal Language

The portal language that the user used on their device; for example, English, Spanish, etc.

Microsite (if applicable)

If the customer has enabled microsite, this filter control will filter for user activities on the microsite selected.

UTM Source Group

This filter control is based on the utm_source of PCS traffic. The utm_sources are grouped into several groups. The filter control will filter for traffic and conversions from the utm_source selected.

UTM Campaign

This filter control is based on the utm_campaign of PCS traffic. The filter control will filter for traffic and conversions from the utm_campaign selected.

Metrics and dimensions calculation

Career site hires

• Description: number of candidates hired; their applications were from Career Site.
  • Date range on this metric is based on the application date of the hired application
  • An application is considered ‘hired’ when it is in the ‘hired’ stage group.

• Used in tab(s):
  
  • PCS Performance Overview
• Formula in Quicksight calculation:
  • distinct_countIf({application_id}, {stage_group}='hired' AND {Source Channel} = 'Career site & job boards')
• Dataset(s):

%hires from career site

• Description: among all hires, the percentage of hires from Career Site.
• Used in tab(s):
  • PCS Performance Overview

• Formula in Quicksight calculation:
  • {Career site hires} / distinct_countIf({application_id}, {stage_group}='hired')
• Dataset(s):
  • application_source_lasttouch

%female hires

• Description: among all Career Site hires, the percentage of hires that are female (showing Eightfold AI inferred gender if candidate self-reported gender is not available).
  • Gender information could be blank for some applications.

• Used in tab(s):
  
  • PCS Performance Overview
• Formula in Quicksight calculation:
  • distinct_countIf({application_id},{application_inferred_gender}='female' AND {stage_group}='hired')/distinct_countIf({application_id}, {stage_group}='hired')
  • where Source Channel = ‘Career site & job boards’
• Dataset(s):
  • application_source_lasttouch

Avg match score of hires

• Description: average match score of Career Site hires. Match score is generated by Eightfold AI
• Used in tab(s):
  • PCS Performance Overview

• Formula in Quicksight calculation:
  • avgIf({application_match_score}, {stage_group}='hired') where Source Channel = ‘Career site & job boards’
• Dataset(s):
  • application_source_lasttouch

Visitors

• Description: number of unique visitors on the career site in the selected time range (based on vs_cookie, each vs_cookie id is identified as one visitor). This includes both logged-out and logged-in visitors.
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, (namespace = 'smartapply' AND event = 'api_get_job') OR (namespace = 'career_hub_candidate' AND event = 'position_view')) with filters IsValidActivity: {response_code} <400 OR {response_code}>599 Is PCS (logged-out & logged-in): namespace='smartapply' OR namespace='career_hub_candidate' utm_source is NULL for logged-out PCS

Dataset(s):

Applicants

• Description: number of unique visitors who submitted at least 1 application on the Career Site (PCS). This includes both logged-out and logged-in applicants.
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event = 'apply_to_job')
  • with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Visitor to applicant conversion % (on career site)

• Description: Applicants / visitors
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • Applicants / Visitors
  • with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Applications started

• Description: apply clicks; number of applications started on Career Site (PCS) ('application start' is the click on 'Apply' button of a job). This includes both logged-out and logged-in applications started.
  • If the same applicant (identified by vs_cookie) clicked ‘Apply’ more than once on the same position, it will be counted as only 1 application started because they are duplicated apply clicks.

• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)
• Formula in Quicksight calculation:
  • distinct_countIf(concat({vs_cookie}, toString({position_id})), namespace = 'smartapply' AND event = 'click_apply_to_job') + distinct_countIf(concat({user_email},toString({position_id})), namespace='career_hub_candidate' AND event='click_apply_to_job') with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Applications submitted (on career site)

• Description: number of applications submitted on Career Site (PCS). This includes both logged-out and logged-in applications submitted.
  • If the same applicant (identified by vs_cookie) submitted more than 1 application for the same position, it will be counted as only 1 application because they are duplicated positions.

• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)
• Formula in Quicksight calculation:
  • distinct_countIf(concat({vs_cookie}, toString({position_id})), namespace='smartapply' AND event = 'apply_to_job') + distinct_countIf(concat({user_email},toString({position_id})), namespace='career_hub_candidate' AND event='apply_to_job') with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Application completion % (on career site)

• Description: applications submitted / applications started. This metric measures the completion rate of the application started.
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • {Applications submitted} / {Applications started}
  • with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

New vs returning visitors

• Description: among all visitors, new visitors are those who have never been on PCS (first time visitor), returning visitors are those who have been on PCS before.
• Used in tab(s):
  • Key Conversion Metrics

• Formula in Quicksight calculation:
  • ifelse(dateDiff({Logged-out & in PCS first visit date},{server_log_ts},'DD')>=1, 'returning visitors', 'first time visitors')
  • with the same filters applied to 'Visitors'
• Dataset(s):

Visitors w/ application start

• Description: the unique number of visitors who had at least one apply click (application start). This includes both logged-out and logged-in visitors.
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event='click_apply_to_job') with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

%visitors w/ application start

• Description: among all visitors, the percentage of visitors who had at least one apply click (application start)
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • {Visitors w/ application start} / Visitors
  • with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Job views

• Description: number of job views on PCS. If a visitor has viewed the same job post multiple times, it is counted as 1 job view. This includes both logged-out and logged-in job views.
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf(concat({vs_cookie}, toString({position_id})), event = 'api_get_job' AND namespace = 'smartapply') + distinct_countIf(concat({user_email}, toString({position_id})), event = 'position_view' AND namespace='career_hub_candidate') with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

Job view to application start conversion

• Description: applications start / job views
• Used in tab(s):
  • Key Conversion Metrics
  • Traffic Sources
  • Re-engagement (Job Alerts)
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • {Applications started} / {Job views}
  • with the same filters applied to 'Visitors'
• Dataset(s):
  • source_analytics_career_site_metrics

UTM source (group)

• Description: the source from which the visitor landed on the career site.
  • Source to career site is captured by tracking either the UTM parameter, src parameter, or referrer related to the visits on the career site.
  • When more than one parameter is captured, UTM parameter takes precedence, followed by src parameter.
  • source variations are grouped and renamed into one
    • For example, 'linkedin' and 'lnkd' are grouped into 'LinkedIn'.

  • Refer PCS source tracking for more details.
• Used in tab(s):
  • Application Sources Analytics
• Formula in Quicksight calculation: N/A
• Dataset(s):

UTM campaign

• Description: the utm_campaign from which the visitor landed on Career Site. This is captured by the ‘utm_campaign’ parameter in the URL. Read PCS source tracking for details.
• Used in tab(s):
  • Application Sources Analytics

• Formula in Quicksight calculation: N/A
• Dataset(s):

% visitors uploaded resume for AI match

• Description: among all visitors, the percentage of visitors who upload resumes for job match.
  • This excludes the resume upload in apply form or in the ‘upload resume’ modal after visitor clicks ‘Apply’, because those uploads are not for job match.

• Used in tab(s):
  • Job Search
• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event = 'api_post_resume' AND ({resume_upload_method_raw} = 'jd-match' OR {resume_upload_method_raw} = 'personalization-bar' OR {resume_upload_method_raw} = 'profile-dropdown')) / Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

% visitors using keyword search

• Description: among all visitors, the percentage of visitors who used keyword search to search for jobs.
• Used in tab(s):
  • Job Search

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event = 'api_get_jobs' and isNotNull(query) and query <> '*') / Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

% visitors using location search

• Description: among all visitors, the percentage of visitors who used keyword search to search for jobs.
• Used in tab(s):
  • Job Search

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event = 'api_get_jobs' and isNotNull({query_location_search}) and {query_location_search} <> '*') / Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

% visitors using chatbot

• Description: among all visitors, the percentage of visitors who used chatbot.
  • Data will be null if chatbot is not enabled on PCS.

• Used in tab(s):
  • Job Search
• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, event = 'api_chat') / Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

% visitors using map

• Description: among all visitors, the percentage of visitors who used PCS Map.
  • Data will be null if map is not enabled on PCS.
  • There are 4 actions related to PCS Map usage:
    • ‘Hide Map’ click
    • ‘Show Map’ click
    • ‘Search this area’ click
    • Map pin click

  
  
• Used in tab(s):
  • Job Search
• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, locate(event, 'map') > 0) / Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

Job alerts sent

• Description: number of job alerts sent to recipients, including all job alert types.
  • No data if job alert feature is not enabled.
  • Job alert types:
    • in terms of where the job alert was set up:
      • logged-in job alerts
      • logged-out job alerts

    • in terms of job alert content
      
      
      
      • AI profile based job alerts
        
        
        
        • Job recommendations are based on candidate profile.
        
        
        
        
      • Saved search job alerts
        
        
        
        • Job recommendations are based on the search keyword that the candidate set up.
    
    
• Used in tab(s):
  • Re-engagement (Job Alerts)
• Formula in Quicksight calculation:
  • distinct_countIf({message_id}, namespace = 'notifications' AND locate(event, 'send_') = 1 AND locate(event, 'notification_email') > 1)
• Dataset(s):
  • source_analytics_career_site_metrics

% visitors from job alerts

• Description: among all visitors, the percentage of visitors clicked from a job alert email.
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, ((namespace = 'smartapply' AND event = 'api_get_job') OR (namespace = 'career_hub_candidate' AND event = 'position_view')) AND locate({utm_source}, '_notification') >0)/Visitors
• Dataset(s):
  • source_analytics_career_site_metrics

Job Alert Click Through Rate

• Description: visitors from job alerts / job alerts sent
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • distinct_countIf(concat(toString({user_email}), substring(tostring({t_create}),1,10)), namespace='career_hub_candidate' AND locate({utm_source}, 'notification') > 1) / {Job Alerts Sent}
• Dataset(s):
  • source_analytics_career_site_metrics

Unique Visitors From Job Alerts

• Description: number of visitors who clicked from a job alert email.
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace = 'career_hub_candidate')
• Dataset(s):
  • source_analytics_career_site_metrics

Unique Applicants From Job Alerts

• Description: number of visitors who clicked from a job alert email.
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace='career_hub_candidate' AND event='apply_to_job')
• Dataset(s):
  • source_analytics_career_site_metrics

Visitor to Applicant Conversion from Job Alerts

• Description: visitor to applicant conversion in visits from a job alert email.
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • {Unique Applicants From Job Alerts} / {Job viewers from job alerts}
• Dataset(s):
  • source_analytics_career_site_metrics

Job alerts set up

• Description: The number of job alerts set up. The calculation method varies by job alert type:
  • Logged-in AI profile based job alert: not applicable because this kind of job alert is automatically set up.
  • Logged-out AI profile based job alert: number of users who set up job alerts in logged-out PCS.
  • Saved search job alerts: number of keyword based job alerts set up.

• Used in tab(s):
  • Re-engagement (Job Alerts)
• Formula in Quicksight calculation:
  • {Unique Applicants From Job Alerts} / {Job viewers from job alerts}
• Dataset(s):
  • source_analytics_career_site_metrics

Job Alert Unsubscribe Rate

• Description: in the selected time frame, the percentage of job alert recipients who unsubscribed.
• Used in tab(s):
  • Re-engagement (Job Alerts)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace='notifications' AND in(event, ['unsubscribed_position_notification_email', 'unsubscribed_saved_search_notification_email'])) / {Unique Job Alert Recipients}
• Dataset(s):
  • source_analytics_career_site_metrics

Candidate Portal sign ups

• Description: number of users who signed up for Candidate Portal (who created an account in the candidate portal).
• Used in tab(s):
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({vs_cookie}, namespace="career_signup" AND event = "candidate_signup_create_account")
• Dataset(s):
  • source_analytics_career_site_metrics

Logged-in visitors

• Description: users who logged into the candidate portal.
• Used in tab(s):
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace='career_hub_candidate')
• Dataset(s):
  • source_analytics_career_site_metrics

Candidate Portal % returning visitors

• Description: among all users who logged into the candidate portal, the percentage of visitors who have logged in before (not first time visitors).
• Used in tab(s):
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace = 'career_hub_candidate' AND dateDiff({Candidate Portal first active date},{server_log_ts},'DD')>=1) / {Logged-in visitors
• Dataset(s):
  • source_analytics_career_site_metrics

Logged-in applicants

• Description: users who submitted applications within the candidate portal.
• Used in tab(s):
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, event='apply_to_job' AND namespace='career_hub_candidate')
• Dataset(s):
  • source_analytics_career_site_metrics

Candidate Portal % returning applicants

• Description: among all logged-in applicants, the percentage of applicants who have applied in logged-in before (not first time logged-in applicants).
• Used in tab(s):
  • Candidate Portal (Logged-in PCS)

• Formula in Quicksight calculation:
  • distinct_countIf({user_email}, namespace = 'career_hub_candidate' AND event = 'apply_to_job' AND dateDiff({Candidate Portal first application date},{server_log_ts},'DD')>=1)/ {Candidate Portal applicants}
• Dataset(s):
  • source_analytics_career_site_metrics

Frequently asked questions

What is the difference between the ‘unique visitor’ funnel and the ‘activities’ funnel?

Although having the same steps, the ‘unique visitors’ funnel counts the number of unique users in each step, while the ‘activities’ funnel counts the number of activities (‘events’) in each step.

Usually the ‘activities’ funnel will have higher numbers at each step, because each user can view multiple job posts and apply to multiple positions.

How to use the ‘Candidate Portal type’ filter on the ‘Candidate Portal’ tab? / If I have ‘logged-in mandatory’, how do I see funnel metrics from logged-out to logged-in?

Some customers have ‘log in is optional’ - candidates can have the option to create an account in the candidate portal after they submit an application in ‘logged-out PCS’.

Some customers have ‘log in is mandatory’ - candidates must create a portal before they can finish submitting their applications.

This is already set up during PCS implementation.

On the ‘Candidate Portal (Logged-in PCS)’ tab, there is a filter ‘Candidate Portal type’ that lets the customer alter the visualizations based on their PCS type. The default is ‘Log in is optional’; if you have ‘logged-in mandatory’, please switch to ‘Log in is mandatory’ in the filter control. This will not be auto selected based on your PCS setting.

Source tracking related questions

Read PCS source tracking for further details.