Overview
This article explains how applicant data behaves once a Core Applicant ATS integration is in place, including:
- What data is imported
- How frequently data is refreshed
- How ATS changes can impact integrations
How Applicant Data Is Used
Applicant integrations are used to:
- Complete the candidate’s hiring story within Radancy CRM
- Track applicant progress through ATS workflows
- Enable recruiters to target messaging based on applicant stage
- Maintain alignment between ATS hiring stages and CRM visibility
By default:
- Radancy imports active applications only
- Withdrawn, rejected, or historical applications are excluded unless explicitly required
Candidate Backfill
A candidate backfill is the process of importing historical applicant data outside of the standard ongoing integration.
Backfills are used to:
- Populate CRM with applicant records that existed prior to integration go‑live
- Import applicants that fall outside default import rules
Important considerations:
- Backfills are typically one‑time or limited‑scope
- They are not part of the ongoing automated applicant feed
Data Frequency & Refresh Behavior
Applicant data is typically:
- Pulled on a scheduled cadence
- Incremental, based on status or date changes
Common Cadence Scenarios
Report‑based integrations (e.g., RaaS / Workday):
- Daily or multiple times per day, based on report availability
API‑based integrations:
- Multiple times per day or daily
- May appear near real‑time, but updates occur on a defined schedule
SFTP / Flat‑file integrations:
- Typically daily
- Some customers use nightly or weekly schedules depending on ATS capabilities and data volume
Impact of ATS Configuration Changes
Changes in the ATS can directly impact applicant integrations.
Customers should notify Radancy before making changes such as:
- Modifying workflows or stages
- Renaming statuses
- Changing API users or permissions
If changes are made without notice, Radancy may need to:
- Re‑evaluate mappings
- Perform additional troubleshooting
- Apply remediation to restore expected behavior