Enhanced job ID
Updated at August 20th, 2026
Table of Contents
We are excited to announce an important update to Job ID's for our Conversational ATS clients. This new ID structure brings improvements that will benefit both new and existing clients.
Please carefully review the details below, including steps to ensure a smooth transition for existing clients.
What’s new?
New Job ID Structure:
- New Clients: All new clients should now use the unique and versioned Job ID structure. Please enable for all new clients to be implemented moving forward.
- Existing Clients: Existing clients can migrate to the new Job ID structure, but this requires careful review to ensure there are no dependencies on the old ID structure.
- New Structure: P24-XXXXX-X
- Previous Structure: PDX_XXX_XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX_XXXXXXXX
Why did we make this update?
We introduced Enhanced Job IDs because the previous ID lacked unique job identifiers. For multi-location jobs, we had to append the location ID to the end of the job ID, which created challenges when evaluating candidates and their data.
Example: In the Job Builder, the Crew Team Member job is created and assigned 5 locations. In My Jobs, each postings displays today as:
-
Location 1:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_001 -
Location 2:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_002 -
Location 3:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_003 -
Location 4:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_004 -
Location 5:
PDX_JTC_B2C3BA90-3A15-441D-AFD9-96D17E0CFEC2_005
Our clients requested a solution where each job posting in My Jobs has its own unique ID, making it easier to reference and track jobs independently. With this update, every job posting now has its own distinct Job ID, improving clarity and data management.
Example: In the Job Builder, the Crew Team Member job is created and assigned 5 locations. In My Jobs, each posting will now display as:
-
Location 1:
P1-10862-1 -
Location 2:
P1-38484-1 -
Location 3:
P1-58673-1 -
Location 4:
P1-45775-1 -
Location 5:
P1-55757-1
Key benefits of enhanced job IDs
-
Unique & Shortened IDs:
The new Job ID format is easier for clients to reference internally within My Jobs and can also be used externally on Career Sites and Job Boards. -
Consistent Core ID:
The core part of the Job ID remains the same, providing consistency, while the versioned part of the ID allows flexibility. -
Version Logic:
The Version ID is appended to the core Job ID and updates each time the job is toggled open or closed. This ensures that updates (e.g., status changes) are tracked without creating a completely new Job ID, simplifying job management and reporting.
Important considerations for existing clients
When migrating existing clients, it is essential to evaluate any dependencies that may rely on the old Job ID (PDX value). This includes third-party systems such as job boards, career sites, or advertising platforms. If these dependencies are not properly accounted for, the client’s job mapping may break, disrupting ongoing job campaigns and processes.
Steps to confirm no client dependency on the previous job ID structure
Before enabling the Enhanced Job ID for existing live clients, follow these steps:
-
Review Third-Party Integrations with your client:
Check for integrations that depend on the currentPDXJob ID format, such as:- Job Boards (e.g., Indeed, LinkedIn)
- Career Sites or external job portals
- Advertising Campaigns currently running on the old Job ID format
- Custom Reports or Dashboards dependent on the current Job ID structure
-
Analyze Built Logic Outside of Paradox with your client:
Identify any internal workflows, automation, or scripts the client may have that rely on the old Job ID format. These workflows will need to be updated before migration. -
Client Approval and Migration Confirmation:
- Discuss the change with the client and ensure they are fully prepared for the migration to the new Job ID format.
- Confirm that the client does not have any dependencies on third-party systems or custom logic tied to the old Job ID.
- If dependencies exist, work with the client to create a migration plan and establish a timeline to ensure a smooth transition to the new Job ID format.
Configuration steps
If client dependencies have been confirmed or you are building a NEW client account, follow these steps to enable enhanced job IDs:
- Navigate to the Job Management section in Client Setup.
- Toggle on Enable Unique and Versioned Job ID to activate the new job ID format.
- Disable the Job ID Refresh on Job Publishing toggle if jobs are being posted to job boards. This ensures the job ID does not refresh every time a job is published, maintaining consistency across external platforms.
- Click Save.
Impact
Once the configuration is complete, the following updates will be reflected across the platform:
- Apply URLs will use the new Job ID format.
- The job ID displayed in My Jobs, Candidate Profiles, and other job references will be updated to the new Job ID format.
- Job feeds (e.g., Custom Feeds, Master Feed, Paradox Standard Feeds) will now reflect the new Job ID structure.
- Reporting & Analytics will display the new Job ID values, ensuring all tracking and metrics align with the updated structure.
Client one-pager
Provide your client a PDF of this document to provide them more information on this feature.
FAQs
Are all new clients required to use the new job ID structure?
Yes, all new clients should automatically use the new, unique, and versioned job ID format. This will allow for a more seamless transition and experience for your clients.
Can existing clients migrate to the new job ID format?
Yes, but you must confirm that the client does not have any third-party or internal dependencies on the old job ID structure before making the switch.
As noted above, when migrating existing clients, it is essential to evaluate any dependencies that may rely on the old Job ID (PDX value). This includes third-party systems such as job boards, career sites, or advertising platforms. If these dependencies are not properly accounted for, the client’s job mapping may break, disrupting ongoing job campaigns and processes.
Where will the job ID be updated in the system?
The new job ID will be reflected in the Candidate Profile, My Jobs, Apply URLs, Job Feeds, Reporting, Analytics, and any other areas that reference job IDs.
What should I do if a client has dependencies on the old job ID structure?
If there are dependencies, you must create a migration plan and work with the client to adjust any affected systems or workflows before enabling the new job ID structure. If you have any questions, please reach out to Solutions or Product for assistance.
How does the versioned job ID work?
The versioned job ID allows changes to job postings when the job is toggled on/off without generating a completely new job ID. This helps clients track changes while maintaining consistency in job references.
How can we verify that no job postings will break on external sites like Indeed or LinkedIn?
Before making any changes, ensure that external job boards are not reliant on the old Job ID structure by consulting with the client. It may also be good for the client to review the Job ID change with their contact at the job board. If ad campaigns or job feeds depend on the old structure, those systems will need updates to accommodate the new Job ID.
The update will likely also result in a new job posting. Please inform your clients this change will need to be made in accordance to the job boards reposting policies.
Will there be any impact on analytics or reporting?
Yes, the new Job ID will be reflected in all analytics and reporting tools, providing a more streamlined and consistent structure across data points.
What happens if the new job ID isn’t compatible with a client’s current system?
If incompatibility is detected, work closely with the client to update their system or create a workaround. In some cases, clients may opt to stay on the legacy ID format if necessary, but migration should be encouraged when possible.
Can a client revert to the old Job ID structure after migration?
No, once the migration to the new Job ID structure is complete, reverting to the old format should not be allowed. Please ensure the client is fully prepared before initiating the change.
Will the new job ID affect existing candidates?
No, existing candidate applications tied to jobs with the old Job ID will remain associated to the job and legacy job id. The new structure applies moving forward for future jobs and postings.
Will Filters and Segments that are currently configured using the Req ID migrate with the new Job ID structure?
Segments built today may be supported, but they will not sync new candidates associated to the new job ID appropriately. It is recommended that segments are re-configured because the Job ID structure that existed previously was the same for multiple postings.