VONQ uses a set of tracking events to capture the behavior of the candidates on customer’s career site. Each of those serves a different purpose and monitors a different aspect of the behavior as well as relevant data.
Page View (1) - Capturing a generic page view, storing referral URL, browser characteristics and other metadata that might be of interest.
Step View (2) - Capturing a visit on a particular step of the application process funnel such as viewing the Job Description, the Application form or successfully applying via the application form.
Depending on the value of “label” field of the step_view event object this might be:
2.1 job-description - the candidate is viewing the job description
2.2 application-form - the candidate is viewing the application form
2.3 application-success - the candidate has successfully submitted the application form
2.4 career-page - the candidate is browsing a page which is part of the career section of the customer’s website
Page Ping (3) - Measuring the time spent by the user on the page with a 10 seconds resolution.
Job board click (4) - Capturing the source channel (Job Board) and the VONQ campaign from which the candidate is coming. Used to attribute campaign and channel performance.
Applicant Conversion (5) - Fired upon a successfully submitted application form.
In order to track the candidate journey, you will need to place our Javascript trackers on a few specific points of interest.
The steps of the applicant journey are:
The Career Page - The page where the jobs are listed
The Job Description - The detailed description of the job
The Job Application Form - The application form where candidate data such as Name, Location, CV etc., is submitted
The Application Success - The page which is shown after successfully validated and submitted candidate details
Each step gets its own tracking code which basically differs by the rest only by the type of where the type of the page or, to be more specific, the event being tracked is defined.
Tracking code snippets for each of those events that capture a particular “step” or phase of the journey can be found on the “Getting Started Page” in the platform.
Usually, one can just copy & paste the code snippets directly from the platform, as they will be prefilled with all the necessary information for attributing the traffic and data to the customer’s account, but not all career sites are equal so additional adjustments to the code can be expected. An example of this might be an SPA (Single Page Application) application that does not have the traditional unique pages, located on a fixed individual URL, but views inside the browser that are generated entirely by business logic at the frontend.