> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Disposition Data Sync

> How candidate outcomes and disposition data flow from your ATS into inploi for reporting and analytics.

After a candidate applies through inploi, their journey continues in your ATS. **Disposition sync** pulls hiring outcomes back from the ATS — application statuses, stage changes, rejections, and hires — so Studio Insights reflects what actually happened downstream.

## What it does

* **Retrieves** application-level disposition data from your ATS on a scheduled sync.
* **Links** each ATS application back to the original inploi application, so outcomes can be attributed to the job, source, and campaign the candidate came from.
* **Normalises** ATS stage names into a consistent set used across Insights reporting.
* **Surfaces** hiring funnels, conversion rates, and source performance in [Studio Insights](/studio/insights/overview).

Disposition sync is **ATS → inploi**. Your ATS remains the system of record for hiring decisions; inploi uses the synced data for analytics and attribution.

## How it works

<Steps>
  <Step title="Candidate applies via inploi">
    When [Submitting Applications](/integrations/ats/application-submissions) succeeds, inploi stores the ATS application ID returned by your ATS. This ID is the link between the two systems.
  </Step>

  <Step title="Hiring progresses in the ATS">
    Recruiters move candidates through stages, reject applications, extend offers, and mark hires — all in the ATS as usual.
  </Step>

  <Step title="Daily sync retrieves outcomes">
    inploi runs an automated daily sync with your ATS and retrieves disposition data for available applications.
  </Step>

  <Step title="Data is matched and stored">
    Each ATS application is matched to its inploi application event where possible. Outcomes are normalised, stored securely, and made available in Studio Insights the following day.
  </Step>
</Steps>

<Note>
  Disposition data is updated once per day. Changes made in your ATS after the daily sync will appear in Studio Insights the following day.
</Note>

## What data is synced

Typical fields retrieved during disposition sync include:

| Data                    | Purpose                                                          |
| ----------------------- | ---------------------------------------------------------------- |
| **Application status**  | Current state of the application in the ATS                      |
| **Stage progression**   | Movement through shortlist, interview, offer, and similar stages |
| **Hiring outcomes**     | Hired, rejected, or withdrawn                                    |
| **Disposition reasons** | Rejection or closure reasons where your ATS captures them        |

Exact fields and mappings depend on your ATS and are configured during **implementation**.

## Where you see it

Synced disposition data powers reporting across Studio Insights — particularly the [Hiring view](/studio/insights/hiring), funnel analysis, and source attribution. For a full explanation of matching, stage normalisation, date models, and funnel logic, see [How ATS data sync works](/studio/insights/faqs/how-ats-data-sync-works).

## What to expect

* Outcomes for candidates who applied through inploi should appear in Insights within a day of the change being recorded in the ATS.
* Applications created directly in the ATS, or moved to a different job after applying, may not match back to an inploi application and will not appear in source- or funnel-based reporting.
* If stage names look wrong or counts differ from your ATS, confirm you are comparing the same date range and date model — see [How ATS data sync works](/studio/insights/faqs/how-ats-data-sync-works#date-attribution) before raising a discrepancy.
* If something looks wrong, contact your Customer Success Manager. inploi can review sync logs and application matching.

<Warning>
  Disposition sync depends on a successful [Submitting Applications](/integrations/ats/application-submissions) and a captured ATS application ID. Without that link, inploi cannot attribute downstream outcomes to the original application.
</Warning>

<Note>
  Stage mapping and sync configuration are set during implementation.
</Note>

<Snippet file="ats-managed-integration.mdx" />

<Snippet file="contact-support.mdx" />