Journey Targeting will be utilized for customers who manage their jobs in an integrated ATS but who want to utilize Conversational ATS functionality (forms, offers, assessments, etc). The goal of Journey Targeting is to allow your team to customize your candidate experience based on business rules and requisition targeting configured in this feature. 

Use cases

• Teams who want a customized candidate experience even though their jobs are managed in an external ATS.

Best practices for implementation

Important things to keep in mind when utilizing Journey Targeting:

• Journey Targeting Targeted Requisition Count: Currently, the targeted requisition count column in the Journey Targeting list view only includes a count of “Active Jobs” for each Journey Targeting flow created (jobs targeted to turn on or marked as Disable Application).
• Updated Job Status Behavior: When a job is turned on or off in My Jobs, all jobs sharing the same requisition ID will have their job status updated to match. This behavior will occur regardless of whether location mapping (Map Locations in My Jobs with Location ID from feed) is enabled or disabled, ensuring all jobs with the same requisition ID are managed as a group.
  • Example: The user navigates to My Jobs and turns on the Petroleum Engineer job. There are three other Petroleum Engineer positions in the feed that share the same requisition ID.
  • Result: Turning ON the Petroleum Engineer job in My Jobs automatically updates the job status for all four positions, as they share the same requisition ID. 

Configuration

Learn how to configure this feature here.

Journey Targeting list view

You can see all of your Journey Targeting flows in the Journey Targeting list. There are four statuses for every Journey Targeting flow:

• Published
• Unpublished Changes
• Draft
• Archived

List actions

By hovering over a Journey Targeting flow in the list and selecting its action menu, or ellipses, you can select one of the following options:

• Edit – This will open the Journey Targeting Builder where you can make and publish any necessary changes.
• Archive – This will mark the flow as inactive and move it to the Inactive list.
• Delete – This will remove the flow from the list, it not already in use.

You can also hover over any of the values in the Requisitions column to see the number of targeted requisitions for open, closed, and external application jobs.

Reporting

The following legacy reports can be utilized for this feature:

• External Job Activity Summary

Permissions

By default, only Paradox Admins, Company/Account Admins, and Franchise Owners will have full access to Journey Targeting. Contact a user with full access to Roles and Permissions or your CS Representative to adjust this, as needed.

FAQs