1. Implementing Recruiting
  2. Data Consideration

Data Consideration

Below are points to consider regarding your data management.

  • Data Visibility by User Group: Requisitions visible on the LinkedIn Recruiter application for the One-Click Export feature are determined by the user groups to which a user belongs. Submissions visible on the LinkedIn Recruiter application in the ATS Indicator are determined by the user groups to which a user belongs.

  • Requisition Location: Requisition locations are sent to LinkedIn in the base language of the requisition. LinkedIn subsequently parses the locations, and assigns those job locations structures in LinkedIn’s location data model. The location names configured for your countries, states/provinces, and cities, should be standard globally understood location names. Peculiarities such as “Branch Office 12345” in a location title may result in poor location processing by LinkedIn.

  • Postal Code: The postal code is sent to LinkedIn. It's recommended to populate postal codes at the lowest level on the location tree. This includes levels below the City level, which are not mapped on the location mapping.

  • Requisition Number: The Requisition Number field must not be blank. Requisitions with an unpopulated requisition number will not be synchronized with LinkedIn.

  • Job Title: The value in the Job Title field must be between 1 and 200 characters in the base language of the requisition to be included in the synchronization. Requisitions with blank job titles or with more than 200 characters are excluded from the synchronization.

  • Job Description: The External Job Description field must not be blank. Requisitions with unpopulated external job descriptions are excluded from the synchronization. Also, the External Job Description field should be configured as Required for Saving or Required for Approval, and not Required for Sourcing. Requisitions with the Open status are eligible for export to LinkedIn.

  • Synchronization of Delete Action and Other Actions: When candidates or submissions are deleted, they will also be deleted from LinkedIn Recruiter. This delete action at LinkedIn doesn't impact a LinkedIn Member’s member profile they maintain themselves. Only the Taleo information which was synchronized to LinkedIn is deleted. When requisitions are deleted from Taleo, they will be sent to LinkedIn as Closed, and no longer available for use on the 1-Click Export service. If you use a limited data set, descoping parameters will invoke a delete action for requisitions and submissions. Any requisitions for the descoped parameter will be closed at LinkedIn.

  • Posted Requisitions: Requisitions posted on a Career Section of type External and display type Public, are posted on the LinkedIn jobs site as a Limited Listing. That posting will include a link to apply to the job on the Career Section. As those requisitions become unposted from the Career Section, they will be also be unposted from LinkedIn.

  • InMails and Notes: All InMails and Notes synchronized into Oracle Taleo Enterprise Edition from LinkedIn Recruiter are visible to all users who have a LinkedIn Recruiter seat connected.

  • Seats: Only one Taleo account can use a LinkedIn Recruiter seat. Seat sharing is not permitted.