# Set up SourceTag with Pipedrive

Canonical: https://sourcetag.io/docs/setup-pipedrive

When a visitor submits a form with SourceTag data, the attribution fields need somewhere to go in Pipedrive. You need to create custom person fields that match the SourceTag field names.

## What you need

- SourceTag installed and form hidden fields set up
- Pipedrive account with admin access

## Step 1: Go to data fields settings

In Pipedrive, navigate to **Settings > Company settings > Data fields**.
## Step 2: Create custom fields

Create a new custom text field for each SourceTag data point:

### Core fields (create these)

| Field name | Label | Type |
|-----------|-------|------|
| `st_fc_channel` | First Click Channel | Text |
| `st_fc_detail_1` | First Click Smart Field 1 | Text |
| `st_fc_detail_2` | First Click Smart Field 2 | Text |
| `st_fc_detail_3` | First Click Smart Field 3 | Text |
| `st_fc_detail_4` | First Click Smart Field 4 | Text |
| `st_lc_channel` | Last Click Channel | Text |
| `st_lc_detail_1` | Last Click Smart Field 1 | Text |
| `st_lc_detail_2` | Last Click Smart Field 2 | Text |
| `st_lc_detail_3` | Last Click Smart Field 3 | Text |
| `st_lc_detail_4` | Last Click Smart Field 4 | Text |
| `st_fc_landing_page` | First Click Landing Page | Text |
| `st_lc_landing_page` | Last Click Landing Page | Text |

### Optional extended fields

| Field name | Label | Type |
|-----------|-------|------|
| `st_fc_click_id` | First Click Click ID | Text |
| `st_lc_click_id` | Last Click Click ID | Text |
| `st_visits` | Visit Count | Number |
| `st_days_to_convert` | Days to Convert | Number |
| `st_device` | Device Type | Text |

See [Captured Fields](https://sourcetag.io/docs/captured-fields) for the full list of available fields.

## Step 3: Map form fields to CRM fields

If your form builder sends data to Pipedrive via an integration (Zapier, native feed, webhook, etc.), make sure the SourceTag form fields are mapped to the corresponding Pipedrive custom fields.
## Step 4: Test

Submit a form with UTM parameters and check the person record in Pipedrive. The custom fields should be populated with attribution data.
## Tips

- The field internal name in Pipedrive must match the form field name. Pipedrive may modify internal names automatically.
- Test with a fresh person (not one that already exists) for the cleanest test.
- **Pipedrive's native web forms** (LeadBooster Web Forms) are not covered by this guide. Pipedrive's [August 2026 update](https://www.pipedrive.com/en/product-updates) added its own UTM capture to Web Forms hidden fields; test it with a tagged link before relying on it. For full SourceTag attribution (channel, first and last touch, click IDs), use a form on your own site that submits to Pipedrive via Zapier or a direct integration.
