> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner attribution in Pipedrive

> How to attribute Pipedrive deals to partners with a custom field - the one method Pipedrive supports - including multiple partners per deal and setup.

export const object_3 = "deal"

export const crm_2 = "Pipedrive"

export const object_2 = "deal"

export const crm_1 = "Pipedrive"

export const object_1 = "deal"

export const crm_0 = "Pipedrive"

export const object_0 = "deal"

Attribution is the link between a Pipedrive record and the partner who sourced or influenced it. It is what makes partner-attached pipeline, reporting, and commissions trustworthy - so it deserves to match how your deals are actually modelled, not the other way around.

Pipedrive models that link one way: a **custom field** on the record. That is deliberately the simplest of the three CRMs Introw supports, and **Introw handles it out of the box.**

There is no RevOps project, no schema rebuild, no code, and no {crm_0} consultant. You keep your existing model; you simply tell Introw *how a record is linked to a partner*, and from there Introw does the rest:

<CardGroup cols={3}>
  <Card title="Reads it in" icon="arrow-right-to-bracket">
    Introw pulls every matching {object_0}, even old ones, and attributes each correctly.
  </Card>

  <Card title="Embeds it" icon="table-cells">
    Attributed records appear in portals, dashboards, commissions, and reporting under your name.
  </Card>

  <Card title="Writes it back" icon="arrow-right-from-bracket">
    A form submission is attached with the *exact method* you configured, so the record is born compliant.
  </Card>
</CardGroup>

<Note>
  The whole point: **you match your system to Introw once, and Introw matches every record to your system forever.** Historic {object_0}s become attributable, and new partner-created records are born correctly attributed. That is the backwards-compatibility and data-hygiene win - and it holds for whichever method below you already use.
</Note>

## The method - a custom field

**Best for:** every Pipedrive program. It is the only attribution method Pipedrive offers, and it covers the common case cleanly.

A **custom field** on the deal holds the partner. Most commonly a **single-option (dropdown) field** with one option per partner, though a text field works too. Reps pick the partner on the deal, and because the value lives directly on the record it is easy to filter and report on with Pipedrive's own tools.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  deal["Deal"] -->|"partner field"| partner["Partner"]
```

<AccordionGroup>
  <Accordion title="How it works in Pipedrive" icon="gear">
    Pipedrive lets you add custom fields to deals, persons, and organizations. A single-option field stores a defined set of options; each deal carries one value. You add the field once, and reps set it on the deal - no relationships or junction objects to design.
  </Accordion>

  <Accordion title="How Introw configures it" icon="sliders">
    On **Object Linking → How do you attribute partners to Deal objects?**, choose **Custom properties** and select the field. If the field stores coded values (IDs or abbreviations rather than partner names), use **Match property values to Introw partners** to line each value up with the right partner record, so deals resolve correctly.
  </Accordion>

  <Accordion title="Introw-managed dropdown - options stay in sync" icon="arrows-rotate">
    Introw can **own the field's options** and keep them synced to your live partner list - one option per active partner. Add a partner in Introw, the option appears; the field never drifts into stale names or typo'd free text. That is the difference between a field that decays and one that stays clean.
  </Accordion>
</AccordionGroup>

| Pros                                                 | Cons                                                       |
| ---------------------------------------------------- | ---------------------------------------------------------- |
| Simplest possible setup, no relationships            | One value per field, so multi-partner needs several fields |
| Native Pipedrive filtering, lists, and reports       | Free-text variants drift without an owner                  |
| Introw can manage the options so they never go stale | Coded values need a one-time value-to-partner map          |
| Works on any Pipedrive plan                          | Not linked to a separate partner record                    |

<Note>
  Pipedrive has a few limits the other CRMs do not: partners are stored as the **Organization** object (custom partner objects are not available), attribution is **custom-field only** (no association labels or relation tables), and there is **no in-CRM embed** - your team and partners work in Introw, Slack, or email rather than inside Pipedrive. If your program needs association-based or relation-table attribution, see [Attribution in HubSpot](./attribution-in-hubspot) and [Attribution in Salesforce](./attribution-in-salesforce).
</Note>

## More than one partner on a deal

Pipedrive has no relation table, so when a deal involves several partners - a referrer who surfaces it and a delivery partner who implements it - you model each role as its **own custom field** and map each one independently.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  deal["One Deal"] -->|"Referring partner field"| referrer["Referring partner"]
  deal -->|"Delivery partner field"| delivery["Delivery partner"]
```

<Note>
  Each named attribution is **independently reportable**, so several partners can be credited on one {object_1} - a sourcing partner and an influencing partner side by side - and your commission plans run on whichever attribution(s) you scope them to. Name each attribution clearly and it reads that way in reporting, in the portal, and to partners.
</Note>

## Two-way by design - read *and* write

Attribution isn't only about reading what exists. Introw also **writes attribution the same way you defined it**, so the model holds no matter who creates the record.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  partner["Partner submits<br/>a form in the portal"] --> introw["Introw form automation"]
  introw -->|"creates the record"| record["New record"]
  introw -->|"attaches the partner via<br/>your configured method"| link["Configured attribution"]
  record --- link
  link --> compliant["Record is born<br/>correctly attributed"]
```

<CardGroup cols={2}>
  <Card title="Backwards compatibility" icon="clock-rotate-left">
    Point Introw at your existing model and every historic {object_2} becomes attributable, in the right partner's pipeline. Nothing to backfill.
  </Card>

  <Card title="Data hygiene going forward" icon="broom">
    A partner registering through a form is attached with the **exact method you configured** - compliant from creation, not reconciled later.
  </Card>

  <Card title="No RevOps work either way" icon="circle-check">
    You never restructure {crm_1}. Tell Introw once how objects link to partners; reading old records and writing new ones follow that one definition.
  </Card>
</CardGroup>

## Set it up

You configure attribution on the **Object Linking** screen. This is the same step the connect wizard runs, reopened any time to add or refine a mapping.

<Note>
  The Pipedrive integration is a plan feature. If the tile is not offered under **CRM & Data**,
  it is not on your plan yet - check what yours includes at [introw.io/pricing](https://introw.io/pricing).
</Note>

<Steps>
  <Step title="Open Object Linking">
    Go to [Integrations](https://app.introw.io/settings/integrations?category=crm), open the connected Pipedrive connection with **Configure**, and go to **Which objects do you link with partners?**. Select **Add object**, or open the existing **Deal** mapping to edit it. Configure **Deal** at minimum, since deal attribution is what reporting and commissions run on.
  </Step>

  <Step title="Choose the partner field">
    On **How do you attribute partners to Deal objects?**, choose **Custom properties** - the only method on Pipedrive - and select the Pipedrive field that records which partner influenced the deal. For more than one partner, add a mapping per field.
  </Step>

  <Step title="Map values to partners if prompted">
    When the field holds coded values rather than partner names, use **Match property values to Introw partners** to line each value up with the right partner record, so deals resolve correctly.
  </Step>

  <Step title="Name the attribution and save">
    Set **What name do you want to use for this attribution?** so the link reads clearly to your team and partners (for example "Influencing partner"), then select **Add Deal attribution** (or **Save** when editing). Repeat **Add object** for persons or organizations you also want credited.
  </Step>
</Steps>

## Verify it worked

Open a partner-influenced {object_3} in {crm_2}. In Introw it shows attributed to the right partner under your attribution name, and that partner's sourced/influenced pipeline reflects it in reporting and commissions. For a partner-created {object_3}, confirm the attribution (association, field, or relation row) was written on the {crm_2} record itself.

## Related

<CardGroup cols={2}>
  <Card title="Connect Pipedrive" icon="book-open" href="./connect-pipedrive">
    Set up the connection and run this attribution step inside the wizard.
  </Card>

  <Card title="Partner attribution in HubSpot" icon="book-open" href="./attribution-in-hubspot">
    Properties, association labels, and custom objects for HubSpot.
  </Card>

  <Card title="Partner attribution in Salesforce" icon="book-open" href="./attribution-in-salesforce">
    Picklists, lookups, relation tables, and custom objects for Salesforce.
  </Card>

  <Card title="Show & rename CRM fields" icon="table-columns" href="./show-and-rename-crm-fields">
    Put any Pipedrive field on your Introw tables, overviews, and partner views - renamed to partner-friendly labels.
  </Card>
</CardGroup>