B2B buying committees break single-contact attribution

November 8, 2026

Buying committee attribution header: several glowing paths converge into one ACCOUNT node, then run to a DEAL node

Most B2B attribution reports give a deal to one person: whoever filled out the demo form. That person is rarely the whole story. B2B deals are closed by a buying committee, and each member reaches you through a different channel. Our view is simple. If your report credits one contact per deal, your CAC and channel quality numbers are wrong, and buying committee attribution is how you fix them.

What is a buying committee in B2B attribution?

A buying committee is the group of people at one account who research, evaluate, and approve a purchase. In a software deal that usually means a champion who finds you and pushes for the tool, an evaluator who tests it or reviews security, and an economic buyer who owns the budget. Titles change from company to company. The pattern holds.

Buying committee attribution ties every one of those people to the same account and the same deal, then credits the channels that reached each of them. The form fill is one event on that path. It is rarely the first touch, and it is almost never the one that decided the deal.

Buying committee attribution journey map: a champion, an evaluator, and an economic buyer take different paths that converge at one deal — Three people, three paths, one deal. The form fill captures one of them.

Why does single-contact reporting hide the real path?

CRMs were built around contacts. A form creates a contact, the contact gets a lead source, and the opportunity inherits it. If the champion filled out the form after reading a LinkedIn post, the deal goes to LinkedIn. The evaluator who found you on a review site and spent two afternoons in your docs gets nothing. The CFO who asked an AI assistant for a shortlist and then read your pricing page never shows up at all.

Those errors compound. Channels that reach senior buyers look weak, because senior buyers rarely fill out forms. Channels that reach the form filler look strong, because they collect credit for work the whole committee did. Budget follows the report, so over a few quarters you fund the channel that captures the form and cut the ones that built the consensus.

It distorts team credit too. When an account executive pulls a new contact into the deal from a meeting, that contact is often created with no source. Our post on splitting deal credit between sales and marketing covers how to handle those hand-added contacts fairly.

How do view-through, LLM attribution, and dark research show up across the committee?

Each member of the committee leaves a different trace, and some leave very little.

View-through is common with economic buyers. A VP may see your LinkedIn or Google Ads campaign a dozen times without clicking. Their first Visit is a typed URL. Without view-through data that ties the impression to the account, that Visit lands in Direct and the campaign looks like it did nothing.

LLM attribution covers buyers who start with an AI assistant. They ask ChatGPT, Claude, Perplexity, or Gemini for a vendor shortlist before they ever visit a site. When they click through, the referrer tells you which assistant sent them. When they copy the URL into a new tab, you see Direct again.

Dark research covers the rest. Evaluators paste links into internal chat, read your docs while logged out, and share screenshots in a thread you will never see. You cannot track the conversation. You can track the moment each of those people visits, and which account they belong to.

That last point is what holds the path together. If the economic buyer's Visit matches the same company as the champion's form fill, the committee shows up as one journey. Our guide to identity resolution for B2B attribution explains how anonymous visits and known contacts get matched to accounts.

What should you record so CAC by channel stays honest?

CAC by channel is spend on a channel divided by the customers it produced. If each customer is counted through one contact, every channel that reached a different committee member is undercounted. On every deal, record:

The original source of each contact on the account, kept even after later touches overwrite the CRM field.
Every contact linked to both the account and the opportunity, including people sales adds by hand.
Meetings, demos, and calls as dated touches on the path.
Late joiners, such as the security reviewer or procurement lead who appears in week six. Give them a source too, even if it is "added by sales."
A self-reported answer on the demo form, so channels that never produce a trackable click still get a vote. The self-reported attribution checklist covers how to word and store that question.

Buying committee attribution checklist: keep original source, link every contact, log meetings, add late joiners, then calculate honest CAC — Keep every contact and meeting on the account path before you calculate CAC.

Then apply a multi-touch model at the account level, so each channel's share of a deal reflects every person it reached. With that in place, the math in our guide to CAC by channel for B2B gives you numbers you can defend in a budget meeting.

One practical test: pull your last ten closed-won deals and count the contacts on each opportunity. If most show one contact, your CRM is reporting form fills, and your channel mix is being judged on a fraction of the committee.

How does Source keep the whole account path in one place?

Source installs with one pixel or through Google Tag Manager, with no warehouse to build. It records every Visit and the pages viewed, groups visitors and contacts by account, and joins them to Meetings and Deals in your CRM, such as HubSpot. Each account gets one path, from the first anonymous Visit through every committee member to the closed deal.

On that path, Source applies multi-touch attribution and adds view-through, offline touches, and LLM attribution from ChatGPT, Claude, Perplexity, and Gemini. Real CAC, goals, and channel quality are calculated from the full account path. You can chat with the data, get AI recommendations on where to shift spend, and read a daily Slack report.

Source is SOC 2 Type II and ISO 27001 certified, and customer data is not used to train external models.

If your pipeline report still names one person per deal, start free at dash.source.app/signup and see the whole committee on one path. You can read more about the product at source.app.