How ATS data sync works
inploi connects to your ATS to retrieve candidate disposition data — application statuses, stage progressions, and hiring outcomes. This page explains how that data is retrieved, matched, and surfaced in Studio Insights.Daily sync
inploi performs an automated daily sync with your ATS. During each sync, application-level data is retrieved for all available candidates and stored securely in the data warehouse.Data is updated once per day. Changes made in your ATS after the daily sync will appear in Studio Insights the following day.
Matching applications to inploi
To attribute hiring outcomes to jobs, sources, and campaigns, inploi links each ATS application back to the corresponding inploi application event. This matching uses the ATS application ID — a unique identifier returned by your ATS when a candidate successfully submits an application via inploi. This ID is captured at the point of submission and used as the link between the two systems. When a match is found, inploi can attribute the application — and all subsequent hiring outcomes — to the job, source, and campaign the candidate came from. Applications that cannot be matched are still recorded, but cannot be attributed to a job or source and will not appear in funnel or source-based reporting. See the Hiring view for guidance on monitoring and investigating unmatched applications.Why applications may not match
- Application created directly in the ATS — if a candidate applied through a route that bypassed inploi, there is no inploi application event to match against
- Candidate moved between jobs in the ATS — moving a candidate to a different job creates a new ATS application ID that cannot be linked back to the original
- ATS application ID not captured at submission — in some cases the ATS may not return an application ID in its response, meaning the link cannot be established
Stage normalisation
ATS stage names vary by system and configuration. inploi maps your ATS stages to a consistent set of stages used across all reporting:| inploi stage | Description |
|---|---|
| Applied | Application received |
| Shortlisted | Candidate moved to review or shortlist |
| Interviewed | Candidate invited to or completed an interview |
| Offered | Offer extended to candidate |
| Hired | Candidate accepted and marked as hired |
| Rejected | Application was unsuccessful |
| Withdrawn | Candidate withdrew their application |
How the ATS data is treated
When processing ATS data in the data warehouse, inploi applies deliberate rules so reporting is consistent, comparable, and attributable to jobs and sources. These design choices — together with the matching rules above — can mean that figures in Studio Insights differ from what you see in your ATS interface.Date attribution
inploi uses two date models depending on the reporting view: Date of application — all outcomes (shortlisted, hired, rejected, etc.) are attributed back to the date the candidate originally applied. This is the default in most Insights views and enables funnel analysis: for example, “of the 100 candidates who applied in January, how many were hired?” Date of activity — outcomes are shown on the date the stage change actually occurred in the ATS. This aligns more closely with ATS-style operational reports.A direct comparison between inploi and ATS data can produce different numbers if each is using a different date model. Always confirm the date range and date model before investigating a discrepancy.