HubSpot Attribution Reporting: Models, Setup, and What Each One Hides

Attribution reporting answers the question executives actually ask of marketing — what produced the revenue — and it answers it with a model, which means every answer carries an editorial position about what deserves credit. That is not a flaw; it is what attribution is. The practical failures are elsewhere: teams choosing models without knowing the credit mathematics, and — more damaging — reading reports without knowing which deals the report silently excluded. This article covers the report types and their tier gates, each model's exact distribution, the bias each model imposes, and the exclusions that decide whether the number on the screen describes your revenue or a subset of it.

Definitions

Interaction — a tracked touchpoint in a contact's history: a page view, form submission, email engagement, meeting or logged activity, as catalogued in HubSpot's attribution documentation.

Conversion path — the ordered set of a contact's interactions leading to the outcome being attributed: the contact's creation, a deal's creation, or closed-won revenue.

Attribution model — the rule distributing credit for the outcome across the interactions on the path.

Contact create / deal create / revenue attribution — the three report types, attributing new contacts, new deals and closed-won revenue respectively.

Report Types and Tier Gates

The three report types are gated differently, and the gates shape what a portal can honestly claim to measure. Contact create attribution is available on Marketing Hub Professional and Enterprise; deal create attribution and revenue attribution require Marketing Hub Enterprise. A Professional portal can therefore attribute lead generation but not revenue, and the common workaround — treating contact attribution as a proxy for revenue attribution — assumes the contacts that convert resemble the contacts that arrive, an assumption the two reports exist to test.

The Models and Their Credit Mathematics

The models are precise, and knowing the numbers is what turns a model choice from taste into design.

First interaction assigns 100 percent of credit to the first touch on the path; last interaction assigns 100 percent to the final touch before the outcome. Linear divides credit equally across every interaction on the path. U-shaped assigns 40 percent to the first interaction and 40 percent to the lead-conversion interaction, spreading the remaining 20 percent across everything between. W-shaped assigns 30 percent each to the first interaction, the contact-creating interaction and the deal-creating interaction, with 10 percent across the rest. Full path — available for revenue attribution — assigns 22.5 percent each to the first interaction, lead creation, deal creation and last interaction, with the remaining 10 percent distributed between. Time decay weights recent interactions more heavily on a seven-day half-life, and the J-shaped and inverse J-shaped models split 60 and 20 percent between the conversion and first touch, in opposite directions, with 20 percent across the middle.

The Bias Each Model Carries

Each distribution privileges a stage, which means each model systematically undervalues a kind of work — and the model a team prefers usually flatters the work that team does.

First interaction credits demand creation and hides everything that happened after the first click, which makes nurture, sales enablement content and late-stage marketing invisible. Last interaction does the reverse: it rewards whatever sits nearest the close — typically bottom-funnel pages and sales touches — and hides how the buyer arrived at all. Linear hides nothing and says nothing: by paying every touchpoint equally it flattens a twelve-touch path into uniformity, crediting a passing pageview at the rate of the demo request. The position-based models — U, W, full path — encode a defensible theory of milestone importance at the cost of the middle: the sustained nurture between milestones shares a small remainder no matter how much of the work it did. Time decay assumes recency is importance, which fits short cycles and misstates long ones, where the decisive interaction may sit months behind a seven-day half-life's horizon.

The honest use of this menu is comparative rather than devotional. Running the same question under first-touch and last-touch brackets the range of defensible answers, and a channel that earns credit under both is genuinely load-bearing. A team that reports one model only — especially one it chose — is publishing its own performance review.

The Data a Report Silently Excludes

Model choice moves credit between channels; the exclusions decide whether whole deals exist in the report at all, and they are the part of attribution reporting almost nobody reads before trusting it.

Revenue attribution excludes deals missing a populated amount, create date or close date; deals that are not closed-won; and deals with no associated contacts. Sales activities count only when linked to both the contact and the deal, and one-to-one emails without replies are not counted as interactions. Very large paths are sampled, with processing documented up to 100,000 associations or activities per deal. Each exclusion is individually reasonable and their sum has a sharp consequence: a portal whose deals arrive by import — a migration, an integration writeback, an offline sales motion — can show healthy closed-won revenue and an attribution report describing only a fraction of it, because the imported deals lack associated contacts with tracked interaction history. The report does not warn that this happened. The revenue simply is not there.

The preflight, then, is arithmetic rather than analytics: sum closed-won revenue for the period in a standard deal report, sum the same period's revenue in the attribution report, and treat the gap as the report's coverage. A coverage gap of a few percent is rounding; a gap of a third means the attribution report is answering a question about the subset of the business that happens online, and it should be captioned that way wherever it is shown. The deal hygiene this depends on — amounts, close dates and contact associations populated as process, not as cleanup — is the same property completeness discipline that adoption measurement runs on.

Setup Procedure

1. Write the question first, in the form "which [asset type or channel] contributed to [outcome] in [period]" — the report builder's choices all descend from it.
2. Confirm the tier gate for the outcome you chose; revenue questions need Marketing Hub Enterprise, and no configuration works around that.
3. Run the coverage preflight above for your period, and record the percentage of revenue the attribution report can see.
4. Build the report from the attribution report builder, selecting the report type, the dimension — asset type, interaction source, campaign — and a model whose bias you can state out loud.
5. Verify against a known deal: pick one recent closed-won deal whose story the team knows, filter to it, and check the report's path against the remembered reality — missing touches at this scale are missing at every scale.
6. Publish with the model named on the dashboard, and where the stakes justify it, publish the same question under a second model beside the first.

Failure Modes

Symptom: attribution revenue is far below actual closed-won revenue. Cause: deals missing amounts, close dates or associated contacts are excluded from the report. Fix: run the coverage preflight, then repair deal-contact associations and the default deal properties — amount and close date — at the source.

Symptom: a channel's credit collapses when the model changes. Cause: its touches concentrate at one end of the path, so position-based models redistribute it. Fix: nothing is broken — report under two models and read the range, not either endpoint.

Symptom: sales activity is invisible in every model. Cause: activities count only when associated to both the contact and the deal, and unreplied one-to-one emails are not interactions. Fix: enforce activity association at logging time; no report-side setting recovers unlinked history.

Symptom: two teams show different revenue for the same channel and period. Cause: different report types or models, unlabelled. Fix: name the report type and model on every published view; an unlabelled attribution number is not yet a fact.

Scope and Limits

This article covers HubSpot's native multi-touch attribution and not the general attribution literature, marketing mix modelling, or third-party attribution tools, which answer overlapping questions with different machinery. The tier gates, model set, credit distributions and exclusion rules are as documented in August 2026 and change with the product; HubSpot's documentation is authoritative over this text. And attribution of any kind estimates contribution from observed correlation on tracked paths — it does not establish that removing a credited channel would have removed the revenue, and decisions of that weight deserve experiments, not reports.

Verification Checklist

The coverage preflight has been run and the attribution report's share of actual revenue is known.

Every published attribution view names its report type and model.

At least one known deal's path has been manually verified against the report.

Deal amount, close date and contact associations are enforced upstream, as process.

High-stakes channel decisions cite two models, not one.

Attribution architecture is part of any reporting engagement we scope.