Purpose

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

Audience

This document is created considering its use by recruiters and TA leads to identify sourcing events that lead to an application.

The basics

The TA Source Analytics Dashboard provides metrics about the application trends, how the applicants are breakdown by source, source type, source name and raw data to analyze the application based on various fields.

Users can access and log out of the dashboard by taking the following steps.

Accessing the Dashboard

1. Open a supported browser, and go to https://app.eightfold.ai.
2. Enter the email address and password for your EF account.
3. Click Sign In.
4. Go to the Dashboards tab, and select Source Analytics.

For the first time users:

If you are a first-time user of the TA Source dashboard, you will need to gain its access. Here’s how to provision the dashboard:

1. After signing in, go to More -> Admin Console -> Data Warehouse -> Provision Dashboards.
2. In the Source Analytics Dashboard 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.

Once provisioned, the dashboard will appear on the Dashboards tab.

1. Open a supported browser and go to https://app.eightfold.ai.
2. Enter your Registered Email Id and Password.
3. Click Sign In.

Logging out

To log out of https://app.eightfold.ai, select your user icon at the top-right of the page and then select Logout.

Dashboard features

When you access the TA Source Analytics Dashboard, you’ll see a Controls section/row and then several tabs, graphs, and tables, which make up the dashboard.

The Dashboard contains the following features along with the control’s section/row:

1. Applications Source Analytics
2. Quality & Diversity by Source
3. Recruiter Sourcing Deep Dive
4. Multi Touch Source Path
5. Raw Data
6. Glossary

The following sections describe the dashboard features in detail.

Controls

Controls are attributes used for customizing the TA Source Analytics Dashboard based on different fields (such as application date from, application date to, last N month, job function, position location country, business unit, ATS job ID, profile ID, source channel, and source group).

To better understand the dashboard tiles, it’s important to first understand the Controls section. To open the Controls section, click anywhere in the section. This will expand the Controls section and show the fields mentioned above.

In the Controls section, you’ll be using the fields as filters to show the information that you want to see in the dashboard, and it varies from customer to customer.

Update the fields as per your requirement for all the tabs under the controls.

• Date from - to: Date range associated with the visit date or the application date ("To" date is excluded from the time range).
• Last N months: Show the last N months on time series trend graphs.
• Job function: Job function or department of the position.
• Position location country: The location of the position could be different from the location of the career site visitor.
• Business unit: Business unit of the position.
• ATS job ID: ATS job id of the position.
• Source channel: Channel from which the application came in, including Career site & job boards, (recruiter) sourcing, Referral and Internal mobility.
• Source group: Sources from which the application came in; source variations are grouped into one (for example, 'LinkedIn' and 'lnkd' are grouped into 'LinkedIn').

Following are the terms that can be seen in the Controls tab. Those terms are explained below.

Application Date (from - to)

Application date is the date on which the application was submitted. ‘Application date From - To’ filters control the date range of all charts except for time series charts.

Please note that the date selected in ‘Application Date To’ is not included in the date range selected. For example, the following filter controls:

Application Date From: ‘2022/12/01’

Application Date To: ‘2023/01/01’

are selecting the whole month of December 2022, but 2023/01/01 is not selected.

Last N Months

This also filters on the application date.

This filter control controls the time series charts such as ‘LinkedIn to Career Site (last 6 months)’. The default value is 6 (last 6 months).

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 only.

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 only.

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 only.

ATS Job ID

This refers to the job IDs in the ATS.

This filter control will filter for the selected ATS Job IDs only.

Profile ID

This refers to the Eightfold generated Profile ID. It has a 1-to-1 mapping to candidate_id from the ATS.

This filter control will filter for the selected Profile IDs only.

Source Channel

Based on the source from which the applicant submitted their application, Eightfold grouped the sources into 4 Source Channels: Career site & job boards, (recruiter) sourcing, Referral and Internal mobility.

This grouping is based on the ‘source_type’ and ‘source_name’ raw data.

Please see ‘Metrics and dimensions calculation’ below for more information.

This filter control will filter for the selected Source Channels only.

This filter control is not applicable to the ‘Recruiter Sourcing Deep Dive’ tab or ‘ Multi Touch Source Path’ tab.

Source Group

Based on the source from which the applicant submitted their application, Eightfold grouped the source variations into source groups: LinkedIn, Indeed, Google, Referral, Recruiter, etc.

This grouping is based on the ‘source_type’ and ‘source_name’ raw data.

Please see ‘Metrics and dimensions calculation’ below for more information.

This filter control will filter for the selected Source Groups only.

This filter control is not applicable to the ‘Recruiter Sourcing Deep Dive’ tab or ‘ Multi Touch Source Path’ tab.

Metrics and dimensions calculation

The source analytics dashboard metrics and dimensions are given below.

Source channel

Description: Channel from which the application came in; including Career site & job boards, (recruiter) sourcing, Referral and Internal mobility.

• This grouping is based on the ‘source_type’ and ‘source_name’ raw data.
• Both ‘last-touch’ and ‘multi-touch’ attribution models have ‘Source channel’, and the definitions are the same.
• Please see FAQ section below for channel grouping logics.

Used in tab(s):

• Application Sources Analytics
• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch

Source group

Description: Sources from which the application came in; source variations are grouped and renamed into one.

• For example, 'LinkedIn' and 'lnkd' are grouped into 'LinkedIn'.
• ‘Source group’ is built based on source_type (raw data synced from ATS), source_name (raw data synced from ATS) and utm_source (raw data captured on Eightfold PCS).
• We first look at source_type and source_name, and if they do not provide meaningful information, we will then look at utm_source. For example, if source_type or source_name = 'LinkedIn', the 'source group' will be 'LinkedIn'; if source_type or source_name = 'applied', but utm_source = 'linkedin', then 'source group' will also be 'LinkedIn'.
• Both ‘last-touch’ and ‘multi-touch’ attribution models have ‘Source group’, and the definitions are largely the same.

Used in tab(s):

• Application Sources Analytics
• Quality & Diversity By Source
• Recruiter Sourcing Deep Dive
• Raw Data

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch

Applications

Description: Total number of applications submitted in the selected date range, including applications submitted on Career Site and not on Career Site.

Used in tab(s):

• Application Sources Analytics
• Quality & Diversity By Source
• Recruiter Sourcing Deep Dive
• Raw Data

Formula in Quicksight calculation:

distinct_count({application_id})

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

Hires

Description: Number of candidates hired.

• 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):

• Application Sources Analytics
• Quality & Diversity By Source
• Recruiter Sourcing Deep Dive
• Raw Data

Formula in Quicksight calculation:

distinct_countIf({application_id}, {stage_group} = 'hired')

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

Hire rate

Description: # of hires / # of applications

Used in tab(s):

• Application Sources Analytics
• Quality & Diversity By Source
• Recruiter Sourcing Deep Dive
• Raw Data

Formula in Quicksight calculation:

distinct_countIf({application_id}, {stage_group} = 'hired') / distinct_count({application_id})

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

Source to career site (PCS)

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'.
• Please see FAQ section below for PCS source tracking details.

Used in tab(s):

• Application Sources Analytics

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_career_site_metrics

Visitors (on career site)

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).

Used in tab(s):

• Application Sources Analytics

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 filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

Applicants (on career site)

Description: Number of unique visitors who submitted at least 1 application on the Career Site (PCS)

Used in tab(s):

• Application Sources Analytics

Formula in Quicksight calculation:

distinct_countIf({vs_cookie}, event = 'apply_to_job') with filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

• This dataset uses user activity server log data; there might be a small discrepancy between user activity server log data and applications data.

Applications started (on career site)

Description: Number of applications started on Career Site (PCS) ('application start' is the click on 'Apply' button of a job)

Used in tab(s):

• Application Sources Analytics

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 filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

Applications submitted (on career site)

Description: Number of applications submitted on Career Site (PCS)

Used in tab(s):

• Application Sources Analytics

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 filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

• This dataset uses user activity server log data; there might be a small discrepancy between user activity server log data and applications data.

Visitor to applicant conversion % (on career site)

Description: Applicants on career site / visitors on career site

Used in tab(s):

• Application Sources Analytics

Formula in Quicksight calculation:

Applicants / Visitors with filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

Application completion % (on career site)

Description: applications submitted / applications started

Used in tab(s):

• Application Sources Analytics

Formula in Quicksight calculation:

{Applications submitted} / {Applications started} with filter conditions: is PCS = 1 (namespace='smartapply' or namespace = 'career_hub_candidate') isValidActivity = 1 (ifelse(parseInt({response_code}) >=400 AND parseInt({response_code}) <=599, 0, 1) ) utm_source is NULL = 0 (ifelse(namespace = 'smartapply' AND isNull({utm_source}), 1,0))

Dataset(s):

source_analytics_career_site_metrics

Match score

Description: The match score generated by Eightfold AI for each application.

Used in tab(s):

• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

% of female applications

Description: # of female applications (self declared or inferred) / total # of applications.

• Gender diversity is measured by 1) applicants' self-declared data or 2) Eightfold AI inferred data.
• Gender information could be blank for some applications.

Used in tab(s):

• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation:

distinct_countIf({application_id}, {application_inferred_gender} = 'female') / distinct_count({application_id})

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

% of female hires

Description: # of female hires (self declared or inferred) / total # of hires.

• Gender diversity is measured by 1) applicants' self-declared data or 2) Eightfold AI inferred data.
• Gender information could be blank for some applications.

Used in tab(s):

• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation:

distinct_countIf({application_id}, {stage_group} = 'hired' AND {application_inferred_gender} = 'female') / distinct_countIf({application_id}, {stage_group} = 'hired')

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

% of ethnicity diversity applications

Description: # of applications where the candidate's ethnicity is underrepresented* (self declared or inferred) / total # of applications.

• ethnicity diversity is measured by 1) applicants' self-declared data or 2) Eightfold AI inferred data.
• Ethnicity information could be blank for some applications.

• By default, "Underrepresented" includes one of the following, which is consistent with the evolving standard in diversity reports:

  • Native American or Alaskan Native
  • Black or African American
  • Hispanic or Latino
  • Native Hawaiian or Pacific Islander
  • Two or More Races

Used in tab(s):

• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation: distinct_countIf({application_id}, ({application_inferred_race} = 'black' OR {application_inferred_race} = 'hispanic' OR {application_inferred_race} = 'american indian or alaskan native' OR {application_inferred_race} = 'two or more races' OR {application_inferred_race} = 'native hawaiian or pacific islander') ) / distinct_count({application_id})

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

% of ethnicity diversity hires

Description: # of hires where the candidate's ethnicity is underrepresented* (self declared or inferred) / total # of hires.

• ethnicity diversity is measured by 1) applicants' self-declared data or 2) Eightfold AI inferred data.
• Ethnicity information could be blank for some applications.

• By default, "Underrepresented" includes one of the following, which is consistent with the evolving standard in diversity reports:

  • Native American or Alaskan Native
  • Black or African American
  • Hispanic or Latino
  • Native Hawaiian or Pacific Islander
  • Two or More Races

Used in tab(s):

• Quality & Diversity By Source
• Raw Data

Formula in Quicksight calculation:

distinct_countIf({application_id}, {stage_group} = 'hired' AND ({application_inferred_race} = 'black' OR {application_inferred_race} = 'hispanic' OR {application_inferred_race} = 'american indian or alaskan native' OR {application_inferred_race} = 'two or more races' OR {application_inferred_race} = 'native hawaiian or pacific islander') ) / distinct_countIf({application_id}, {stage_group} = 'hired')

Dataset(s):

source_analytics_application_source_lasttouch source_analytics_application_source_multitouch source_analytics_application_source_path_multitouch

Source path

Description: Besides the last-touch source (presented in the 'Application Sources Analytics' tab), there could be other sources that contributed to the conversion of the application. The 'source path' plots out all the sources related to an application chronologically.

• Please see FAQ section below for ‘source attribution model’

Used in tab(s):

• Multi Touch Source Path

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_application_source_path_multitouch

Stage group

Description: the stage group where the application is in, including ' new applicant', 'phone screen', 'onsite', etc. This field is dependent on ATS-Eightfold stage group mapping.

Used in tab(s):

• Raw Data

Formula in Quicksight calculation: N/A

Dataset(s):

source_analytics_application_source_lasttouch

Dashboard charts (tabs in details)

This section describes the various charts within the Source Analytics Dashboard. You can expand each tile for easier viewing by clicking the expand icon at the top-right corner of the tile. You can also export each tile’s data into CSV or Excel format, depending on which tile you’re exporting data for, by selecting the menu icon at the top right.

Applications Sources Analytics tab

This tab uses ‘last touch attribution’.

Source Channel Overview

KPI boxes in this section show applications and hires overview of the 4 channels & total of the following:

• Career Site
• (Recruiter) Sourcing
• Referral
• Internal Mobility

Applications and hires by source channel waterfall charts

These charts use ‘waterfall charts’ to show the proportion of applications or hires coming from each source channel. The bar on the far right of each chart shows the total number of applications or hires.

Applications and hires by source group pivot table

This pivot table provides more detailed source data for each channel. Click on ‘+’ to view source groups in each channel.

Applications and hires by top 10 source groups pie charts

These pie charts show the top 10 source groups in terms of applications or hires. Source groups ranking 11 and after will be lumped together in the ‘other’ slice.

Career site (PCS) sources conversion funnel table

This table focuses on source to career sites. It shows the different sources that send traffic to the career site, and the visitors, applicants, visitor to applicant conversion, etc. metrics of each source.

This dataset uses user activity server log data; there might be a small discrepancy between user activity server log data and applications data.

LinkedIn/Indeed/Google/Glassdoor to career site time series charts

This time series charts show the MoM movement of # of applications submitted and visitor to-applicant conversion of the top job boards. For example:

• LinkedIn to Career Site (last 6 months)
• Indeed to Career Site (last 6 months)
• Google to Career Site (last 6 months)
• Glassdoor to Career Site (last 6 months)

The number of months included in the chart can be controlled by the ‘Last N Months’ filter control.

Quality & Diversity By Source tab

This tab uses ‘last touch attribution’.

Source Channel Overview for quality and diversity

KPI boxes in this section show an overview of the 4 channels & total: average match score, % of female applications, % of ethnicity diversity applications of the following:

• Career Site
• (Recruiter) Sourcing
• Referral
• Internal Mobility

Avg. application match score by top 10 source groups scatter chart

This scatter chart shows the average match score and the number of applications of the top 10 source groups (in terms of applications).

The x-axis shows the number of applications of each source group; the y-axis shows the average match score of each source group.

Take the ‘LinkedIn’ example in the example chart below: LinkedIn has brought in 3709 applications and its average match score was 2.36. Compared with other source groups, it has the most applications, but the average match score is relatively low.

Gender/ethnicity diversity by top 10 source groups

These side-by-side bar charts show % of diversity applications and hires of the top 10 source groups of the following:

• Gender diversity by top 10 source groups
• Ethnicity diversity by top 10 source groups

Source groups ranking 11 and after will be lumped together in the ‘other’ bars.

Orange bars show % of diversity applications; blue bars show % of diversity hires. Comparing them side by side gives indication of diversity hire rates of each source group.

Recruiter Sourcing Deep Dive tab

This tab uses ‘multi touch attribution’.

Recruiters sourcing details pivot table

This pivot table shows detailed source data related to (recruiter) sourcing. Typical (recruiter) sourcing includes ‘recruiter sourcing via Chrome extension’, ‘Eightfold Campaign’ etc.

The data of this pivot table uses ‘multi-touch attribution’, meaning it includes applications that have recruiter involvement at ANY touch point, and it is essentially counting duplicates (e.g. if a candidate has been 'sourced via chrome extension' as well as 'sourced via email/SMS/whatsapp', they are counted in both buckets)

Therefore, the number of applications and hires in this table is higher than those in the 'Applications and Hires by Source Group' table in 'last touch attribution'.

Click on ‘+’ to see details in each source group.

Multi-Touch Source Path tab

This tab uses ‘multi touch attribution’.

Applications & hires by multi-touch source path table

The 'multi touch source path' shows all the sources related to an application in chronological order. The most popular 'path combinations' are shown here, along with the applications, hires and hire rate of the source paths.

For example, if a job seeker has gone through the following steps to find and apply to a job:

Job seeker went to a career fair and left their contact information →

Recruiter reached out the them via email and invited them to apply →

Job seeker searched for the company’s career site on Google →

From Google they landed on the company’s PCS, found an ideal position and submitted an application

'Career fair', 'recruiter reaching out', 'Google' and PCS are all sources that helped to convert this application, and are part of the ‘multi-touch source path’.

Raw Data

Provide raw data at profile and application ID level, including timestamps, match scores, diversity data, stage groups, and raw source names.

Glossary

This tab contains the definitions for all the key performance indicators (KPIs) used in this Dashboard.

Frequently asked questions

Here is a list of all the frequently asked questions about the source analytics dashboard:

Source attribution model (last touch attribution & multi touch attribution)

First let’s see a digital marketing example:

In job seeking, a job seeker typically uses multiple sources and has multiple engagement before they find and apply to a job. Suppose a candidate had the following sources and engagement:

Job seeker went to a career fair and left their contact information → recruiter reached out the them via email and invited them to apply → job seeker searched for the company’s career site on Google → from Google they landed on the company’s PCS, found an ideal position and submitted an application

Career fair, recruiter, Google and the PCS are all sources that helped the candidate to find the job and apply. Eightfold records all sources and engagement (that Eightfold can track), and provides reports and insights on last-touch attribution (default) as well as multi-touch attribution (supplementary).

Last-touch attribution model

By default, Eightfold reports on the last source from which the application happened. Consider this example again:

Job seeker went to a career fair and left their contact information → recruiter reached out the them via email and invited them to apply → job seeker searched for the company’s career site on Google → from Google they landed on the company’s PCS, found an ideal position and submitted an application

The last source is ‘PCS (from Google)’, so on the TA UI the source associated with the application is ‘PCS (from Google)’, and on the Source Analytics Dashboard the default source associated with this application is also ‘PCS (from Google)’.

Multi-touch attribution model

For the same job seeker journey above, Career fair, recruiter, Google and the PCS are all sources of the application. They will get attribution and are shown in the ‘multi-touch attribution’ sections on the Source Analytics Dashboard, but they will not be shown on the TA UI.

Channels and source groups (grouping logic)

Application sources come from 1) ATS and 2) Eightfold tracking. For customers using Eightfold PCS, ‘career site’ related source data in ATS originated from PCS source tracking.

Using the raw source data, Eightfold categorizes the sources into ‘source channels’, and under each ‘source channel’ there are one or more ‘source groups’.

Source channels and source groups definitions and examples:

Source channel	Description	Source Timestamp Logic	Source group in this channel - examples
Career Site	The application was made on the companies' career site (either the Eightfold PCS or the other career sites)	Source time = application time	‘LinkedIn’, ‘LinkedIn Paid Campaigns’, ‘Indeed’ *sources in channel ‘Career Site’ are essentially the activity sources to the Career Site. The values are usually the post-mapped values of the PCS activity sources (utm_source, src, referrer, etc.)
Referral	Candidate was referred by an internal employee	Source time = application time	‘Employee Referral’
Internal (Mobility)	Candidate is currently an internal employee	Source time = application time	‘Internal Employee’
(Eightfold) Campaign	Candidate was part of an (Eightfold) Campaign	Source time = campaign email sent T=time	‘Midwest Engineering Outreach Campaign’
Eightfold Talent Network	Candidate having a pre-existing application within Eightfold for at least 28 days Please see below for more information
Recruiter reaching out via email/SMS/whatsapp	Recruiting Contacting the candidate via email or text	Source time = email/text sent time	‘bob@XYZ.com’ *usually the source in this channel is the recruiter’s email
Recruiter reaching out via Eightfold Chrome Extension	Recruiter reaching out to prospect using the the Eightfold Chrome Extension (on LinkedIn)	Source time = contact time	‘LinkedIn - public profile’ *usually the source in this channel is the job board or social network where the extension is used
(Recruiter) imported	If the profile was added via ‘import resume’ 90 days prior to application, ‘Imported’ would be one of the multi-touch sources. For example, a recruiter can import ideal candidates from one position to another.	Source time = import time	‘import@XYZ.com’ usually the source in this channel is email of the import action taker
Recruiter requesting leads from Talent Network	Candidate was sourced through Talent Network leads	Source time = the time at which the EFN request was made
(Offline) recruiting events	Candidate came to an offline recruiting event		‘Campus recruiting event’

 

How does Eightfold source tracking work?

More information to come.

What does (Eightfold) Talent Network mean?

If the profile had a pre-existing application within Eightfold for at least 28 days, Talent Network is considered to have contributed to the application. This only reflects that prior to this application this candidate had already been in the system.

For example, if a candidate (profile) has the following applications:

• First application was submitted on Jan 1, 2022
• (candidate became part of the Talent Network)
• Second application was submitted on March 1, 2022

Talent Network is considered to have contributed to the second application because the candidate had become part of the Talent Network prior to the second application.