This article explains how career page analytics work and how events such as page visits and job applications are tracked. RecMan's in-house analytics tool collects and manages this data.
How it works
Each career page automatically includes a front-end tracking script. This script is responsible for capturing information about user interactions (for example, visits, clicks, and applications).
When a user visits a career page, the script performs several key actions:
1. Generates a unique visitor ID
- Each visitor gets a unique identifier: ra_visitor_id, which is unique per browser and device. If a visitor uses a different browser or device, a new ID will be generated.
- This ID is stored in the local storage of the visitor’s browser.
- It ensures that multiple visits from the same browser are counted as a single visitor session.
2. Tracks events on the page
- The script records every user action (such as viewing a page, clicking Apply now, or submitting an application).
- Each event is linked to the visitor’s unique ID.
3. Prevents duplicate counting
- As long as the local storage keeps the same visitor ID, refreshing or revisiting the page does not increase the visit count.
- If the local storage is cleared, a new visitor ID is generated, and subsequent visits are treated as new ones.
If the application is started but not completed (for example, due to an error or missing information), only the apply_now event will be recorded. The apply_now event shows intent to apply, while the applied event confirms a successful application.
Each event entry includes:
- Action type. For instance: visit, apply_now, applied, application_complete
- Job post ID
- Visitor ID
- Candidate ID and Job Application ID once the application is completed
In summary: Our career page analytics system provides a reliable and detailed view of candidate interactions — from viewing a job post to completing an application — while maintaining accurate tracking through unique browser identifiers.