JobTarget is Kula's job board aggregator — one integration that can distribute a job to many boards at once, for free (organic) or as a paid, sponsored placement, without you connecting each board individually.

One-time account setup

• Go to Settings → Career page and job boards → Job boards.

• Scroll to Job Board Aggregators and turn the JobTarget toggle on.

This is purely an account-level connection step — you don't need a separate JobTarget account or login of your own; Kula handles that behind the scenes.

Posting a specific job through JobTarget

• Open the job and go to its Job Boards tab.

• Find the JobTarget card and toggle it on for that job. This enables both free (organic) and paid postings for that job together — you don't choose free-vs-paid at this step.

• Turning it on opens a Manage panel — this is JobTarget's own marketplace experience embedded in Kula, not something Kula builds or hosts, which is why its look and feel can change independently of Kula releases.

• Inside the Marketplace, you can browse available boards under Home; check My Favorite Sites or Contract Sites if your organisation has existing site relationships; see each board's price and posting duration for paid boards; and add the boards you want to your cart, review the summary, agree to the terms, and check out.

Free/organic postings go out to all of JobTarget's available free boards simultaneously — you can't currently hand-pick individual free boards the way you can add individual paid ones to your cart.

Easy Apply is not supported

• JobTarget offers an "Easy Apply" posting type for boards that require it, but Kula does not currently support it. This isn't a settings toggle you're missing — the option was deliberately removed from Kula's JobTarget integration in 2024 because the feature was never built.

The practical impact: some job boards reachable through JobTarget (SEEK is a confirmed example) will only accept Easy Apply postings. Without Easy Apply, JobTarget can still post the job, but it collects applications on its own side and forwards them to you by email instead of routing them into the candidate's application in Kula. That means those applications won't show up in your pipeline automatically, and you lose the usual tracking, source attribution, and stage automation for them.

If you're evaluating a JobTarget package or board that specifically markets Easy Apply support, confirm with JobTarget (or Kula support) whether that board will work in a degraded, email-forwarding mode without it, rather than assuming it will flow into Kula normally.

Good to know

• Toggling off a free JobTarget campaign can deactivate its linked paid campaign too, and re-enabling may prompt for payment again. A real customer case showed this exact behaviour — turning off the free LinkedIn campaign also killed the paid one, with no separate control to keep them independent. If you only mean to pause one side, check both after making the change.

• Paid JobTarget packages that promise a specific number of "matched candidates" have, in at least one real and currently unresolved case, significantly underdelivered against that promise (a customer's LinkedIn package promised up to 350 matched candidates; they received a small fraction of that). If a paid package's results look far off from what was advertised, that's a known, currently-open issue to raise with support rather than something to assume is user error.

• You generally cannot pick individual free/organic boards — enabling organic posting distributes the job to all of JobTarget's available free boards at once, not a chosen subset.

• JobTarget applications sometimes need a moment to attribute correctly in reporting. Real cases have shown mismatched or missing contact counts when filtering by JobTarget-sourced channels (e.g., "JobTarget via LinkedIn Limited Listing Organic") — if your source report and your raw contact list disagree, treat the raw list as more reliable and flag the discrepancy to support.

• "User already exists" is a known JobTarget configuration error, seen when trying to enable the integration or configure it for certain roles. If you hit this exact error, it's a recognised issue rather than something wrong with your account setup — contact support.

• The Marketplace's look has changed at least once without a corresponding Kula release — it's hosted by JobTarget, not Kula, so UI changes there aren't announced in Kula's own release notes. If it looks different from a screenshot or prior walkthrough, that's expected.

FAQ

• What's the difference between "JobTarget via LinkedIn Promotion" and just "LinkedIn" in my source report? LinkedIn (organic) is the free, direct path — candidates who found the job on your LinkedIn company page. JobTarget via LinkedIn Promotion is a paid/sponsored placement distributed through JobTarget. Same platform, two different posting mechanisms, tracked separately.

• Does JobTarget support Easy Apply? JobTarget itself offers Easy Apply as a posting type, but Kula doesn't support it. Boards that require Easy Apply (like SEEK) will still accept the posting, but applications come back to you by email from JobTarget rather than flowing into the candidate's application in Kula.

• Can I choose exactly which free job boards my organic posting goes to? Not currently — organic/free postings go out to all of JobTarget's available free boards at once rather than a hand-picked subset.

• I turned off my free campaign and my paid campaign stopped too — is that expected? It's been observed in at least one real case, yes. If you only want to pause one side, check both campaigns after making a change rather than assuming they're independent.

• I paid for a package that promised a specific number of matched candidates and got far fewer — what do I do? This has been a real, reported issue for at least one paid LinkedIn package through JobTarget. Contact Kula support with your job link so it can be raised with JobTarget directly rather than assuming it's expected behaviour.

Need help?

If a JobTarget posting isn't behaving as expected — applications aren't flowing in, a paid package underdelivered, or you hit a configuration error — contact Kula support with the job link and account name.