Which Attribution Report Type Answers Your Revenue Question?

Attribution questions usually start with a revenue question: which marketing efforts actually move deals and dollars?

But the report you can build depends on two separate choices, and people often make only one of them.

You need to pick the right report type for the question you are asking, and you need to confirm your subscription tier supports it.

Get either one wrong and the report answers a different question than the one you brought to the meeting.

Three report types, three different questions

In HubSpot, attribution reporting shows contact interactions across the customer journey.

It assigns credit to sources, assets and interactions using a model that fits your business per HubSpot's documentation.

The key structural decision is the data source, because each one measures a different conversion.

• Contact Create Attribution measures which sources, assets and interactions had the greatest impact on generating contacts.
• Deal Create Attribution measures which of those had the greatest impact on generating deals.
• Deal Revenue Attribution measures which had the greatest impact on deal revenue.

HubSpot suggests thinking of these as the top, middle and bottom of a funnel model: contact create, deal create and revenue attribution respectively.

That framing is a useful first filter.

If your question is about pipeline creation, deal create is the report.

If your question is about money, deal revenue is the report.

If you are evaluating top-of-funnel content or lead generation sources, contact create is often enough.

Check your tier before you plan the report

Contact create attribution is available on Marketing Hub Professional and Enterprise.

Deal create and deal revenue attribution are Marketing Hub Enterprise only according to HubSpot.

Content Hub Professional and Enterprise also support attribution reporting where noted.

This matters for how you scope work.

If your team runs on Professional and the stakeholder question is explicitly about revenue, the report that answers it directly is not available on that tier.

You have a few honest options.

Build the closest available report and label what it does and does not measure.

Revisit the subscription decision with the revenue question as the concrete use case.

Or answer the question differently, such as with a deal-based report built from source properties your team maintains.

What you should not do is present a contact create report as revenue attribution.

It measures contact generation, and presenting it as anything else erodes trust in the whole reporting stack.

Also note the naming: HubSpot renamed these report types, so older guides may refer to Revenue Attribution as a generic category.

The current names are Deal Create Attribution, Contact Create Attribution and Deal Revenue Attribution.

The last one distinguishes deal-based revenue attribution from attribution for other objects per HubSpot.

Choosing a model once the report type is settled

Once you have the right data source, you choose how credit is distributed across interactions.

HubSpot supports five models per its documentation:

• First Touch gives all credit to the first interaction.
• Last Touch gives all credit to the last interaction before conversion.
• Linear gives equal credit across all interactions.
• Time Decay gives more credit to interactions closer to the conversion.
• Empirical gives credit based on how often each interaction type occurs across conversion paths.

The Empirical model replaces the older U-shaped, W-shaped, J-shaped and Inverse J-shaped models.

It uses historical interaction data to weigh interaction types.

Types that occur less often receive more weight, while all interactions of the same type receive equal weight.

HubSpot's example: if page views occur more often than form submissions across conversion paths, form submissions may get more weight.

They are less frequent and more distinctive in the path to conversion per HubSpot.

Practically, the model choice should follow the decision the report supports.

If the conversation is about which channel starts relationships, first touch is the honest lens.

If sales leadership wants to know what preceded closed deals, last touch reflects that.

If marketing wants a balanced view across a long journey, linear or time decay fit better.

If you want the data itself to determine weighting rather than defending a rule, empirical is the option built for that.

There is no universally correct model; the wrong move is picking one and presenting its output as ground truth without saying which lens it applies.

Two configuration details that affect what your report really shows

Two documented behaviors are easy to overlook and can change how you read results.

First, interaction history and sampling.

Attribution reports include up to 20 million interactions per report after sampling, and when available at least one year of interactions is represented.

If an account has very high interaction volume, HubSpot samples high-frequency interaction types such as email interactions and page views to stay within the limit.

Lower-volume types such as form submissions, calls and meetings are not sampled, and sampling is applied only when total volume would otherwise exceed the limit per HubSpot.

The practical implication: in high-volume accounts, high-frequency interaction types are represented through sampling, so read their share of credit with that in mind.

Second, event inputs.

Each attribution report uses a defined set of interaction types to determine which interactions receive credit.

You can include up to 100 event input types per report per HubSpot.

Which types you include is an editorial decision about what counts as a meaningful touchpoint, and it should match the question.

A report on what drives deal revenue may not need every web page view; a report on content's role in generating contacts probably does.

A short decision path

1. Write the stakeholder question in one sentence, including whether it is about contacts, deals or revenue.
2. Match the question to the report type: contact create, deal create or deal revenue.
3. Confirm your tier supports that report type before promising the deliverable.
4. Choose the model that matches the decision being made, and say so when you share the report.
5. Review the event input types so the interactions included actually reflect the journey you are describing.

If you are building out the surrounding reporting stack, it helps to think about attribution in the context of the broader measurement plan.

Our guide to which interactions to include in an attribution report goes deeper on touchpoint selection.

Our article on which lead score to build first covers how scoring choices shape downstream reporting.

For background on how models differ conceptually, see our attribution model glossary entry and the first touch attribution definition.

Where this fits in your workflow

Attribution reporting is only as good as the interactions flowing into it.

If your integrations and data sync are incomplete, the report will faithfully answer a question about partial data.

Before investing in report design, confirm which systems are connected and what each contributes.

The takeaway: the report type answers which conversion you are measuring, the tier determines whether that report exists for you, and the model determines how credit is told.

Settle them in that order and the report you present will answer the question that was actually asked.

How Meshline can help. Connect automation, Organic Marketing (demand generation), and customer lifecycle management (Revenue Intelligence).

Bring topic planning, content publishing and performance feedback into the conversation about your workflow. Book a Meshline demo.