Skip to main content
Attribution is the link between a HubSpot 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 CRM is actually modelled, not the other way around. HubSpot lets you model that link in three fundamentally different ways. Introw supports all three out of the box. There is no RevOps project, no schema rebuild, no code, and no 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:

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 three methods at a glance

Custom property

A property on the deal holds the partner. Simplest; works on every HubSpot plan.

Association label

A labelled deal-to-company association marks the partner. Native and scalable; needs Professional or Enterprise.

Custom object

A dedicated Partner object is associated to deals. Richest partner data; needs Enterprise.
Configure Deal attribution at minimum - it is what reporting and commissions run on. You can attribute contacts, companies, tickets, and custom objects to partners the same way.

​
Method 1 - Custom property

Best for: simpler programs where a deal has one partner (or a small fixed set), and teams that want attribution live on the HubSpot plan they already pay for. A custom deal property holds the partner. Most commonly a dropdown (enumeration) property - one option per partner - but a text or multiple-checkbox property works too.
A HubSpot dropdown select property stores a defined set of options; each deal carries one value. Reps pick the partner from the dropdown on the deal record. Because the value lives directly on the deal, it is trivial to filter, list, and report on with native HubSpot tools.
On Object Linking → How do you attribute partners to Deal objects?, choose Custom properties and select the property. If the property 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 can own the dropdown’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 picklist never drifts into stale names or typo’d free text. That is the difference between a property that decays and one that stays clean.If you have no link yet, pick No attribution yet and Introw creates a managed partner dropdown on the Deal object in one click.

​
Method 2 - Association label

Best for: scalable programs that already associate the partner company to the deal natively, and teams that want to distinguish how a partner was involved (sourced vs. influenced). A custom association label between the Deal and the partner Company marks which associated company is the partner - for example “Partner sourced” or “Partner influenced”.
HubSpot associations connect records; an association label describes how they’re related. Labels come in two forms: a single label that reads the same from both sides (“Partner”), or a paired label with a different word per side (“Referrer” / “Referred by”). You can create up to 50 labels per object pair, so one deal can carry several partner relationships at once - each under its own label.
Choose Associations and pick the association label that represents the partner relationship. Introw reads the labelled association to attribute the deal to the associated partner company. No value mapping is needed - the association is the partner record.
Custom association labels require Marketing, Sales, Service, Content, or Data Hub Professional or Enterprise, and a Super Admin creates them. On a Starter plan, use a custom property (Method 1) instead - Introw supports both identically.
Association labels are the sweet spot for most growing programs: native to HubSpot, no data drift, and they carry the relationship type natively - which powers the multi-tier attribution described below.

​
Method 3 - Custom object

Best for: large programs that model partners as a first-class entity, with tier, region, focus, and program data living on a dedicated record rather than on a Company. A HubSpot custom object (e.g. “Partner”) is associated to deals - optionally with association labels to distinguish sourced vs. influenced - and Introw treats that object as the partner.
A custom object is your own CRM object with its own properties and associations. You model partners on it, associate it to deals (and contacts, companies, tickets, custom objects), and use association labels on those links just as you would with a Company.
Set the partner object to your custom object during connect (the “How do you store partners in your CRM?” step). Then attribute deals via Associations, selecting the label that links a deal to that partner object. Introw reads the partner object’s properties for tier, region, and more - so your rich model flows straight into segments, portals, and reporting.
Custom objects require a HubSpot Enterprise subscription on at least one Hub (Marketing, Sales, Service, Content, or Operations). Enterprise allows up to 10 custom object definitions.

​
Multi-tier attribution - more than one partner on a deal

Real ecosystems rarely have exactly one partner per deal. A referrer surfaces it, a reseller closes it, an implementation partner delivers it. Introw models this natively: you can define several named attributions on the same object, each with its own name. This is not limited to associations or a custom object - every method here can be repeated, including a plain property: add one property (or label) per role, map each as its own attribution, and one deal credits several partners across tiers. You can mix and match the mechanisms to express roles:

Multiple association labels

One label per role - “Partner sourced”, “Partner influenced” - each its own named attribution.

Multiple properties

Separate dropdowns like “Referring partner” and “Delivery partner” on the same deal, each mapped independently.

Custom object roles

Several partner-object records on one deal, each under a role label.
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.

​
Choosing a method

Whichever you choose, configuration is the same shape: open Object Linking, pick the method, name the attribution, decide if it’s commission-eligible, save. Introw handles the rest - no code, no consultant.

​
Set it up

Whichever method you chose, you configure it in the same place: the Object Linking screen. This is the same attribution step the connect wizard runs, reopened any time to add or refine a mapping.
1

Open Object Linking

Go to Integrations, open the connected HubSpot connection with Configure, and go to Which objects do you link with partners?. Select Add object to create a mapping, 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 how deals attribute to partners

On How do you attribute partners to Deal objects?, pick the method that matches your data: Custom properties, Associations, or No attribution yet (Introw creates a managed partner property on the Deal object in one click). This mirrors the three methods above.
3

Configure the method and map values

Fill in the detail: for a property, select the one that holds the partner; for an association, confirm the label that represents the partner relationship. If a property stores coded values rather than partner names, use Match property values to Introw partners to line each value up with the right partner record.
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). Confirm when Introw asks you to verify. To credit more than one partner on the same deal, add another Deal attribution with a different property or label (for example a “Delivery partner” alongside a “Referring partner”) - each is its own named attribution. Repeat Add object to credit other record types too (contacts, companies, tickets).

​
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.

Connect HubSpot

Set up the connection and run this attribution step inside the wizard.

Partner attribution in Salesforce

The same depth for Salesforce - lookups, relation tables, and roles.

Partner attribution in Pipedrive

The property-based method for Pipedrive.

Show & rename CRM fields

Put any HubSpot field on your Introw tables, overviews, and partner views - renamed to partner-friendly labels.