Reads it in
Introw pulls every matching , even old ones, and attributes each correctly.
Embeds it
Attributed records appear in portals, dashboards, commissions, and reporting under your name.
Writes it back
A form submission is attached with the exact method you configured, so the record is born compliant.
The whole point: you match your system to Introw once, and Introw matches every record to your system forever. Historic 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.
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.How it works in Pipedrive
How it works in Pipedrive
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.
How Introw configures it
How Introw configures it
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.
Introw-managed dropdown - options stay in sync
Introw-managed dropdown - options stay in sync
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.
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 and Attribution in Salesforce.
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.Each named attribution is independently reportable, so several partners can be credited on one - 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.
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.Backwards compatibility
Point Introw at your existing model and every historic becomes attributable, in the right partner’s pipeline. Nothing to backfill.
Data hygiene going forward
A partner registering through a form is attached with the exact method you configured - compliant from creation, not reconciled later.
No RevOps work either way
You never restructure . Tell Introw once how objects link to partners; reading old records and writing new ones follow that one definition.
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.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.
1
Open Object Linking
Go to Integrations, 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.
2
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.
3
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.
4
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.
Verify it worked
Open a partner-influenced in . 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 , confirm the attribution (association, field, or relation row) was written on the record itself.Related
Connect Pipedrive
Set up the connection and run this attribution step inside the wizard.
Partner attribution in HubSpot
Properties, association labels, and custom objects for HubSpot.
Partner attribution in Salesforce
Picklists, lookups, relation tables, and custom objects for Salesforce.
Show & rename CRM fields
Put any Pipedrive field on your Introw tables, overviews, and partner views - renamed to partner-friendly labels.