🚧
Disclaimer
This help article is provided to explain how to use a cookies consent manager with Recruit's Careers API. This should not be used and/or considered as legal advice. You should contact your attorney to seek legal advice with respect to the use of cookies.

Recruit uses cookies to attribute candidates to the sources that referred them to the company's careers website, such as job boards and company employees who referred their friends (for more information about how source tracking works see this page). Applicable privacy, spam, marketing and/or cookie laws and regulations may require you to implement a consent mechanism in order to legally create cookies. If you wish to give website visitors the option to accept or reject cookies, you can use a consent manager tool.

Set up the cookie consent manager

Ensure that you are using the most up-to-date version of the embedding code from Recruit. If you use the embedding code directly then you can find the latest version here and if you use the WordPress plugin see the latest version here.
Use the settings options of your cookie consent manager to ensure that all cookies created by Recruit are classified properly, as defined in the Cookie policy for website visitors. Improper classification might prevent the application form from being embedded or cause the tracking cookies to be created without being accepted.
Some cookie consent managers require the tracking script to be embedded differently, so that it can be enabled only if the visitor accepts the use of these cookies. Please refer to the documentation of the cookie consent manager that you use to see if this is required and if so, which attributes should be defined for the tracking script. The examples below are provided for reference for Cookiebot and Termly.

<!-- Comeet source attribution -->
<script type="text/plain" data-cookieconsent="statistics">(function(){var a=function(){window.COMEET.set("candidate-source-storage",!0)};window.COMEET?a():window.comeetUpdate=a})();</script>

<!-- Comeet source attribution -->
<script type="text/plain" data-categories="analytics">(function(){var a=function(){window.COMEET.set("candidate-source-storage",!0)};window.COMEET?a():window.comeetUpdate=a})();</script>

What happens if a candidate doesn't accept the use of cookies?

When a candidate doesn't accept (or actively rejects) the use of cookies, it’s not always possible to attribute the candidate to the referring source.

The candidate will be attributed to the referring source only if they submit the application form immediately after clicking the link to the position page from the referring source, without browsing through other pages on the company's career website.
When the candidate does browse through pages on the company's career website before applying for a position, the source of the candidate in Recruit will be the domain of the company's career website (eg. "www.acme.com").

📘
Types of cookies that can be rejected
Note that only cookies used for tracking the candidate's source – categorized as "Statistics cookies" – can be rejected by the candidate. Cookies categorized as "Essential / necessary" cannot be rejected. For more information and for the complete list of cookies see Cookie policy for website visitors.