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.

​

Hiring

The Hiring view gives you detailed visibility into ATS data as inploi receives and processes it. Use it to review application events, check matching quality, and investigate discrepancies between inploi and your ATS. Access the Hiring view by clicking Insights in the top navigation in Studio, then selecting the Hiring tab.

​

Tabs

​

ATS Event Logs

A day-by-day breakdown of ATS activity, showing the number of applications, shortlists, interviews, offers, hires, and rejections recorded in your ATS for the selected date range. Use the Display data based on toggle to switch between:

• Date of Activity — shows outcomes on the date the stage change occurred in the ATS
• Date of Application — attributes all outcomes back to the candidate’s original application date

Use the Download button to export the data.

​

Application Logs

A row-level view of every ATS application inploi has received, including the ATS application ID, application date, job details, and matched source. Use the filter toggles to show only applications matched to an inploi job ID, or only those matched to an inploi flow submit event. Use this tab to investigate individual unmatched applications. The Download button exports the full list, including raw application IDs, which can be cross-referenced with your ATS.

​

Matching to inploi

A summary of how well inploi is matching ATS applications to jobs and sources for the selected period: The time-series table below shows these figures broken down by day, week, or month. Use this tab to spot trends or sudden changes in matching quality.

​

Days to Outcome

Average number of days from application to each hiring stage — shortlisted, interviewed, offered, and hired — for the selected period. The distribution chart shows the spread of time-to-hire across all candidates.

---

​

Troubleshooting

Use this section when numbers in inploi don’t align with your ATS. Before investigating, it helps to understand the matching process and date attribution logic covered in How ATS data sync works.

​

The total application count doesn’t match our ATS

First confirm you are comparing equivalent data:

• Check the date range — ensure inploi and the ATS report are using the same date range
• Check the date model — inploi defaults to date of application; most ATS reports show current or point-in-time status. These will naturally produce different numbers for the same period.
• Check for applications created directly in the ATS — applications that didn’t go through inploi will appear in the ATS but not in inploi’s attraction data

If totals still don’t align after confirming the above, use the Application Logs tab to download the raw application IDs for the period and compare them against an ATS extract at application level.

​

Matched to job % is lower than expected

A healthy job match rate is typically 95% or above. If it drops below this:

• Jobs not synced to inploi — inploi only holds applications for jobs it has synced from the ATS. Applications for jobs outside the sync scope will not match. Review which jobs are currently being synced.
• Candidate moved between jobs in the ATS — moving a candidate to a different role creates a new ATS application ID. inploi cannot link this new ID back to the original application.

Use the Application Logs tab and filter for applications without a Job ID to identify the affected records.

​

Matched to source % is lower than expected

A lower source match rate means inploi can attribute applications to jobs but not to a specific source or channel. This affects the Sources view and source-to-hire reporting. Common reasons:

• Applications not submitted via inploi — if candidates applied through a direct ATS link or another route, there is no inploi application event to match against
• ATS application ID not captured at submission — in some cases the ATS may not return an application ID in its response at the time of submission

To investigate, download unmatched application IDs from the Application Logs tab and ask your client whether any applications in that period were created outside of inploi. This is often the explanation and should be confirmed before escalating further.

​

When to escalate

Escalate to the inploi team if:

• Matching rates have dropped suddenly compared to previous weeks, rather than reflecting a known baseline
• You have ruled out client process as a cause and cannot explain a pattern of unmatched applications

When escalating, include a download from the Application Logs tab covering the affected period. This gives the team the application IDs needed to investigate efficiently.