As a job board or recruiting agency, you want to make sure that your customers can see which candidates and applications came from your platform. The cleanest way to achieve this is usually by filling a special “source” field in the ATS with the name of your platform. We call this “application attribution”. Systems almost universally support some form of application attribution, but the exact implementation can vary. We’ve unified the application attribution process across all supported integrations.Documentation Index
Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt
Use this file to discover all available pages before exploring further.
Automatic attribution
When using automatic application attribution, sources are automatically attached to each application created through our API. You can enable the feature in the configuration section on the dashboard.Setup requirements
Some ATS integrations require additional setup to enable automatic application attribution. When this feature is enabled, we will prompt users to complete the setup process with customized flows for each ATS. On the end-user side, the setup process is usually a matter of going into the ATS’s settings and setting up a new source (some ATSs also call this differently). Let’s look at Personio as an example: After we’ve verified the credentials in the connection flow, we will prompt the user to set up application attribution. In the case of Personio, the user needs to create a so-called “recruiting channel” and then paste its ID.
Manual attribution
It is also possible to manually attribute applications by passing thesource
parameter when creating a candidate or
application. Please note that this
approach will only work for ATSs that allow passing a raw source string. For
others, where some setup work is required, automatic attribution must be used.