Location mapping helps Paradox accurately process and manage job location data from external ATS job feeds. When enabled for your account, this feature ensures our Location Management records reliably link to job feed location data.

Use cases

• Location Mapping is crucial for external ATS customers who rely on a configured Master Feed to import job data into Paradox. It is beneficial in scenarios where:
  • Your external ATS provides varying formats of location data (e.g., full addresses, city/state, or only a location ID).
  • Teams need to maintain a consistent and accurate set of job locations within Paradox's Location Management system.
  • Teams want to reduce manual effort in correcting job location discrepancies.

Configuration

Users with full access to Client Setup can complete the following steps.

Step #1: Ensure the master feed is configured

Work with your CS Representative to ensure that your master feed is configured accurately.

Step #2: Enable in Client Setup

1. Select All Apps in the top left corner of the header and then Settings from its drop-down menu.
2. Select Client Setup under the Paradox Tools section.
3. From the left panel of Client Setup, scroll down to and open the Job Management section.
4. In the External ATS Job Management section, enable the Map Locations in My Jobs with Location ID from Feed setting.
5. Save the page.

Overview of the location mapping process

The location mapping process prioritizes finding a precise match for each job's location data.

The following steps below detail the process for matching a job feed’s location data to a record in Location Management.

1. Prioritize Location ID Match
   • The system uses the provided location ID from the job feed to find an existing location record in Location Management.
   • Outcome:
     • If a match is found, the job is linked to this existing Location Management record.
     • If no match is found (either no Location ID was provided or the provided Location ID didn't match), the system moves to the next step.
2. Standardize and Search by Address
   • If no match was found using the Location ID, the system takes the job’s full address information (street name, city, state, country, ZIP code, location name).
   • This address data is then standardized to ensure consistency. This standardization improves the chances of finding a match.
   • The system then searches for an existing location record in Location Management using this standardized address.
   • Outcome:
     • If a match is found, the job is linked to this existing Location Management record.
     • If no match is found again, the system moves to the next step.
3. Create a Tentative Location
   • If no match is found after both previous attempts, the system creates a Tentative Location using the job’s full address information. This tentative location is flagged in Location Management and requires manual review and resolution by a user.
   • Outcome: The job is ultimately mapped to this newly created tentative location.

Ultimately, every job from your feed will be assigned a corresponding location within Paradox.

Relevant documentation

Review Location Mapping documentation here.

Permissions

By default, Paradox Admins, Company/Account Admins, and Franchise Owners will have full access to this feature. To grant or restrict access, users with full access to Roles and Permissions can update the below permissions accordingly:

• Location Management – Full access allows the user to create, view, and manage locations.
  • Location Mapping – Full access allows the user to manage tentative locations, view location mapping history, and have access to the Location Mapping section of Location Management.