Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

B2B Marketing › B2B Pipeline

Writing the Source Rule for Pipeline

How to write the rule that records where each opportunity came from: a closed list of origins, an order for ties, who sets it, a test and restated history.
Tutorialintermediate16 min readUpdated

What a source rule settles, and what it does not

A figure for marketing-sourced pipeline rests on a rule that decides what an opportunity began as. The site's guides each decide the source for their own route: the first touch on the account, an offline value that sales fills in, outbound as a source of its own, a partner field, expansion kept apart. Where opportunities begin in more than one way, through inbound requests, events, outbound sequences, partner introductions, existing customers, product sign-ups and sellers' own contacts, no one of those pages writes the single rule that covers them all. That is the job here: the closed list of origins, the order that decides between two of them, who sets the value and when it locks, a test of the wording on real opportunities, and what happens to history.

The parts the site's guides already state, which are what the field answers, building it in the CRM, reporting and reviewing the agreement, get a short pointer in place of a repeat. Advice that goes beyond those guides is labelled general practice in the text. The table shows where the edges are.

QuestionCovered here?Where the answer sits
Which origins an opportunity can haveYesThe closed list, step three
Which origin wins when two applyYesThe order, step four
Who sets the value, when, and when it locksYesStep five and the named decider
Whether earlier periods are restatedYesStep eight
How credit is shared across several touchesNoA separate choice; this rule records one origin and keeps influence in its own report
How fields, forms and syncs are built in a particular CRMNoThe CRM guides pointed to from step six; this page describes no product's screens
What share of pipeline marketing should sourceNoNot answered here, because the figure depends on the rule, and no benchmark is given

A rule that settles the first four rows still says only how opportunities began, as recorded. It does not say whether marketing caused them.

Before you start

  • Two people, named. The sales leader and the CRM owner. The list and the order are agreements with sales, and the CRM owner holds the lock in step five. Writing the rule without both in the first meeting risks writing it twice.
  • A recent set of opportunities. An export with the creation date, the owner, the current source value and the account's and the contact's activity history, for the reading in step one and the test in step seven.
  • The reports already in use. Note which touch each one counts. Two reports that disagree about marketing's contribution are a sign the work is needed.
  • Source on the account needs contacts attached to the right company. The order in step four reads the first touch recorded on the account, so a contact left loose, or a company split across several records, can hide the earliest touch. Where that is true of the sample, run the matching contacts to company records guide before step seven's test.
  • A first sketch of who owns what. Sketch a RACI matrix of the decisions in this rule now, with one accountable role per row, and finish it in step five.
  • The agreement between sales and marketing, or the place where it will live, since step ten adds the rule to it.

The steps

  1. Read how a recent set of opportunities began

    As general practice, begin with evidence, not a draft rule. Export the opportunities created in the latest reporting period and put four things side by side for each: the value in the source field, the earliest touch recorded on the account, the earliest touch recorded on the person who became the contact, and what the seller who opened it says happened. Read the history before asking the seller, and treat the seller's recollection as a check on the history rather than as the record.

    Then sort what you find into the kinds of disagreement the rule has to settle. Two origins on one opportunity: an account first met through a dealer that later filled in a web form, or a show contact a prospector had already emailed. A person and an account that disagree: the contact who asked for a demo was not the first person at the company to touch the business. A value the history contradicts: a seller choosing the website out of habit on a deal that began with a partner's call. A value that is blank, or that a default filled in. And opportunities whose beginning nobody can reconstruct. Keep one line for each kind, with a couple of examples, because steps three to five are written to settle these cases and the test in step seven reuses them.

  2. Decide what the field answers and keep influence apart

    The source field answers one question, which origin began this opportunity, and so is a single-touch form of attribution that leaves the choice among other approaches outside this tutorial. The business-to-business measurement guide covers sourced and influenced pipeline, so keep influence in its own report and out of this field.

  3. Write the closed list of origins with sales

    List all the ways an opportunity can begin in this business, with the sales leader in the room, since sellers and prospectors will be the ones choosing the offline origins from it. As general practice, give each origin a one-line definition that names the evidence placing an opportunity there, and build the list as a picklist, so that a value outside it cannot be saved and a report can group it. A business whose opportunities begin as inbound requests, at events, through outbound sequences, through partners, inside existing customers, through product sign-ups and through sellers' own contacts would end up with a list close to this: inbound request, event, outbound, partner, customer expansion, product sign-up, seller's own network and unknown.

    Keep each origin as a value of its own, because the site's guides already separate them; see the outbound prospecting guide, the channel partner guide, the expansion guide and the pipeline coverage diagnosis.

    Keep stages out of the list. An origin says how an account first reached the business; a stage says how far it has travelled. The product-qualified lead guide reports that stage beside marketing-qualified leads and the lead stages guide holds the earlier ones, so, as general practice, a sign-up that later qualifies on usage keeps its sign-up origin. Last, add the explicit unknown for opportunities whose beginning cannot be shown, and mark in a second column which origins the business has agreed belong to marketing, so that the report reads that column instead of guessing from the names.

  4. Write the order that decides between two origins

    Some opportunities may fit two origins, and a list cannot choose between them; an order can. As general practice, start from the rule the measurement guide prefers for judging demand creation, the first touch recorded on the account, and write it as one sentence: the first recorded origin on the account takes precedence. A new opportunity on an account that already buys is customer expansion. Then add exceptions, each in one sentence that names the record which triggers it. A business that sells through dealers, exhibits at a show and has prospectors would write three. Here an earlier website visit stands for an earlier inbound request recorded on the account, and a dealer is the partner origin. A registered dealer introduction outranks an earlier website visit; the ownership rule under the partner lead registration tutorial gives an approved registration the deal, and this rule points to it rather than restating it. A meeting that a prospector booked outranks an earlier website visit. A meeting pre-booked through the show's promotion outranks it too, following the trade show tutorial, which credits those meetings to the promotion. Each exception beats an earlier website visit only; an earlier event, dealer or outbound origin still comes first. A business without one of these drops that line and keeps the method.

    As general practice, two habits keep the order workable. Write each exception as evidence the CRM owner can check, such as a registration record, a meeting created by the prospector or a meeting that carries the show's campaign, so that nobody has to settle it by opinion. And write down which exception wins when two apply to one account, because a gap there is where a dispute can start. When a case turns up that the order does not settle, add a sentence to the rule and take it to the review in step ten rather than ruling on it case by case.

  5. Decide who sets the source, when, and when it locks

    Answer three questions in writing: who sets the value, when, and when it locks.

    Who sets it depends on how the origin arises. As general practice, an origin derived from a recorded first touch, such as an inbound request, carries over from the account and nobody types it, because the CRM fundamentals guide ranks a salesperson's guess lowest for reliability among source values and writes original source once, at creation, without overwriting it. The offline origins, which create records with no landing page, are picked by whoever creates the opportunity, from the list, with no default and with the event, dealer or prospector named, and the order in step four still decides between that pick and an earlier origin on the account; that guide asks for a picklist filled by sales at creation for offline sources alone. As general practice too, customer expansion is picked the same way, since the account's first touch belongs to its first purchase. Routing is a separate matter: lead routing may move the record to another owner, and the origin stays as set.

    When: at creation, and the opportunity cannot be saved without one, as the channel partner guide asks of its partner field, which is completed at creation and not at close. As general practice, the value locks as soon as the opportunity exists: sellers, marketers and automations can read it, and none can edit it except the CRM owner. The CRM owner alone changes a value, and writes a note recording what changed, why, who asked and on what evidence. Finish the matrix sketched at the start of this tutorial with a row for each of these decisions, each with one accountable role.

    Finally, write what happens when no source is recorded: the opportunity carries the explicit unknown, not a default that happens to read as a marketing value, and the marketing report leaves it out and, as general practice, shows its share.

  6. Build it in the CRM with no default

    Build the list and the rule in the CRM so that a value is required when an opportunity is created. The guide to standardising CRM field values keeps a list's values consistent, and the syncing guide for the CRM and the marketing platform lists original source among the values a later sync must not overwrite.

  7. Test the rule on real opportunities with two readers

    A rule that reads clearly to the people who wrote it can still fail in other hands, so test the wording before it governs a report. As general practice, choose a sample of recent opportunities that includes some of each kind of disagreement found in step one, and give two readers, one from marketing and one from sales, the written rule and the histories but not the current source values. Each assigns an origin to each opportunity alone and writes the evidence beside the choice. Then compare the two sets of answers with each other and with the value in the field.

    As general practice, where the readers disagree, treat the wording as the thing at fault. Find the sentence in the list or the order that allowed two readings, rewrite it, and have both read the disagreements again until they agree on them. Where both agree and the field says something else, you have found the cases the new rule will change, which step eight needs. Where neither can say, the history is missing or the list has no origin for the case: add the evidence or the missing origin, not a guess. Keep the sample and its disagreements as the test pack for the review in step ten. The sample is small, so a handful of disagreements can reflect chance alone, and the guide to reading small numbers calls for counts beside rates and for more data where a count is small.

  8. Settle what happens to history

    A new rule can move the figures. Decide before the first report how earlier periods are treated, and say so in writing: rebuilt under the new rule where the records allow it, or, where they do not, left as reported with a dated line. Changing a source definition without restating earlier periods is a mistake the glossary entry for sourced pipeline flags, and a quiet restatement misleads too: a figure that jumps for a reason nobody recorded can be mistaken for a change in the market. The same holds if the definition of what counts as an opportunity changes in the same period.

    As general practice, rebuild an earlier period under the new rule only where the CRM holds evidence for it. The diagnosis of a blank or wrong lead source gives the pattern for records with no source: fill a value only where a reliable record exists, set the explicit unknown where none does, and note the rule and the date of the change. Where a rebuild is not possible, leave the older figures and, as general practice, put a dated line under them in the report itself, saying which rule produced them, when the new rule began and that the two series are not comparable. Then compare like with like: read the accounts first touched in a given quarter as a cohort, under one rule at a time, and do not set a figure under the new rule against an earlier one under the old.

  9. Report sourced and influenced side by side

    Report both views next to each other, as the campaign records guide and the self-reported attribution guide describe, and, as general practice, show beside them the share of opportunities whose origin is unknown.

  10. Review the rule with the agreement

    Put the finished rule into the agreement between sales and marketing, as the sales and marketing alignment guide asks of a written sourcing rule, with its date and its named decider, and, as general practice, set a date to review it against the test pack from step seven.

The origins and the order on one page

As general practice, keep this page with the agreement between sales and marketing, dated at each revision, and adapt the rows to the business's own origins. The last column is what the business has agreed, not a fact about the origin.

OriginWhat places an opportunity hereWho sets itCounted as marketing-sourced?
Inbound requestThe account's first recorded touch is a request from someone at the companyCarried over from the accountAs agreed in step three
EventThe opportunity began with a contact met at an eventThe creator, from the list, with the event namedAs agreed
OutboundThe opportunity began with a prospector's sequence or callThe creator, with no defaultNo: its own source, with marketing's part recorded as influence
PartnerThe opportunity began with a registered partner introductionThe creator, with the partner field filledNo: reported apart as partner-sourced
Customer expansionA new opportunity on an account that already buysAs general practice, the creator, from the list, with no defaultNo: its own source, not new marketing-sourced pipeline
Seller's own networkA seller's personal contact or referralThe creatorNo: sales' own referral
Product sign-upSomeone signed up for the free plan or trial before the opportunityAs general practice, carried over from the recorded sign-up; without one, another origin or the unknownAs agreed
UnknownNo evidence of how it beganSet explicitly, not by defaultNo: left out of the marketing report and, as general practice, with its share shown
  • The order. The first recorded origin on the account takes precedence. A new opportunity on an account that already buys is customer expansion. The listed exceptions, each naming its evidence, outrank an earlier website visit only.
  • The lock. The value is set at creation, locks at once, and only the CRM owner changes it afterwards, with a note.
  • History. Earlier periods are rebuilt where the records support it, and carry a dated line where they do not.

A hoist maker's source rule (illustrative)

Illustrative example — not a real result

Gidbrod Hoists settles a third against a fifth

Gidbrod Hoists is an invented maker of electric hoists and lifting beams. It sells to workshops directly, through machinery dealers, at one trade show and through two prospectors. The sales leader has just been told that marketing sourced a third of last quarter's pipeline by one report and a fifth by another. The two reports apply different first-touch rules: one counts the first touch on the person, the other the first touch on the account.

The marketing lead, the sales leader and the CRM owner start by reading last quarter's opportunities one at a time. They find a dealer introduction where the buyer had also filled in the website form, a show meeting that a prospector had already emailed, and sellers entering "website" from habit on deals that began with a dealer's call. They then write the rule. The closed list of origins is inbound request, event, outbound, dealer, customer expansion, seller's own network and unknown. The first recorded origin on the account takes precedence, except that a registered dealer introduction, a meeting a prospector booked and a meeting pre-booked through the show's promotion each outrank an earlier website visit. The dealer case applies the ownership rule written under the partner registration tutorial, and the show case follows the trade show tutorial's credit of pre-booked meetings to the show's promotion; neither is restated. An origin derived from a recorded first touch, an inbound request, carries over from the account, because a seller's guess ranks lowest for reliability among source values, while the offline origins (event, dealer, seller's own network and outbound) are picked by the creator at creation with no default. After that, the CRM owner alone changes a value, with a note.

To test the wording, the marketing lead and one seller each assign an origin to 40 recent opportunities from the histories alone. They disagree on a handful, and the group rewrites the sentences on prospector-booked meetings and the dealer exception until the two readers agree on those cases. Both reports are rebuilt on the written rule where the records allow it, and a dated line under the older quarters says they were produced under the earlier rules. The monthly report then puts sourced and influenced pipeline next to each other, with the share of opportunities still recorded as unknown beside them.

The pipeline section sets this tutorial among the guides on stages, alignment, measurement and the weekly review that read the figures the rule fixes.

Common mistakes

  • Writing "first touch" and stopping there. Without the closed list and the order, two readers still reach different answers on the same opportunity.
  • Letting two reports count different touches. A rule on the person and a rule on the account can credit the same deal differently, and the dispute that follows concerns the rules, not the market.
  • Letting sellers type the source for opportunities that began with a recorded touch. Carry the origin over from the account and keep manual choices for the offline origins.
  • A default value. Offline origins get no default, and an opportunity with no recorded origin carries the explicit unknown (steps five and six).
  • Putting influence in the source field. One field cannot carry both views, so keep influence in its own report.
  • Counting outbound, partner or expansion opportunities as marketing-sourced. Give each its own origin and report it apart.
  • Letting anyone edit the value after creation. Changes go to one named role, with a note that records the evidence.
  • Changing the rule without saying so. Rebuild earlier periods where the records support it, set the unknown where they do not, and put a dated line under the older figures.
  • Skipping the two-reader test. A rule that reads clearly to its authors can fail in the hands of the seller who opens the next opportunity.
  • Reading a handful of disagreements as proof. A small sample can reflect chance alone; the aim of the test is to cover all the kinds of case.

Frequently asked questions

Should an opportunity's source follow the first touch on the person or on the account?

Where several people at a company deal with the business, a rule on the person gives a different answer depending on which contact is read, and two reports can disagree about the same opportunity. The measurement guide prefers first touch recorded on the account as the single rule for judging demand creation, so, as general practice, write that as the base and name the few exceptions the business accepts, such as a registered partner introduction. Whichever rule is chosen, put it in the agreement between sales and marketing and apply it in all reports.

Who should be able to change the source once an opportunity exists?

As general practice, one named role, such as whoever runs the CRM, and only with a note that says what changed, why and on what evidence. The CRM fundamentals guide writes original source once, at creation, and does not overwrite it, and it ranks a salesperson's guess lowest for reliability among source values. A seller who disagrees with a value should bring evidence to the named role instead of editing the field. The agreement between sales and marketing should say who sets the field, when it locks and who may change it afterwards.

What should happen to opportunities with no recorded source?

Give them an explicit unknown value instead of a default, leave that value out of the marketing report, and, as general practice, show its share beside the sourced and influenced figures so readers can see how much of the pipeline cannot be placed. Backfill an older record only where a reliable record of how it began exists, and note the rule and the date.

Terms used on this page

Frameworks

Sources

  1. Digital Marketing and Measurement Model — Avinash Kaushik

Related