Multichannel job distribution: reaching the right people
Why posting everywhere misses the point, and how feeds, segments and attribution put each frontline role in front of the right people.
Multichannel job distribution means sending every live role to the places candidates already search, from one connection to your ATS, and then putting extra reach behind the roles that need it. Done well, it is not about being everywhere at once: it is about knowing which channel brought each application, so the budget follows the people you hire rather than the clicks you bought.
That last part is what separates distribution from simply posting more. Plenty of employers are on every job board going and still cannot say which one delivered last month’s hires.
Why one channel is never enough
Frontline candidates do not all look in the same place. Someone hunting for a first job in retail might search Google on their phone. An experienced chef might go straight to a job board they trust. A student looking for summer work in leisure might start on an aggregator. If a role only appears in one of those places, you have quietly decided who gets to see it.
This is also where reaching a wider range of people starts. The simplest way to hear from candidates you have not heard from before is to be visible where they already are, and then make sure nothing on your side turns them away: a careers site that works on a phone, an application that does not assume a CV, and a site that meets WCAG 2.1 AA so nobody is excluded by the design. Reach without a front door that works just moves the drop-off somewhere else.
Why more channels is not the answer on its own
The instinct when a role is short of applicants is to add another board. It sometimes works, but it has two costs that are easy to miss. Every extra channel is something someone has to post to, check and pay for, often by hand. And without attribution, each new channel makes it harder to tell which of the others were ever working. The budget ends up defended by habit at every renewal.
The better question is not how many channels, but which channel for which role. A kitchen porter role in a busy city might fill from organic listings alone. A qualified chef in a smaller town might need paid reach. Treating them the same wastes money on one and underserves the other.
How job distribution works on inploi
Job distribution on inploi reads your live roles from the ATS and does the placing. Two things come as standard.
Job feeds send every live role out to Google, Indeed, Adzuna and the job aggregators as listings where candidates already search. They work against any ATS that exposes a list of live jobs, so there is nothing to re-key.
Segments group roles by what they are and where they are, and the groups update themselves as jobs open and close. That is what lets a hard-to-fill kitchen role in one city get more attention than a role that fills itself.
Job sponsorship is an add-on for the roles, regions or brands that need paid reach. Budget follows applications rather than clicks and is set per segment, so it moves towards the roles that are short and away from the ones that are not. Your team sets the segments and the limits in Studio.
Every application carries its channel
The part that makes all of this worth doing is attribution. Because inploi sits between the channels and your ATS, it can see which channel brought each application, what it cost, and what happened next. With analytics and attribution, that shows up in Studio and goes back to your ATS where technically possible. Spend and outcome sit on the same row, so the conversation at renewal starts from a number rather than a feeling.
wagamama is a good example of what changes when spend follows results. It moved its recruitment marketing onto job distribution and its whole application onto conversational apply, and over the year its cost per application fell 63% while recruitment media spend fell 27%, with a cost per application of £4.89 across 23,000+ applications. The wagamama story has the detail.
Where the careers site comes in
Distribution gets people to your roles; the careers site and the application decide whether they stay. A listing that lands on a slow page, or on a form that asks for a login and a CV, loses most of what the channel delivered, and the attribution will show you exactly that. The two work best together: distribution brings people to a role page that loads quickly, an application that adapts to the role and finishes in minutes, and an ATS that receives the result with its source attached.
What to do next
Start by listing every channel you currently pay for and asking which of them you could defend with numbers. If the honest answer is not many, the problem is less about reach and more about attribution. From there, look at which roles are consistently short and which fill themselves, because that split is where the budget should move first.
Our page on connecting spend to hires goes further into the attribution side, and you can read more about how careers sites and distribution work together under careers sites.
