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.
Where your roles go
On the boards candidates already search.
Job feeds put every live role on Google for Jobs, Indeed, Adzuna and the aggregators. Job sponsorship adds paid reach on the boards, CV-Library, Totaljobs and ZipRecruiter among them.
Paid reach
Deeply connected to Appcast.
Sponsored roles run through Appcast, so they reach a long list of publishers, from the largest boards to the specialist ones a hard-to-fill role needs. We are not an agency: the budget is yours, and so are the numbers.
Reach beyond the big boards
A role that the large boards cannot fill goes to the specialist publishers that can, from the same connection to your ATS.
Bids that follow applications
Bids are placed automatically, role by role, and budget follows applications rather than clicks, set per segment in Studio.
Publishers held to account
Every publisher is judged on cost per application and, where your ATS shares outcomes, cost per hire. The ones that hire keep the budget.
Proof
What changed when wagamama moved its spend.
63%
27%
“They are reaching talent pools we couldn’t reach on our own.”
Source-to-hire attribution
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.
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 |
Every application, its channel
The careers site and the application record the source, campaign and channel of every candidate, from the first click.
Hires traced back to source
Where your ATS shares what happened next, each hire is traced back to the channel and publisher that brought them.
Cost per application, cost per hire
Every channel is judged on what it costs per application and per hire, not per click.
Budget moves to the channels that hire
The numbers are in Studio, by job, location, brand or date range, and go back to your ATS where technically possible.
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.
Managed service. For larger hiring programmes, a named expert from our customer success team runs your campaigns, publishers and budget on job distribution.
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 for Jobs, Indeed, Adzuna and the job aggregators as feeds, with job sponsorship on the paid boards, including CV-Library, Totaljobs and ZipRecruiter, 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.
Yes. Job distribution is deeply connected to Appcast, so sponsored roles reach its publishers, specialist boards among them. Every publisher is judged on cost per application and, where your ATS shares outcomes, cost per hire, in Studio.
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.
Let’s find the admin your team shouldn’t be doing.
The hiring experience audit takes four minutes.