Candidate Source Tracking
Source tracking helps identify from what source candidates originated. Source tracking information is displayed in the Source Info section in the candidate profiles, candidate job applications, prospect records, and candidate pool members.
When source information is captured, the domain name of the source is captured along with the long URL. The domain name appears in the interface as the display name, whereas the long URL is available in the database for reporting purposes. Source information (source medium and source name) can be changed by recruiting users to make sure the right source is captured. Note that the source information of type referral can't be changed.
When recruiting users create candidate profiles, these sources are available.
-
LinkedIn
-
Facebook
-
Email
-
Phone
-
Resume Handed in Person
The source mediums and sources listed in this table are provided with the product. For some source mediums using UTM codes, the list of source names is extensible. You can decide on the actual source name that will be captured. Here are the source mediums having extensible list of source names:
-
Shared for posting
-
Job board
-
Job aggregator
-
Third party
|
Source Medium |
Source |
Description |
UTM Code |
|---|---|---|---|
|
Campaign |
|
The candidate applied from a campaign email or from social media channels. |
utm_source=email&utm_medium=campaign utm_source=linkedin&utm_medium=campaign utm_source=facebook&utm_medium=campaign utm_source=twitter&utm_medium=campaign |
|
Candidate added to job requisition |
Job Requisition Candidate Profile Candidate Search Candidate Pool |
The recruiter uses the Add to Job Requisition action to add a candidate to a job requisition from another requisition, from a candidate profile, or after performing a candidate search. Example:
|
utm_source=job+requisition&utm_medium=manual+add utm_source=candidate+profile&utm_medium=manual+add utm_source=candidate+search&utm_medium=manual+add utm_source=candidate+pool&utm_medium=manual+add |
|
Candidate added to pool |
Job Requisition Candidate Profile Candidate Search Candidate Pool Talent Community |
The recruiter adds a candidate to a job requisition from another pool, from a candidate profile, from a requisition, or after performing a candidate search. The application automatically adds a candidate to a talent community pool by matching candidate preferences to the pool context. Example:
|
none |
|
Candidate created manually |
Phone Resume handed in person Agency |
The recruiter creates a candidate manually using the Create Candidate action. For example, a recruiter was actively searching for new candidates on LinkedIn, or a candidate handed a resume in a restaurant. The task to add more source names to the list is Manage Candidate Dimension Source Names. |
none |
|
Career site |
External Career Site Internal Career Site Talent Community Job Alert |
The candidate applied from an external career site or an internal career site, or a candidate received a job alert and applied using an external career site. It doesn't include referred candidates who applied using an external or internal career sites. Example:
|
utm_source=job+alert&utm_medium=career+site |
|
Intelligent matching |
Job requisition |
The candidate is selected by the intelligent matching feature. Example:
|
none |
|
Job aggregator |
Name of job aggregator |
The candidate found a link to a job requisition on a job aggregator. Example:
|
utm_source=indeed&utm_medium=job+aggregator |
|
Job board |
Name of job board |
The candidate applied on a job from a job board. |
utm_medium=jobboard&utm_source=ziprecruiter |
|
Referral |
External Referral Internal Referral Agency Referral |
The user or agent is referring a person outside of the company (external candidate) or an employee (internal candidate). Example:
|
utm_source=external+referral&utm_medium=referral utm_source=agency+referral&utm_medium=referral |
|
Referral website |
The candidate originated from any other referral website. Example:
|
none If you have an external career site that has a link to the Oracle Recruiting career site, by default the Oracle Recruiting career site is considered as an external referral and it's logged as such in the source tracking. To track candidates as direct visitors, you need to add the rel="noreferrer" attribute to the link. For example: <a href="www.mycareersite.com" rel="noreferrer"> Find Jobs Today</a> |
|
|
Search engine |
Yahoo Bing |
The candidate searched for a company career site or job requisition using a search engine such as Google, Yahoo, Bing. Example:
|
none |
|
Shared job posting |
none |
The job shared using the copy link on a career site. Example:
|
utm_source=external+job+share&utm_medium=jobshare |
|
Social media |
|
The candidate found a link to a career site or job requisition on Facebook or Twitter. Example:
|
none |
|
Third Party |
Third Party Name |
The recruiter manually adds codes to the job url link. Example:
|
utm_source=ITJobs&utm_medium=third+party |
URL Code to Capture a Source
For source mediums that use UTM parameters in the URL, the utm_medium and utm_source parameters must be added to the URL to capture the source. In some cases, the UTM code is added automatically. In other cases, you must add it.
Use the following schema:
<client domain>/hcmUI/CandidateExperience/<LanguageCode>/sites/<SiteCode>/job/<jobid>/?utm_medium=<medium_code>&utm_source=<source_code>
Example:
https://eifv.fa.us643.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX/job/75/?utm_medium=jobboard&utm_source=indeed
Only source mediums that use URL parameters can be hand coded.
These source mediums have nonextensible list of source names. You must use the URM code in the above table.
-
Candidate added to job requisition
-
Career site, job alert
-
Referral
-
Campaign
These source mediums have extensible list of source names. You can decide on the actual source name that will be captured.
-
Shared for posting
-
Job board
-
Job aggregator
-
Third party