Logo
  • System Status
  • Gem API
  • Gem Academy
  • What's New?
Logo

Products

People

Outreach

ATS

Scheduling

Talent Marketing

Talent Compass

Templates

Resources

Compliance

Resource Center

Blog

Events

About Gem

About Us

Careers

Contact Us

X/Twitter

LinkedIn

YouTube

(Internal) How is ATS location derived for candidates?

Algolia ID

Audience
Internal
Changes Made
Created Time in Notion
Oct 1, 2025 1:14 PM
Displayed Description

Glean bot
Last Edited At
Apr 7, 2026 9:42 PM
Last edited by
Renée Carignan
Markdown

Notion Created By
Optemization
Notion ID
Notion URL
Owner
Page Type
Article
Persona Types
Summary

Super URL
Verification
Zapier Sync Check (Don't Delete)
Zendesk API URL
Zendesk Article ID

Zendesk URL
Zendesk created
Zendesk last updated
body

category_name
draft

getting_started
section_name
top_level

ATS location for candidates is mapped from specific fields in the corresponding ATS:

ATS
Location Stored Where?
Greenhouse
GreenhouseCandidate.addresses
Workday
WorkdayCandidate.address
SuccessFactors
TBD
SmartRecruiters
SmartRecruitersCandidate.location
Lever
LeverContact.location
AtsLite / Gem Jobs
Person.location
OATS
Person.location
iCIMS
TBD
Taleo
TBD
  • For SucessFactors, we are currently deriving the location value based on available fields like work experience/location.
  • Greenhouse has two location fields; one on the profile (which is typically their home address) and another on the application (where a user has specified their location). We chose the former, despite known data quality issues since Prospect Search surfaces candidate level data more akin to the application values. This helps us simplify the logic and avoid potential collisions.