This option gives customers the ability to specify Custom Source ID's for their boards in cases where our Pipeline ID (pipeline_id) will not work for sourcing. When the Custom Source ID's feature is enabled, you will see a new tab in that admin account that displays a list of allowed boards.
Getting Started in the Custom Source ID Section
Select Custom Source ID Advanced Settings; here you will see the list of boards that are allowed to your company. This is where you will enter your Custom Source ID's. Remember to Save.
Required Changes
In order for your new Custom Source ID's to be appended to the apply URL's, a {custom_source_id} token should either be included in the eQuest URL (by your ATS) or eQuest must configure the backend option to replace the the pipeline_id with the custom_source_id (assuming the ATS is sending the pipeline_id token.
backend company setting - must be handled by eQuest supportIf neither of these options work, eQuest may be able to configure the {custom_source_id} (or {pipeline_id}) so it's automatically appended to all including URL's. Contact eQuest support to determine if this option can be used in your case.
Scenarios Where Only Some Job Boards Use Custom Source ID
If only one more (of many job boards) require a custom source Id, simply omit custom source id values for those boards when configuring the Custom Source ID table (top screenshot).
If eQuest is configured to replace the pipeline_id with the custom_source_id but you want to bypass that logic and retain the pipeline_id in certain cases, toggle the "Ignore CSI Substitution" field in the board instance you'd like to override (Advanced tab).
URL Examples
Example 1: http://jobs.ats.com/1033/ASP/TG/cim_jobdetail.asp?partnerid=256&siteid=39&Codes={custom_source_id}&req=54239
Note: Custom Source ID can be used in conjunction with the other variableshttps://equesthelp.zendesk.com/hc/en-us/articles/25279192728475-URL-Variables
Example 2: http://jobs.ats.com/1033/ASP/TG/cim_jobdetail.asp?partnerid=256&siteid=39&Codes=12345&req=54239
In example 2 {custom_source_id} token was included in the eQuest 'candidate_response_url' for job board Dice (Pipeline ID "Dice"), with a Custom Source ID value of '12345'.
Setting Custom Source ID Per Board Instance
Many customers have multiple accounts at boards, such as LinkedIn.
Within eQuest you can apply a unique Custom Source ID to each board account/board instance.
You will find the board instance Custom Source ID field in the Advanced section. The top level value is Inherited based on the standard setup outlined above. To override that default, enter a value and Save.