AI Sourcing Report

The AI Sourcing Report provides metrics for prospects and candidates that have been sourced with our AI Sourcing (Cold Prospects) tool. It counts totals rather than uniques, meaning if an externally sourced prospect is sent to multiple requisitions, they are counted for each one. 

In this article:
Purpose
Metrics
Data
Filters

Purpose

The purpose of the AI Sourcing reporting is to offer a more accurate reflection of value, as you can leverage a single-sourced prospect across multiple requisitions, maximizing your investment and getting more value out of each externally sourced prospect.

• Visibility into Prospect Data: Enable insights into the entire lifecycle of prospects, starting from when they are added to drip campaigns to when they become candidates and hires.
• Highlight AI Sourcing Value: Provide clear KPIs that reflect the ROI of AI Sourcing, not only on externally sourced candidates and hires but also on the effectiveness of sourcing efforts at the prospect stage.

Metrics

Credit Usage

This tracks the total number of credits used to add prospects to the drip campaigns from the Cold Prospects feature. Deleting prospects or candidates does not affect this count.

Prospect Value Multiplier

This measures how efficiently each externally sourced prospect or credit is leveraged across multiple requisitions. A value greater than 100% indicates that prospects are being used in multiple requisitions, maximizing the return on sourcing efforts and increasing the overall value per credit. This KPI helps assess how well AI Sourcing contributes to reducing sourcing costs while improving efficiency in filling roles.

Count of Externally Sourced Candidates

This measures the number of prospects that were successfully converted into candidates. This is calculated by counting all Cold Prospect sourced candidates. If prospects or candidates sourced from Cold Prospects are forwarded to multiple requisitions as a candidate, they are counted for each one.

Count of Externally Sourced Hires

This shows how many externally sourced candidates resulted in hires. This is calculated by counting all hires sourced from Cold Prospects. If prospects or candidates sourced from Cold Prospects are forwarded to another requisition and hired, they are included.

AI Sourcing Funnel: Counts by Current Workflow Type

This chart shows how prospects and candidates sourced from Cold Prospects progress through each Workflow Type. Prospects and candidates are counted each time they enter a new Workflow Type but are not double-counted within the same type, even if they move between stages or re-enter later.

For source comparisons, use the Workflow Stage Analysis report (note: different date filters apply). This chart reflects historical data, not the current funnel.

Note

This report only counts externally sourced prospects and candidates, it does not count prospects or candidates that have a different source. It counts totals rather than uniques, meaning if an externally sourced prospect is sent to multiple requisitions, they are counted for each one. This approach offers a more accurate reflection of value, as you can leverage a single-sourced prospect across multiple requisitions, maximizing your investment and getting more value out of each externally sourced prospect.

Data

Date Added

The date the Prospect or Candidate was added to the requisition. This can be either from:

• Cold Prospect tool to the Drip Campaign
• Drip Campaign to another requisition
• Requisitions to drip campaign on another requisition
• Requisition to another requisition

Prospect Name

This data point is populated from the cold prospect information—the full name of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is the name on their profile.

Prospect State

This data point is populated from the cold prospect information—the location state of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is populated when they were originally created or when their candidate profile was edited.

Prospect City

The location city of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is populated when they were originally created or when their candidate profile was edited.

Prospect Zip Code

The location zip code of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is populated when they were originally created or when their candidate profile was edited.

Prospect Email

The email of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is populated when they were originally created or when their candidate profile was edited.

Prospect Phone

The phone number of the Prospect or Candidate. For a newly created Prospect, this is pulled in when they are added to the drip campaign. For Prospects or Candidates that already exist in the system, this is populated when they were originally created or when their candidate profile was edited.

Workflow Type (Historical)

The name of the Workflow Type the candidate was in when they were moved into its associated Workflow Stage (Historical).

Workflow Stage (Historical)

The name of the Workflow Stage the candidate was moved into at the specific time recorded in "Date Entered Workflow Stage (Historical)".

Date Entered Workflow Stage (Historical)

The date the user moved the candidate into the specific Workflow Stage (Historical).

Requisition Title

The title of the requisition entered in the 'Enter job title for posting' field.

Requisition ID

An optional field for a unique identifier for a requisition, either manually entered by the user or auto-generated if the auto-generation feature is enabled. When the auto-generation feature is enabled, the system assigns the ID upon the requisition's initial save. Admins can enable auto-population of requisition IDs via Tools → Setup → Recruiting Setup → Requisitions. Requisition IDs must be unique across the organization and cannot be reused, even for unposted or deleted requisitions and templates.

Requisition Status

Indicates the current state of the requisition, such as open, on hold, or closed.

Recruiter Assigned to Requisition

The name of the recruiter assigned to the requisition. This field is required and selected under the Hiring Team section of a requisition. This is not an indicator of who added the Prospect to the drip campaign or moved a Prospect or Candidate.

Hiring Manager Assigned to Requisition

The name of the hiring manager assigned to the requisition. This field is required and selected under the Hiring Team section of a requisition. This is not an indicator of who added the Prospect to the drip campaign or moved a Prospect or Candidate.

Requisition Role

The name of the role associated with the requisition.

Requisition Custom Fields (if applicable)

The custom fields that users created and have marked to be “Included in Report”. These custom fields can be found under Setup → Custom Fields → Select Requisition Custom Fields.

Filters

Date Added	Requisition Title
Requisition ID	Requisition Role
Department	Office
Workflow Type (Historical)