> 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/delpha-campaigns/configure-a-delpha-campaign/select-the-campaign-type/job-tracking.md).

# Job Tracking

## Job Tracking Campaign Overview

The **Job Tracking** campaign is designed for managing **Contacts and Accounts already existing** in your Salesforce org. It's ideal for detecting job changes and enriching related data—automatically.

### **Prerequisites**

* Both **Contacts and Accounts** should already exist and be **LinkedIn-enriched**.
* [**Job tracking automation**](/delpha-for-salesforce/delpha-apps/delpha-setup/delpha-configuration/job-tracker.md) should be define to match your expectations: manual or automatic  account creation and contact movement

### **Contact-Centric Workflow**

Since the contact is the central entity, the process begins with a LinkedIn enrichment:

* **Enrich Contact from LinkedIn**: Detects job changes.
* **Check Contact Quality**: Triggers a quality review and recommendation.
* **Find Email**: Suggests a new email if missing.

### **Account Updates (if job changed)**

* **Create Account**: If a job move is detected and allowed by the setup.
* **Enrich Account from LinkedIn**: Pulls company insights.
* **Check Account Quality**: Runs full data quality assessment and recommendations.

{% hint style="info" %}
In Job tracking, the main subject is the contact. \
That's why the pipeline starts with a LinkedIn enrichment to update the job history and detect a new position (same company) or a new  job (different company). 
{% endhint %}

{% hint style="warning" %}
More information on[ Delpha Job tracking](/delpha-for-salesforce/how-to-faq/delpha-job-tracking/how-does-job-tracking-works.md) 
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.delpha.io/delpha-for-salesforce/delpha-campaigns/configure-a-delpha-campaign/select-the-campaign-type/job-tracking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.