2090953 - Advanced Analytics Frequently Asked Questions - Recruiting Marketing

• SAP SuccessFactors Recruiting Marketing
• Advanced Analytics

There are several potential reasons for this. If the date field you are using in your ATS report is different than the one you provide in your extract, the numbers will likely not align.

Analytics typically only contains external activity. If your ATS report is including internal activity, that would also cause the data to not align.

Most of the reporting in Analytics only displays data where we had a match back to the talent community. To see all of your ATS data, you need to use the Browse report and select “Display all ATS data” in the options.

Q. How can I have more Apply Completes than Apply Starts?

When a candidate starts the apply process, we record one apply start record. If that candidate applies to multiple positions while in the ATS during that apply session, they could have multiple apply complete records.

(Note they must be logged in to their profile -new or existing- for the Apply start to be counted)

Also note that depending on whether you select the Advance Option : “Include Additional ATS application” , Apply Completes may or may not include candidates that didn’t apply via RMK. (Forwarded applies, manually entered applies, or candidates that only applied within the ATS)

Q. When I look at my data by a certain filter, there are a lot of Visits and Subscribes listed as Undefined.

If you filter your data using a field related to a job/requisition, you will likely see a large number of visits and subscribes in the Undefined bucket. The reason is job data points are associated to a specific job id/requisition id. Often times a visit lands on a page not tied to a specific job, such as a strategy page. Because we do not know what job id/requisition id to associate with that visit, it is associated to no job id/requisition id. This typically happens at the visit and subscribe steps. Once a candidate starts the apply process, they are almost always associated with a specific job id/requisition id.

Q. What is the difference between current referrer source and original referrer source?

 Current referrer source is the source that drove the candidate to the specific job. A candidate can have multiple current referrer sources, depending on how many applies they have and if they used different sources for those applies. Original referrer source is the source that drove the candidate to join the talent community. Candidates only have one original referrer source.

Q. Why is the Apply Conversion % on Browse different than the What does my applicant conversion look like report in Ask?

Apply Conversion % on Browse is simply taking the Apply Completes and dividing it by Apply Starts. This number can be skewed by candidates applying to multiple positions during one apply start session so this means the number could be higher than 100.

The most accurate applicant conversion numbers are in the Applicant Conversion Report. This report takes all apply start records and looks for the corresponding apply complete record. It does not factor in additional apply complete records that do not have an apply start record.

Q. Is there a way to see when was a particular candidate hired?

A. Yes. On the Summarize tab, in the right/middle of the page, there is an input box that allows you to search talent community by email or by applicant id. You can search individual candidate records with this search box.

Q. In Advance analytics side how is the status date retrieved for the status hired.

Status dates reflect the date assigned to an ATS status that is mapped to hired (or whichever Analytics status you may be looking at).

You can review the app status audit trail to see the dates in which candidates were assigned to a particular status. If you have multiple statuses mapped to one Advanced Analytics status (very common) then AA will use the following logic for which records to keep:

- Within any single data load, Advanced Analytics will take the most recent Advanced Analytics status mapping for each of the Advanced Analytics status buckets for a given applicant.
- Outside of a single data load (read: thinking long term and overall) Advanced Analytics will maintain the first status mapping recorded for each Advanced Analytics bucket for a given applicant.

Note: the above 2 pieces of logic are very minute details and tend not to skew the data very much. If you check an applicant's app status audit trail and check the Advanced Analytics applicant detail page, then you will see how these match up. It is very intuitive.

Q. Why does the number of hires in AA not match the number in my pipeline

Make sure that you under Advanced Options you have the following options selected:
Display all Applicant Tracking System data and Include additional Applicant Tracking System applications since Hires constitute ATS data

Q. The date range that inserted in Browser tab is referring to which date? To the date when candidate applied to a job or date that candidate created an account?

The date range selected in Advanced Analytics applies to the status date (or activity date). So in terms of Apply completes, these records show because the candidate was assigned to the status (status date) on a date within your currently selected range. Measure definitions can be shown in the resources tab in the top right of Advanced Analytics. We recommend you to review the resources tab. Overall, Advanced Analytics functions on status date.

Q. Are there scheduled daily outages or known performance issues with Advanced Analytics

Due to a nightly refresh process, there WILL be a daily outage for Advanced Analytics in each environment. Outside of Rackspace these outages will be brief and should be scheduled to occur between midnight and 8:00 am in the local timezone for the datacenter. The outage in Rackspace is expected to be about 2 hours per day. The timing of the outage is dependent on how long the various precursor steps in the nightly refresh process take. This daily outage is a known issue and not a defect. We have been and will continue to try to improve performance of the nightly refresh in order to minimize the impact on AA availability in Rackspace during the US workday.

General performance issues with Rackspace which could cause long data loading times in the UI and unresponsive pages messages being displayed are being addressed via a project which is currently targeted for completion by release 2H2021. This KBA will be updated if the timeline is updated.

Q. What is the difference between Source Engines LinkedIn and LinkedIn Job Posting?

LinkedIn Postings is the source code for traffic from LinkedIn slot/sponsored job advertisements. LinkedIn is general LinkedIn traffic based on the referring URL of “LinkedIn.com”. LinkedIn Postings is generally only recorded when the recruiter uses Source Tracker, RMK XML Feed for automation or Recruiting Posting, because most general LinkedIn traffic defaults to "LinkedIn" if not hard-code tracked via those methods.

Q. How to export data from AA?

When any query or report is run, the Export button will be available in the UI. Note the only available option is currently to export a CSV file. Some transformation might be required to convert text data into spreadsheets, this video might help. (see this Microsoft Office Support page)
If the destination is other than Excel please refer to the corresponding software documentation.

Q.There is a discrepancy in the numbers for Interviews recorded in AA compared to RCM for a requisition. The number is larger in AA than RCM.

Advanced Analytics backfills skipped statuses. So even if a candidate was moved from a status to another in RCM but some statuses were actually skipped, because these statuses were mapped in AA then the missing statuses are backfilled by AA.
This then causes discrepancies in the count between the two systems as you get much higher numbers in AA. (see KBA 2951463 - Advanced Analytics backfills missing statuses - Recruiting Marketing)

Q. Can data appear anonymized in AA?

RCM is the system of record. If data anonymization is triggered in RCM then this will be reflected in AA. Results will be retained but PII will be anonymized.

Q. Why are there unknown sources appearing in AA?

RMK captures candidate traffic when they enter onto the career site.  The source means how the candidate found the posting which then brought them back to RMK to apply. There are multiple ways where RMK will track where a candidate came from.  The default option is if there is a referring URL able to be captured, which is the previous site that the candidate came from.  The primary method of tracking is if there is hardcoded utm_source tracking tags added to the end of the landing page URL.  The hardcoded tracking is based on very specific tags that are maintained within the RMK tracking system by vendor and/or product. Jobs can be posted manually to third party sites via source tracker for example. In this case the source will be one of the RMK enabled sources (see 3046033 - Career Site Builder Site Source Editor - Recruiting Marketing)
Postings may also be broadcast by RMK automatically by approved automatic job feeds, however there are cases where third party sites may also scrape the content from the public RMK site.  In these cases the job board will list the jobs on their sites for free or potentially extend them out to their own network channels for additional exposure.
As a result, some unexpected sources can be captured.

Q : When is the data retrieved and processed from RCM 

The data is retrieved at 12:00 pm and processed at 1:00 PM in the data center’s local time on the scheduled date. Each subsequent time the process runs, it retrieves data going back to the end of the last run date.

Q : Is it possible to purge historical requisition data after a field mapping change?

No. After a field mapping change, historical data (data from closed requisitions) will still be shown resulting in a mixture of values from before and after the mapping change. This cannot be helped or removed. This is why it is not recommended to change field mapping after the original implementation.

Q: The CSV export is truncated at 10000 rows. Is this expected? Can this be worked around?

Yes. this is the maximum that can be exported. To extract all the data, it would have to be extracted in chunks by limiting the time period.

2234847 - About Recruiting Marketing Advanced Analytics
2557093 - Candidate Status Mapping from RCM to RMK Advanced Analytics

Advanced Analytics, Linkedin, scheduled daily outage, date range, status , KBA , LOD-SF-RMK-AAN , Advanced Analytics - Professional Services , How To