> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-job-tracking.md).

# Delpha Job Tracking

Track your contacts' career changes in Salesforce with Delpha Job Tracking. Learn to display job history and automate updates using LinkedIn enrichment for smarter prospecting and engagement.

## Delpha Job Tracking Menu Overview

The **Delpha Job Tracking** section helps you monitor your contacts’ career movements directly in Salesforce. It centralizes features related to job history visualization and automation of job change detection.

## **Available Options**

* **How to display the Job History**\
  [Step-by-step instructions for adding the *Job History* related list to the Contact page layout, allowing easy tracking of employment changes.](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-job-tracking/how-to-display-the-job-history.md)
* **How does job tracking works**\
  [Describes how Delpha uses LinkedIn data to identify job changes, enrich account/contact records, and trigger follow-up actions such as contact updates or account creation](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-job-tracking/how-does-job-tracking-works.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-job-tracking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
