Configuring Advanced Analytics

All applicant statuses on the Application Workbench must be mapped. For example, if the customer has multiple disqualification statuses on their talent pipeline, ensure that each is mapped to an Advanced Analytics status, usually "ATS Capture" (which will not display on the reporting). If a status is not mapped when the integration is run, the sync will fail.

Customers can improve their recruiting processes by viewing the candidate progression from visit to apply to hire. They want to know: How long did it take to get through the statuses? Where are the hold-ups in the candidate process?

To assist with this, it’s helpful to map for reporting the minimum number of statuses that will help customers track candidate history. Map the most accurate and initial status that the customer would like to track to. For example, if there are multiple screening statuses (such as "Recruiter Review", "Hiring Manager Review", and so on) map the first one to "Qualified" and the others to "ATS Capture".

Do not include internal logistical steps in the reporting. For example, if the customer has "ScheduleInterview" and "Prepare Offer" statuses, map those statuses to "ATS Capture".

Lastly, be mindful of how the Talent Pipeline is configured. For example, if statuses are grouped together, ensure to map all statuses within the grouping.

Status Mappings in the Advanced Analytics Admin Interface

After setting up the integration, if there are statuses that are not mapped a notification will be triggered. After the data is processed, an Unmapped Statuses email will be sent to the person(s) with the Notify email address on the Integration Settings page. The email contains a spreadsheet listing the statuses that need to be mapped.

Map any statuses that are available to map. Otherwise, the system will be "on hold" and data will not be captured.

If a new status is added to the customer’s applicant status set, the synchronizations will continue to happen, but that ATS data is not loaded. It is critical to map all statuses.

Once mapped, statuses cannot be easily changed. If you make an error during mapping, you will need to do a data purge and reload all of the status data. This is discussed under Data Purge in this lesson.

Customers may want to change field labels in Advanced Analytics reports. For example, when a job requisition field is mapped to a field with a different name, such as Custom Field 1, this is where you will make the change.

Data Purge is used to correct errors. It removes existing information so it can be corrected. All purged data must be completely reloaded.

An ATS Data Purge is used when the customer would like to change their status mappings. You can choose to purge all data, or you can select a starting date from which to purge the data.

Note that you do not need to purge data because existing statuses need to be mapped, only when statuses were mapped incorrectly.

When you run a purge, all statuses will be pulled in the next day (or the day after, depending on cutoff time), regardless of the frequency that is set.

The status activity will be reloaded since the date at the bottom of the Integration Settings page.

Functional consultants will complete the setup by granting permission to generate reports. Customers also have the ability to enable their own users.

Users must be set up in Recruiter SSO. There are two levels of permissions:

• Ability to access reporting in Advanced Analytics
• Ability to drill into the details (international customers will want to limit this permission if recruiters in one country shouldn't be able to view candidates for jobs in a different country)

Remember that when you configured the Integration Settings page, in the Notify field, you entered your email address so that after the nightly data sync runs, you will receive an email notification if statuses need to be mapped. After all statuses have been successfully mapped to Advanced Analytics, you will remove your email address from this field and enter the email address(es) for the customer administrator who is to be responsible for monitoring this. Multiple emails and/or email distribution lists can be entered in the Notify field, separated by a semicolon. For example: admin@email.com, hris@email.com (distribution list).

Remind your customer that they do not have access to the backend Recruiting Command Center application. If they change or add statuses to the applicant status set and receive an email about the change, they will need to contact Support to map the new status(es) in Advanced Analytics.

• Every Applicant Workbench status must be mapped to an Advanced Analytics status, and unmapped statuses can cause the sync to fail or pause, with any issues sent to the designated notification address.
• Statuses should be mapped for meaningful reporting rather than internal workflow steps, assigning the first relevant status to a reporting category and routing intermediate steps to ATS Capture, while pre‑application and RMK‑specific statuses remain unmapped.
• Status mappings are difficult to change once applied, and corrections require an ATS data purge and full reload, so organizations should finalize mappings carefully, assign appropriate user permissions, and update notification recipients to customer administrators.