What should I do if my candidates’ sources aren’t being tracked in Greenhouse?

How does Greenhouse track candidates’ sources?

Greenhouse tracks the source of your candidates using tracking links. A tracking link is a link made up of your job board or job post URL (e.g. https://example.com/jobs) and an appended Source Token that identifies the source of the candidate. The Source Token will be a combination of numbers and letters that Greenhouse will generate when a new source is added to your account. When a tracking link is generated, Greenhouse automatically appends the Source Token to your job board or job post URL in a parameter that follows the format “gh_src={TOKEN}”. For example, the tracking link for the job board on example.com might look something like this: https://example.com/jobs?gh_src=abcdef.

In order for Greenhouse to effectively track the source of your candidates, the Source Token will need to be included in the URL of the job application page. If the Source Token is dropped from the URL when the candidate is redirected to the application form, Greenhouse won’t be able to track the source of the candidate.

Learn more about how tracking links work here.

 

Tracking Sources across Job Board Integration Options

If you generated a tracking link in Greenhouse, the Source Token will automatically be appended to your Job Board or Job Post URL using the parameter “gh_src={TOKEN}”. For most job board types, if the Source Token is in the URL when the candidate applies, the Source of the candidate will be pushed back into Greenhouse. This will be the case if you embed your application form in a Greenhouse iFrame or if you redirect candidates to https://boards.greenhouse.io to apply.

Sometimes job boards drop the Source Token URL parameter when the candidate clicks links on the Job Board. On the page that holds the application form, check the URL for the parameter “gh_src={TOKEN}” to make sure that the Source Token is still in place.

 

If the candidate is redirected to https://boards.greenhouse.io to apply (Options 1 and 3):

With Job Board Integration Option 1 and Option 3 candidates are redirected from your website to a Greenhouse-hosted application page to apply. The URL of the Greenhouse-hosted application page will include the job board token (typically the name of your company) and the Job ID for the specific job.

For the Source of the candidate to be tracked correctly, the Source Token needs to be passed from your careers page URL to the URL of the application form on https://boards.greenhouse.io. For example, if the Source Token was “abcdef,” the full application page URL might look something like this: https://boards.greenhouse.io/example/jobs/12345?gh_src=abcdef.

If the Source Token is not present in the application URL as in the example above, we recommend reaching out to your web development team. Especially with Option 3, it’s likely that the Source Token is not being passed to the application URL when candidates click the link to apply.

 

If the application form is in a Greenhouse iFrame (Options 2 and 4):

For customers who embed the application form in an iFrame on their own page using an Option 2 or an Option 4 job board, the Source Token will also need to be included in the URL of the application page. For example, the URL of the application page for a job with ID “12345” may look something like this: https://example.com/jobs?gh_jid=12345. In this case, the Job ID is included in the URL in the parameter “gh_jid={JOB_ID}.”

For Greenhouse to track the candidate’s Source, that URL also needs to contain the Source Token “gh_src={TOKEN}”. The full URL might look something like this: https://example.com/jobs?gh_jid=12345&gh_src=abcdef.

If the Source Token is not present in the application URL as in the example above, we recommend reaching out to your web development team. If your application form is hosted on different URL from your job board, you’ll first want to go Configure > Dev Center > Configuring Your Job Board to confirm that the Job Post URL has been configured correctly. You can read more about setting up Job Post URLs here.

 

If your page uses a custom application form generated through the Job Board API (Option 5):

If you’ve constructed your own customized application form through the
Job Board API (in an Option 5 job board), the developers who created the application form will need to send the Source Token to Greenhouse in the POST Application request. The Source Token should be included in the field “mapped_url_token” and should be pushed into Greenhouse along with the candidate’s application data. Read more about constructing the API-driven application form here.

 

What should I do if my candidates’ sources aren’t being tracked in Greenhouse?

If you suspect that your candidates’ sources aren’t being tracked into Greenhouse, try generating a Tracking Link and following the link your browser to ensure that the Source Token is included in the URL of the application page.

For example, if a careers page is using an Option 3 job board (i.e. is redirecting candidates to https://boards.greenhouse.io to apply), the Source Token would need to be pulled from the URL of the careers page appended to the application page URL on https://boards.greenhouse.io.

This means that the careers page would first need to copy the Source Token URL parameter “gh_src={TOKEN}” from the URL of the job board page (e.g. https://example.com/jobs?gh_src=abcdef):


Then, the page would need to append that parameter to the URL of the final application page (e.g. https://boards.greenhouse.io/example/12345?gh_src=abcdef):


If the Source Token is not present in the application URL as in the example above, we recommend reaching out to your web development team. You can share this FAQ with them to help demonstrate how the Source Token should be applied to the job application URL.

 

Please reach out to support@greenhouse.io with any questions!

Have more questions? Submit a request

Comments

Powered by Zendesk