Per-Post Pipeline Calculation

Your analytics show the second blog post in the follow-up sequence has 3,400 sessions. What it does not show is whether any of those sessions became deals. The per-post pipeline calculation bridges that gap. It produces a single number per slug: the total ARR of open and closed-won opportunities where a contact read that post before converting. The per-post attribution pillar frames the strategic case. This post covers the mechanics: data requirements, CRM query structure, credit-splitting rules, and the benchmarks that tell you whether a number is reliable or noise. According to NinjaCat's State of AI in Marketing 2026 (n=500), only 19% of marketing teams have a formal content measurable movement tracking process with defined metrics and windows. The calculation below is how to join that 19%.

What does "influenced pipeline" mean when applied to a single post?

The difference between sourced and influenced in content attribution

Sourced pipeline and influenced pipeline measure different things. A deal is sourced to a post when the post was the first touchpoint in a contact's history before they became a lead. A deal is influenced by a post when the contact viewed it at any point within the attribution window and later converted to an opportunity.

Blog content is rarely first-touch in B2B SaaS buying cycles. Buyers research for months before they raise a hand. Sourced-only attribution misses most of the work blog content does in a long cycle. A post that generates zero first-touch MQLs and 34 influenced opportunities represents a real business impact that a sourced-only report hides entirely. Use influenced pipeline as your primary content metric. Use sourced pipeline as a secondary check on which posts are pulling in net-new audiences versus re-engaging existing ones.

Why last-touch attribution systematically undercounts blog content

Last-touch attribution assigns all deal credit to the final touchpoint before conversion, typically a demo request or a rep-sent email. Blog posts almost never appear last in the sequence. A reader visits a post in week one of their research, returns twice in month two, then clicks a paid ad in month three before submitting the demo form. Last-touch gives 100% of the credit to the paid ad and 0% to the three blog visits. This is not a data quality problem. It is a model choice problem. For content investment decisions, influenced pipeline with a defined attribution window is the only model that produces defensible numbers.

What data do you need before you can run the per-post pipeline calculation?

The three data requirements

Three inputs must be clean before the calculation produces reliable numbers. The first is UTM capture on every internal CTA click from each post. When a reader clicks any link from a blog post to a product page, form, or demo request, a UTM parameter must fire and be written to the resulting form submission or CRM property. If UTM capture is missing, influenced-deal identification relies on self-reported source, which accounts for fewer than 30% of actual influence events. The CRM property setup guide covers which fields to create and how to populate them from form submissions.

The second input is a contact-to-opportunity association in your CRM. Every opportunity must be linked to the contacts involved in the deal. This is standard in most CRMs but is often incomplete for multi-stakeholder enterprise deals where secondary buyers are added mid-cycle.

The third input is page-level visit data at the contact level: either a CRM contact field that records which content assets a contact visited (written by your form handler or a behavioral enrichment tool) or an analytics export joinable to a CRM identifier on form submit. Most teams have the first two inputs. The third is the one that most commonly fails a data-quality plan.

The most common missing input

The visit-to-contact link breaks most often when teams rely on analytics page-view exports without a reliable way to stitch anonymous sessions to identified CRM contacts. Before a visitor submits a form, their sessions are attached to a browser cookie, not a CRM record. Most analytics platforms stitch pre-form sessions to identified records when the form is submitted on the same browser, but the stitch rate varies by browser, device, and ad blocker prevalence. Plan for a stitch rate of 60 to 75% in a typical B2B SaaS environment and document the gap explicitly in every pipeline report.

How do you identify which deals a specific post influenced?

The CRM query structure

To identify deals a post influenced, you need to cross three data sets: contact visit history, contact-to-opportunity association, and opportunity creation dates. The logic: for each opportunity in your pipeline, pull the associated contacts, then check which of those contacts have a recorded visit to the specific post URL within the attribution window before the opportunity creation date.

In CRM/email platform, this breaks into three steps. Pull all deals created in the measurement period. For each deal, pull associated contact records and check the content-interaction timeline. If your form handler writes a "last content viewed" or "blog post visited" property on each page visit, filter contacts where that field contains the post slug. Count deals where at least one contact matches, sum their ARR, and you have the influenced pipeline number for that post. Salesforce users map the same logic through Campaign Member records joined to Opportunity Contact Roles, filtered by the post URL and a touch-date prior to the opportunity created date.

Handling anonymous versus identified sessions

Your influenced pipeline number is bounded by identified contacts. Anonymous sessions that did not lead to a form submission on the same browser cannot be attributed to a CRM record with current standard tooling. Add a standard footnote to every per-post pipeline report: "This figure counts influence from identified contacts only. Pre-identification sessions are not attributable with current data infrastructure." This is an honest floor estimate. Every per-post number in your report is conservative, not inflated, which makes it more defensible in a budget conversation.

What is the per-post pipeline calculation, step by step?

The four calculation steps

Step one: define the plan. Choose the post slug and the attribution window. Standard options: 30 days for high-intent, late-stage content; 90 days for the typical B2B SaaS research cycle; 180 days for enterprise deals with longer cycles. The attribution window decision framework covers how to pick the right window for each content type. Set your measurement period: trailing 12 months for a mature post, trailing 6 months for a post published fewer than 6 months ago.

Step two: pull influenced deals. Using the query structure from the previous section, identify all open or closed-won opportunities where at least one associated contact visited the post within the attribution window before the opportunity creation date.

Step three: sum the ARR. For each opportunity in the influenced set, record the deal ARR. Do not include closed-lost deals unless you are specifically calculating a "contacted but did not convert" metric for a separate analysis. Sum the ARR of open and closed-won deals. That total is the post's influenced pipeline for the period.

Step four: calculate the monthly run rate. Divide the total influenced pipeline by the post's age in months. A post live for 14 months with implementation budgetin influenced ARR runs at implementation budgetper month.

An illustrative example, not a client result

A post published 10 months ago appears in the influenced-deal set for 48 opportunities. The company's median deal size is implementation budget. Forty-eight opportunities at implementation budgetequals implementation budgetin total influenced pipeline, or implementation budgetper month. At a typical content production cost of implementation budgetper post, the measurable movement ratio over 10 months is 1,440:1. This is a model for estimation, using hypothetical round numbers to show what the output looks like with reasonable B2B SaaS inputs, not a client result.

How do you handle deals that touched more than one post?

Three credit models for multi-touch influence

Most deals in a content-rich program touch more than one post. A single opportunity might have contacts who read five posts across eight months. If every post receives full deal-ARR credit, your influenced pipeline totals will exceed your actual pipeline by a large multiple. Three credit models address this.

Equal-weight split: if a deal influenced five posts, each post gets 20% of the deal ARR credited. Straightforward to calculate. The limitation is that it weights a post visited once in month one identically to a post read six times in the final 30 days before conversion.

Position-weighted: the first-touch and last-touch posts each receive a larger share, typically 40% each, with the remaining 20% split equally among middle posts. This recognizes that initial discovery and final decision content perform different roles in a long B2B cycle.

Time-decay: posts touched closer to the opportunity creation date receive more credit, with influence decaying on a logarithmic curve matched to your typical research cycle length.

The practical default for most teams

Equal-weight split is the practical starting point for most B2B SaaS teams. It is transparent, auditable, and defensible. Once you have 12 months of influenced pipeline data at the equal-weight level, the multi-touch attribution model comparison covers when position-weighted or time-decay is worth the added implementation work.

What makes a per-post pipeline number trustworthy versus noisy?

The three sources of noise in per-post pipeline data

A per-post pipeline number is a full enumeration, not a statistical sample. It counts every identified influenced deal, not a subset. It does not improve with more data in the way a survey estimate improves, but it does degrade from specific, identifiable failure modes.

The first source of noise is UTM breakage. If a post's CTAs fire URLs without UTM parameters on some clicks, the influenced-deal count is systematically underreported. Run the UTM plan from the attribution infrastructure post before treating any pipeline number as reliable. A UTM coverage rate below 85% on CTA clicks makes the resulting influenced number a floor estimate with an unknown gap above it.

The second source of noise is the contact association gap. In some CRMs, contacts are only associated to opportunities when they are the primary contact on a deal. Secondary buyers are left out of opportunity records, so their content interactions do not appear in the calculation. Plan a random sample of 20 closed-won deals to check how completely your CRM associates multi-stakeholder contacts.

The third is the minimum deal count threshold. Harvard Business Review's analysis of marketing measurement found that optimization loops with defined cadences outperform ad hoc improvement by 41%. The same discipline applies to sample size: a post with fewer than five influenced deals in a period produces a directional signal, not a reliable verdict. Use it to flag a post to watch, not to justify a budget cut.

The minimum influenced-deal count for a reliable signal

Five influenced deals is the practical floor for a single data point. Ten or more in a measurement period justifies a budget decision. Below five: label the number as early-stage signal, hold the decision, and give the post another 60 to 90 days of data. If traffic is low, the issue is distribution, not content quality, and the influenced pipeline will not grow until distribution improves. Fix distribution before evaluating the content itself.

How do you use per-post pipeline numbers to make budget decisions?

The three decisions per-post pipeline data supports

IBM's Institute for Business Value AI Agents Study (June 2025, n=2,500) found teams with granular content attribution close 27% more AI-influenced pipeline than teams tracking at the channel level. Granularity is a performance lever, not just a reporting preference. Per-post numbers support three budget decisions that channel-level numbers cannot.

The first is refresh priority. Posts in the top quartile by influenced pipeline get quarterly refreshes: updated statistics, a new external authority link, and a check on the quick-answer block. These posts are active in open deals. Forrester's B2B Content Performance research found that asset-level attribution increases content measurable movement visibility by 44%, specifically because the refresh versus retire decision becomes explicit and defensible rather than traffic-rank-dependent.

The second is retirement candidates. Posts in the bottom quartile with zero influenced deals after 120 days of clean UTM tracking are not contributing to pipeline. Before retiring: confirm UTM coverage above 85% on that post's CTAs, confirm the post has enough traffic to realistically generate opportunities, and check whether it links correctly to the per-post attribution cluster pillar. A post that passes all three checks and still shows zero influenced deals after 120 days is a retirement candidate.

The third is publishing budget allocation. If your top-performing cluster post generates implementation budgetper month in influenced pipeline and cost implementation budgetto produce, the case for more posts in that cluster is financially grounded. The per-post calculation converts content investment into a measurable movement ratio that holds in a CFO conversation because the numerator is real pipeline, not projected value. If you want a diagnostic of which content in your program generates pipeline versus traffic that does not convert, that is what an AI System Plan plan surfaces.

What the top-quartile cutoff tells you about refresh priority

The top quartile adjusts to your inventory size. In a 20-post cluster, it is the top five posts by influenced ARR. In an 80-post cluster, it is the top 20. What stays constant: posts above the cutoff receive active maintenance, posts below it receive a review, and posts with zero deals after 120 clean days of data get a retirement evaluation. This cadence, run quarterly, prevents the inventory accumulation pattern that turns a clean content program into posts competing with each other for ranking.

Methodology

This post addresses a VP Marketing execution need: running the per-post pipeline calculation from raw CRM data to a number defensible in a budget conversation. Four external sources were used. The IBM Institute for Business Value AI Agents Study (June 2025, n=2,500) provides the 27% more pipeline figure for teams with granular attribution, sourced from the prior-verified Day 54 C3 entry in source-usage-log.jsonl. Harvard Business Review's marketing metrics analysis (April 2022) provides the 41% performance advantage for defined measurement cadences, sourced from the prior-verified Day 64 C1 entry. Forrester's B2B Content Performance report provides the 44% content measurable movement visibility improvement figure, sourced from the prior-verified Day 56 C1 entry. NinjaCat's State of AI in Marketing 2026 (n=500) provides the 19% formal tracking figure, sourced from the prior-verified Day 66 C3 entry. All four sources are public and reader-verifiable at the URLs cited. The illustrative example in the step-by-step section uses round, hypothetical numbers explicitly labeled as a model for estimation, not a client result. The SEO keyword "per-post pipeline calculation" was confirmed structurally unoccupied at the exact calculation mechanics angle. The full attribution framework context is at The 44% Gap: Per-Post Attribution.