Job distribution
Every live role, in front of the people who fit it
One connection to your ATS sends every live role to the channels candidates already use.
From your ATS, onceWhat you get
Feeds and segments as standard.
Job distribution reads live roles from your ATS and does the placing. Two things ship as standard, and job sponsorship is an add-on your team switches on for the roles, regions or brands that need it.
Job feeds Live
Every live role, from your ATS, out to Google, Indeed, Adzuna and the job aggregators as listings where candidates already search. Works against any ATS that exposes a list of live jobs.
Segments Live
Group roles by what they are and where they are, and let the groups update themselves as jobs open and close. A hard-to-fill kitchen role in one city gets more budget than a role that fills itself.
Paid reach where a role needs it.
Proof
What changed when wagamama moved its spend.
63%
27%
“They are reaching talent pools we couldn’t reach on our own.”
Attributed to source
Every application carries the channel that brought it.
Spend and outcome sit on the same row: which channel brought each application, what it cost, and what happened next, in Studio and back to your ATS where technically possible.
ApplicationsIllustrative people and figures
| Candidate | Role | Channel | Cost | Outcome |
|---|---|---|---|---|
| Maya OkaforChef | ChefManchester | Indeed | £4.20Hired | Hired |
| Josh CarterKitchen porter | Kitchen porterManchester | £2.90Interview | Interview | |
| Amara DialloTeam leader | Team leaderLondon | Sponsored | £6.10Screening | Screening |
| Darren HoltCustomer assistant | Customer assistantBristol | Adzuna | £3.40Applied | Applied |
The alternative
Job board spend with no attribution.
Most teams buy job board credits, post by hand and find out at renewal what they think it delivered. Nobody can say which channel brought the hires, so the budget is defended by habit. Job distribution places every role from one connection, prices the paid part on applications rather than clicks, and attributes every applicant and every hire back to source, so the number is there before the renewal conversation is.
FAQ
Yes. inploi tracks every candidate from first click through to application, showing which source, campaign, or channel brought them. This data is visible in Studio and can be segmented by job, location, brand, or date range. Attribution data is sent back to your ATS where technically possible.
Google, Indeed, Adzuna and the job aggregators as feeds, with job sponsorship on the paid boards as an add-on. One connection to your ATS feeds all of them, and every application is attributed back to the channel that brought it.
A list of live jobs, which is what the feed reads; it works against any ATS that exposes one. Completed applications land in your ATS the way they do today, with their source attached where technically possible.
Budget follows applications, not clicks, and is set per segment, so it moves towards the roles that are short and away from the ones that fill themselves. Your team sets the segments and the limits in Studio.
It is the same channels, placed from one connection, with every application attributed to source so you can see what each channel returned.
Agents do the admin. Humans do the hiring.
See what inploi would take off your team.
The hiring experience audit takes four minutes.