> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/operations/lead-forms/lead-source-tracking.md).

# Lead Source Tracking

Track and customize lead sources to understand where your painting leads come from and measure marketing effectiveness.

{% hint style="danger" %}
**Important:** this feature requires the paid **Operations add-on.**
{% endhint %}

A lead source in PaintScout tracks how a potential customer first found or heard about your business. You can assign lead sources to deals, estimates, contacts, and companies to measure which marketing channels drive results.

***

## What Is a Lead Source?

A **lead source** is how a potential customer first found or heard about your business. Tracking lead sources helps you understand where your leads are coming from and which marketing channels are driving results.

You can assign a lead source to:

* Deals
* Contacts
* Companies

This gives you flexibility to track it at the level that makes the most sense for your workflow.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-64e357d3315573ed2c4176513b95b72869550709%2F1732581507_2eb3790ab4cd8229ad7dc7211dee?alt=media" alt=""><figcaption></figcaption></figure>

***

## How Do I Customize Lead Sources?

1. Click the **person icon** in the top right and choose **Account Settings**
2. Go to the **Lead Sources** section
3. Here you can edit, remove, and add new lead sources

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-c02aa4bf99dc679154fd4519a73481cafb406a69%2F1732582655_f67013a350830b73989a19a6bbaa?alt=media" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Lead Source vs. Acquisition Source</strong></td><td>Understand the difference between lead source and acquisition source to better track where your painting leads come from.</td><td><a href="/support/operations/lead-forms/lead-source-vs-acquisition-source.md">Lead Source vs. Acquisition Source</a></td></tr><tr><td><strong>Lead Conversions Report</strong></td><td>Track which lead sources bring the most valuable leads with win rates and revenue data by source.</td><td><a href="/support/dashboard-and-reports/reports/lead-conversions-report.md">Lead Conversions Report</a></td></tr><tr><td><strong>Integration Sources Report</strong></td><td>Track where your estimates originate from by monitoring integration sources like Workglue, Zapier, and other connected apps.</td><td><a href="/support/dashboard-and-reports/reports/integration-sources-report.md">Integration Sources Report</a></td></tr><tr><td><strong>New Leads Report</strong></td><td>Track new leads received and their sources to evaluate lead generation performance across channels.</td><td><a href="/support/dashboard-and-reports/reports/new-leads-report.md">New Leads Report</a></td></tr></tbody></table>


---

# 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.paintscout.com/support/operations/lead-forms/lead-source-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.