How to Track Outbound Attribution in HubSpot

Most HubSpot outbound setups track what happens to a contact after they enter the CRM. Reply status, deal stage, meeting booked, closed won. These are outcome fields.

What most setups do not track is the input side: why this contact was reached out to in the first place, what signal triggered the outreach, and what the timing context was at capture.

Without input-side data, you can see that contact X converted. You cannot see what made contact X different from the 400 contacts who did not.

The minimum input fields to track per contact

Before any contact enters a sequence, at least three input fields should exist on their HubSpot contact record:

Why them. The ICP match criteria that caused this person to be selected. Not just "VP of Engineering" as a job title, but the specific filter set that qualified them: title, company size range, industry, geography. This does not need to be long. A short text field or a custom property with the ICP tier is sufficient.

Why now. The timing signal. If the contact came from a database pull, this field might be empty or set to "database pull, [date]." If it came from a signal source, this field should contain the signal type and topic: "LinkedIn comment, LLM cost benchmarking, [date]."

Why us. This one is optional at early stage but valuable later: what about the offer matched this contact specifically. Which product tier, which use case, which pain category.

The custom properties to add in HubSpot

Create these as custom contact properties in HubSpot:

signal_theme: text field. The keyword topic that triggered capture.

engagement_type: dropdown. Comment, reaction, share, job change, database pull.

engagement_class: dropdown. Evaluating, active consideration, category engaged, unknown.

signal_capture_date: date field.

composite_score: number field. If you score records before delivery.

icp_tier: text or dropdown. Which ICP segment this contact belongs to.

sequence_name: text. Which sequence was used for first outreach.

These do not replace HubSpot's native deal and activity tracking. They sit alongside it as the input-side context that explains why the outreach happened. This is one of the operating details in signal-led outbound.

How to use the data

Once you have input-side and output-side data in HubSpot, you can run two analyses that are not possible with outcome fields alone:

Which input types convert. If contacts with engagement_class "evaluating" close at a higher rate than contacts with engagement_class "category engaged," that tells you to prioritize evaluating-class signals in future delivery. You cannot know this without the input field.

Which signal themes produce pipeline. If the signal_theme "LLM cost benchmarking" produces 3 closed deals and "general AI tooling" produces none from the same volume, you shift monitoring toward the first theme. Again, not visible without the field.

The feedback loop this creates

Tracking input fields transforms the CRM from a record of outcomes into a feedback loop for improving the input layer. Every closed deal traces back to a reason. Every dead sequence can be examined for whether the input was the problem or the execution was.

This is the operational reason to track attribution. Not for reporting, but for iteration.

Richie Reach attaches signal_theme, engagement_type, engagement_class, composite_score, and signal_capture_date to every HubSpot contact record as custom properties. The feedback loop is part of the delivery model, not an afterthought.

See how HubSpot sync works in detail.