Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

    English (US)
    MX Spanish (Mexico)
    CA French (Canada)
    US English (US)
    • Home
    • Management Tools
    • Data Feeds
    • Location Feeds

    Location Feeds overview

    Written by Lindsey Stanifer

    Updated at August 20th, 2026

    Contact Us

    If you still have questions or prefer to get help directly from an agent, please submit a request.
    We’ll get back to you as soon as possible.

    Please fill out the contact form below and we will reply as soon as possible.

    • Getting Started
      Setting up your calendar Managing your alerts Additional Settings
    • Daily Processes
      Candidate Inbox Candidate Profile My Calendar/Calendars Browser Extension My Jobs Approvals Engine Manual and Common Scheduling Practices Form I-9 processes Troubleshooting Forms & Offers
    • Candidate and User Engagement
      Campaigns Conversation Builder Surveys Channels Talent Community Voice Web Management Analytics & Reporting Data Privacy Career Sites
    • Management Tools
      Job Management Scheduling Security Journeys Content Management System (CMS) Multiple Brands Workflows Users, Roles and Permissions Data Feeds Location Management Lookup Tables Assistant Messaging Company Information Client Setup System Attributes Integration Center
    • Contextual AI
      Knowledge Training Library
    • Conversational Events and Campus
      Conversational Events Campus Events
    • Employee Communications
      Communications App Employee Management
    • Release Notes
      2025 2026
    • Workday Feature Descriptions
    + More

    Table of Contents

    Best practices for implementation Relevant documentation Permissions

    Paradox can consume client location data through the manual addition of locations, manual CSV file import, CSV file import through a Paradox sFTP, or the Paradox API. CSV / SFTP is recommended, API should be used for specific client cases. 


    Best practices for implementation

    • When implementing Location Feeds, it is highly encouraged to set up data feeds with date and time included in their files' naming convention (include YYMMDD_HHMMSS instead of just YYMMDD). If files are sent over on the same day and you’ve included only YYMMDD, then the latest file will override the previous file in the system, preventing any way to analyze the original file upload.

    Relevant documentation

    Learn more about this feature here.


    Permissions

    By default, only Paradox Admins will have access to Data Feeds. If you and/or a member of your team needs access to uploading one-time location files and/or viewing scheduled location feeds, request to have the Locations permission (under the Data Feeds parent permission) granted for the necessary user roles.

    conversational ats integrated ats

    Was this article helpful?

    Yes
    No
    Give feedback about this article

    Related Articles

    • Multiple job locations for standard jobs
    • Job posting locations
    • Selecting job posting type on the job

    Copyright 2026 – Paradox.

    Knowledge Base Software powered by Helpjuice

    Expand