When sales and marketing both claim the same deal
When sales and marketing both claim the same deal, the answer comes from a written rule for what sourced means, applied to the full buyer path, with influenced pipeline reported next to it. Most credit disputes start because each team reads a different slice of the same record, and nobody wrote down which slice decides.
The deal in this post is a composite of a pattern common in B2B teams that run an inbound program and an SDR team on the same accounts.
What happened on this deal?
An operations director finds one of your blog posts through Google search in week 1. She reads two more pages and leaves without filling out a form, so the visits are anonymous.
In week 3 an SDR adds her to an outbound sequence because her company is on a target account list. She does not reply. In week 5 her manager clicks a LinkedIn Ads unit and registers both of them for a webinar. That registration is the first time her email is tied to her earlier visits.
They attend the webinar in week 6. In week 7 she replies to the SDR's fourth email and books a meeting. The AE opens an Opportunity the same day, and the deal closes a few months later.
What does each team see when it looks at this deal?
Marketing opens its attribution report and sees a path that starts with organic search, picks up a paid social click, and runs through a webinar. By a first-touch reading, this is marketing-sourced pipeline.
Sales opens the CRM. The Contact was created by the SDR from a list in week 3, so Lead Source says Outbound. The meeting was booked by a reply to a sales email. By the CRM's reading, this is a sales-sourced deal.
Both readings are accurate about what each team can see. The CRM record starts in week 3 because that is when the Contact was created, two weeks after her first visit. The attribution report starts in week 1 because the webinar form tied her anonymous visits to her email. Our post on why your Lead Source field is misleading you covers how that create-time stamp gets set and why it rarely changes later.
Who sourced this deal, and who influenced it?
Sourced pipeline is one label per deal: the touch that started the relationship. Influenced pipeline covers every touch after that, up to the close, and it is shared. A deal can be sourced by one team and influenced by both.
If your rule says sourced means the first recorded touch before the Opportunity, this deal is marketing-sourced. The search visit in week 1 came before any sales touch. The SDR sequence, the ad, the webinar, and the reply all count as influence, and the SDR's reply is the touch that turned interest into a meeting.
That reading does not take anything away from sales. The SDR booked the meeting and the AE closed the deal, and both show up in influenced pipeline and in quota. What the rule settles is the narrower question of which team started the deal. Our guide to first-touch attribution for B2B marketers explains why that first visit is worth keeping on the record.
What rule should decide marketing-sourced pipeline?
Any rule works if both teams agree to it before the quarter starts and it is applied to the full path. Most teams write theirs from a few decisions:
- The starting event. Pick the first recorded touch from either team, counted before the Opportunity is created.
- A lookback limit. Ignore touches older than a set number of days before the Opportunity, so a blog visit from two years ago does not claim a new deal. Our explainer on the attribution window covers how to size that limit from your own closed deals.
- An outbound rule. If an SDR touch came before any recorded visit from that person or account, the deal is sales-sourced.
- A tie-break. When two touches land the same day, the earlier timestamp wins, and both still count as influence.
Write the rule in one paragraph, store it where RevOps, sales leadership, and marketing leadership can all find it, and keep it the same for the whole quarter. A rule that changes mid-quarter turns every board review into a debate about definitions.
How should you report sourced and influenced pipeline?
Put them side by side and never add them together. Sourced pipeline sums to 100 percent of pipeline, because each deal has one source. Influenced pipeline sums to more than 100 percent, because most deals have touches from several channels and both teams.
Show the path behind any deal someone questions. A label in a CRM field is easy to argue with. A dated list of every visit, ad click, webinar, and sales email is much harder to dispute. Our post on putting marketing attribution on the board slide covers how to present the sourced view to leadership without overstating it.
If your team uses Salesforce or HubSpot, keep Lead Source as the create-time label it is. Report sourced pipeline from the path, and note the difference when the two disagree, because those gaps show where Contacts are being created late. Our post on what your CRM attribution report leaves out goes deeper on that gap.
How do you settle the next dispute faster?
Give disputes a standing process so they do not end up in a Slack thread between two VPs.
- Pull the full path for the deal: every visit, form, ad click, event, and sales touch, in order.
- Apply the written rule to that path and let it decide.
- Report influence too, so the team that did not source the deal still sees its touches.
- Log the decision with the deal, the rule used, and the outcome.
- Revisit the rule once a quarter. Change it only at the start of a quarter, and only if the log shows a pattern the rule handles badly.
After a quarter, the log becomes useful on its own. If most disputes come from Contacts created by SDRs before any form fill, the fix is upstream: connect anonymous visits to Contacts earlier, so both teams see the same first touch.
How Source helps both teams read the same path
Source installs with one pixel or Google Tag Manager, with no data warehouse to build. It records each visit from the first one and ties the path to Contacts and Deals in your CRM, including HubSpot, so marketing and sales look at the same dated record when a deal is in question.
You can read that path under multi-touch models, with view-through, offline, and LLM attribution for ChatGPT, Claude, Perplexity, and Gemini, plus real CAC, goals, and channel quality. You can chat with your data, get AI recommendations, and receive daily Slack reports. Source is SOC 2 Type II and ISO 27001 certified, and customer data is not used to train external models.
Start free at dash.source.app/signup and pull the full path behind the last deal your teams argued about.