You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Candidate Source Tracking: Custom URL using UTM

Summary:

My organization is keen on enhancing our candidate sourcing strategy, particularly in tracking the origins of applicants. We aim to distinguish between multiple Facebook posts related to events or various job listings to precisely identify which post led the candidate to apply.

In my efforts to implement this, I referred to the Oracle guide for guidance on utilizing UTM parameters. Consequently, I crafted the following URL structure, intending to capture source information. However, despite the URL functioning seamlessly during the application process, the source information does not appear within the recruiting interface or reporting features.

Example URL:

https://<client-domain>/hcmUI/CandidateExperience/en/sites/CX/job/41884/?utm_medium=Shared+job+posting&utm_source=Recruiting+Test+Post+Facebook+2023

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!