Personal tools

Positions published externally

From Onlinehelp

Jump to: navigation, search

External job board

In the jobs overview on the external job board, potential applicants can search for an appropriate job, set up a job alert subscription, or apply for a job. The jobs advertised here are controlled from the expert view for HR experts/recruiters.

Overview of expert view in Applicant Management

Controlling and setting properties of the job board

You can use URL path identifiers and URL parameters (CGI parameters) to control and configure the properties of a job board and its postings, as well as how they are displayed.

  • The job board can be subdivided into sub-boards by branch office and by language (the language is controlled through an ID).
  • Each jobs overview can have its own design, its own welcome emails, and its own job alert subscription.
  • You can also activate unsolicited application links separately for each branch office. Applicants who are currently unable to find an appropriate job to apply to, but who would still like to express their interest in joining your company, can either submit an unsolicited application or set up a job alert subscription so they can be sure not to miss a single opportunity.

Info.gif Note:

  • To ensure that job postings on the external job board (/Jobs/All) have a consistent appearance, you should never activate more than one job posting image in configuration mode. If you are seeing duplicated images in the jobs overview on the external job board, it is recommended that you hide the second image via configuration mode.

URL structure and parameters for the job board

The job board is introduced by the URL path identifier “Jobs”, followed by multiple URL control elements and parameters.

“https: //recruitingapp-[CustomerID].umantis.com/Jobs/[LanguageID]?CompanyID=[ID]&DesignID=[ID]&lang=[ID]"

  • [CustomerID]: Corresponds to the customer ID (e.g. “133”).
  • [LanguageID]: Corresponds to the language ID for the publication contents (e.g.: 1 = German (Switzerland), 31 = German (Germany), 2= English, 3 = French, 4 = Italian, etc.; the list of all IDs can be found under Languages).
    In addition to language-specific job board calls, you can also call up the job board independently of language. To do this, use the All parameter (e.g. /Jobs/All).


Parameter:

  • CompanyID=[ID]: Corresponds to the ID of a specific branch office. For example, this parameter can be used to display only those jobs that are associated with the specified branch office. If this parameter is left out, then all externally-published jobs from all branch offices will be displayed. If you use job boards for individual branch offices, then you should use the parameter CompanyID=All for the global job board (resets all saved CompanyID parameters). If you would like to combine multiple branch offices in a single overview, then separate the IDs for those branch offices with the pipe character ‘|’ (e.g. CompanyID=19|15|1).
  • DesignID=[ID]: Corresponds to the page’s design ID. The individual designs must be created beforehand. The correct ID can be found on the page where it was created. This parameter is optional and can also be left out; in that case, the general external design is then displayed. DesignID=00 resets all saved DesignID parameters (to the default design).
  • lang=[ID]: Corresponds to the language of the environment. In umantis, the “label language” can be different from the “content language”. Each page can be displayed at any time in the relevant language (e.g. ?lang=ger or ?lang=eng) without affecting which content is drawn from the database. The list of all language parameters can be found under Languages.


Example URL:
https: //recruitingapp-123.umantis.com/Jobs/1?CompanyID=19&DesignID=1001&lang=eng

Notes:

  • The list of parameters begins with “?”, and individual parameters are separated with “&”. The parameters can be added in any order.
  • The square brackets “[” and “]” should be left out.
  • The “DesignID”, “CompanyID” and “lang” parameters have an ongoing effect, and only have to be specified once. The “lang” parameter is overwritten after login by the current user language.
  • Jobs can be published to the internal job board (intranet) in much the same way (but introduced by the URL path identifier “VacanciesIntraxData”).


URL structure and parameters for a posting

A posting is introduced by the URL path identifier “Vacancies”, followed by multiple URL control elements and parameters.

"https://recruitingapp-[CustomerID].umantis.com/Vacancies/[PositionID]/Description/[LanguageID]?lang=[ID]"

  • [CustomerID]: Corresponds to the customer ID (e.g. “133”).
  • [PositionID]: Corresponds to the job ID (e.g. “119”).
  • [LanguageID]: Corresponds to the language ID for the publication contents and the welcome email that is sent out (e.g. 1 = German (Switzerland), 31 = German (Germany), 2= English, 3 = French, 4 = Italian, etc.; the list of all IDs can be found under Languages).
  • lang=[ID]: Up until the moment when the user logs in, this parameter determines in which temporary user language the interface (labels, navigation) should be displayed. After the user logs in, this is controlled by the selected user language. Accordingly, you can distinguish the “label language” from the “content language” in umantis, and every page can be shown translated into the appropriate language at any time (e.g. ?lang=ger or ?lang=eng) without affecting which content is drawn from the database. The list of all language parameters can be found under Languages.

Source markings / parameters

Source markings allow you to identify applications that were received from other job boards or through a referral program. The ID assigned to each application allows its source to be uniquely identified. If you perform an Advanced Search, you can search by “Has source marking”. This search will return a list of all applications that have a source marking. You can also use Advanced Search to search for a specific source marking (e.g. “Has source ID”) or a specific unique ID.

  • ?tracking_id=[ID]
When using a referral program, the tracking ID is used to track applications to a given job. This ID can be an alphanumeric value.
Example URL: https://recruitingapp-[CustomerID].umantis.com/Vacancies/[ID]/Description/1?tracking_id=al76u7vtjqJ
  • ?srcID=[ID]
The source ID is a numeric value that provides information about the source of the application.
Example URL: https://recruitingapp-[CustomerID].umantis.com/Vacancies/[ID]/Application/CheckLogin/[langID]?srcID=123
  • ?srcText=[ID]
The source text is a value that provides information about the source of the application.
Example URL: https://recruitingapp-[CustomerID].umantis.com/Vacancies/[ID]/Application/CheckLogin/[langID]?srcText=abc
  • source=[ID]
The URL parameter “source” is used to transfer and track information about where applications come from. The URL parameter (CGI parameter) is used during the application process to pre-select the “How did you find out about us?” field in the application form. The applicant still has the option to set the value of this field manually. However, automatic preselection for this field leads to a significant improvement in the quality of data collection, since it covers the cases where the applicant does not explicitly fill in the field themselves.
Example: "https://recruitingapp-133.umantis.com/Vacancies/119/Description/1?source=indeed"
Note: In order for the correct list entry to be pre-selected on the application form when the URL parameter is transferred, the URL parameters must be saved as codes for the selection listHow did you find out about us?”.
When setting up and configuring job boards, the job posting URL you submit can be extended with this parameter as appropriate for each job board (e.g. “indeed” or “jobs_ch”). When an applicant uses the URL to view the job posting, the parameter is activated and the applicant source is recorded.
The “How did you find out about us?” selection list must also be visible on the application form in order for this parameter to have an effect.


Notes:

  • The list of parameters begins with “?”, and individual parameters are separated with “&”. The parameters can be added in any order.
  • The square brackets “[” and “]” should be left out.
  • The parameters for crawling our system can be accessed and modified via the following link (except for the internal job board):
https://recruitingapp-xxx.umantis.com/robots.txt
This link provides information about currently active crawling data:
Example:
user-agent: * # applies to all robots
Disallow: /VacanciesIntraxData/

Settings for Indeed Conversion Tracking

With the help of a so-called “conversion tracking code”, you can determine how many of your applications (“conversions”) come from people who found your posted job on Indeed. If you have activated tracking for Indeed, a conversion success rate will be shown in the display report for your Indeed account. This rate indicates how many of the applications you have received for one of your jobs come from Indeed.

Info.gif Please contact Indeed directly for your specific code.

Settings in umantis:
In order to use the Indeed Conversion Tracker, you must enter a conversion tracking code in umantis.
To do this, navigate to the branch office profile, then go to the “Basic information” section and enter the conversion tracking code under Confirmation code for Indeed .

Attention.gif Note that from the snippet received from Indeed, only the number is stored as the “Confirmation code for Indeed”.
Example: Snippet from Indeed: <img height=1 width=1 border=0 src="//conv.indeed.com/pagead/conv/2787332703034415/?script=0">
The only part actually stored is: 2787332703034415

Info.gif The conversion tracking code is used to inform Indeed that someone has applied to one of the jobs published on its platform. Indeed registers only the fact that an application was received, and does not collect any other applicant data.

Tips for search engine optimization (SEO)

The following tips are helpful for optimizing your job board for search engines like Google.

  • Integrate job board on your home page via automatic export and not via iframe
Reason: With iframe integration, Google does not recognize the page as part of the customer’s home page (different URL)
  • Mask the umantis system with an upstream proxy solution
This way, everything is defined from the customer’s website
  • If you want search engines (Google, Bing etc.) to index your jobs, they must be able to find them. Therefore, add appropriate “meta” tags in the Head section of the job posting. These meta tags are included in the example shown here, and can be adapted to your needs.

Info.gif Please also take note of the relevant notes and information on web tracking and the Robots Exclusion Standard in umantis.

Related topics

In other languages