Edit default and create custom Journey Targeting
Table of Contents
This page outlines how you can edit default Journey Targeting as well as create and manage custom Journey Targeting.
Edit default Journey Targeting flow
The account will require the Default Journey Targeting flow to be configured first. The default will target all requisitions that do not meet any other targeting rules for the Journey Targeting flow.
- Select the All Apps button in the top left corner of the page and then Settings in its drop-down menu.
- When the Settings page opens, select Job Manager under the Jobs section.
- Job Manager will then open to the Journey Targeting section.
- Select the Configure Default Journey Target button to set up the default Journey Targeting flow.
- Note: Targeting cannot be set for the Default Journey Targeting flow. Any requisitions that do not match the targeting criteria from custom Journey Targeting flow will be assigned to this default flow.
- In the Set Details section, enter the Name and External Journey Targeting ID.
- Select Save in the upper-right corner of the section.
- The Candidate Journey section will then open. Select the preferred Candidate Journey from the journey selector at the top of the section.
- Build the type of experience candidates will have at each stage of the selected journey by selecting the preferred conversations, forms, etc.
- Select Save in the upper-right corner of the section.
- In the lower-left corner, select the Publish button to publish the Journey Targeting flow.
Create a custom Journey Targeting flow
You can create additional Journey Targeting flows once you’ve configured the Default Journey Targeting flow. For custom Journey Targeting flows, you can set targeting rules based on Custom and Standard Candidate and/or Job Attributes.
Step #1: Create a new Journey Targeting flow
- From the Journey Targeting section of the Job Manager, select + Create Targeting in the upper-right corner.
- When the new flow opens, enter a name for it and an External Journey Targeting ID, if relevant.
- Select the preferred Candidate or Job Attribute from the Targeting Rules selector.
IMPORTANT NOTE WHEN TARGETING LOCATION ID: For this functionality to work, ensure to complete the following configurations:
- Toggle on Map Locations in My Jobs with Location ID from feed (Client Setup > Job Management > External ATS Job Management toggle/section > Map Locations in My Jobs with Location ID from feed toggle).
- Map the location from the job feed to the location in Location Management.
- Choose the preferred Matches option.
- Enter in your Input value.
- Add additional conditions by clicking the + And and + Or buttons and then building them out so that you can precisely target the desired candidates.
- You can build complex conditions in order to allow for more precise condition grouping. To do this, click the + Add Rule Set button to view an AND/OR switch and select your desired operator statement. From here, rule sets can then be further separated with an + AND or + OR operator.
- Select Next Step in the top right corner.
- Click Select the Candidate Journey.
- Select the preferred candidate journey and click Apply.
- Once selected, you will see the journey statuses and the content to be assigned. Select the default options for each status.
-
Notes:
- Only Custom and Dynamic Conversations can be used in Journey Targeting.
- The targeting rules set for each stage of the Candidate Journey will determine the candidate’s outcomes, including those set for the selected conversation (Screening and Actions will not work here). Learn how to utilize Dynamic ATS Conversations with Journey Targeting here.
- You can view the number of remaining required tasks on the counter on the top right corner of this section.
-
Notes:
Step #2: Configure alternate targeting
You can add alternate targeting for each stage so you can target certain conversations, forms, etc. to send to candidates for different jobs at different stages. When targeting requisitions, it will follow the targeting rules for the Journey Targeting flow and the targeting rules set on the stage.
- Select + Add Alternate [component] under the stage's default action.
- For example: You want candidates applying to “Marketing” part-time jobs to receive a different conversation. You can add targeting that says IF = JOB TITLE contains Marketing, then Send Alternate Conversation.
- Note: Alternate targeting on each stage can be configured for both Custom and Default Journey Targeting flows.
- When targeting is added, the total targeted requisitions will update in the top right.
- Once targeting has been set and no errors exist, the alternate targeting will display on the Journeys page. This can be edited or removed from the action menu, or ellipses.
- Select Save & Publish.
Live Job Data & Alternate Targeting Logic:
All alternate targeting for Journey Targeting references live job data rather than the applied data captured at the time of a candidate’s application.
- Future Journey Stages: Updates to job data only apply to future journey stages and will not alter any journey stages that have already been completed. Note that live data updates do not change the candidate's initial journey assignment, only the alternate targeting outcomes within that journey.
- Disabled Jobs: When a job is turned off, Paradox stores and references the last captured live job data. This ensures candidates remaining in the workflow receive consistent information despite the job's disabled status.
- Data Retention: If a job is deleted, Paradox retains the job data package (JDP) for 30 days for any active candidates. If a location is removed or deactivated, Paradox references the Hiring Team of the last candidate who applied to ensure tokens remain accurate in the Candidate Summary and within sent content.
Journey Targeting errors
Errors and/or a toast notification will display when the following occurs:
- Targeting Rules between two Journey Targeting flows are duplicated and requisitions are matched by the Targeting Rules (Job Attribute).
- Targeting Rules between two Journey Targeting flows are duplicated but no requisitions are matched by the Targeting Rules (Job Attribute).