How to Attribute Pipeline.

To attribute pipeline to a specific blog post, you need one thing most teams have not wired: an opportunity field that inherits the contact's first-touch blog tag, so revenue reports can group closed deals by post slug. The UTM tagging and the form capture are usually already in place. Fifty-nine percent of CMOs report insufficient budget to meet their marketing goals, according to the Gartner 2025 CMO Spend Survey (n=402, Feb-Mar 2025). Budget defenses require post-level evidence, not a channel rollup that says "organic search drove $480k." For the full per-asset attribution framework, start at The 44% Gap: Per-Post Attribution. This spoke covers the opportunity-level field copy, the pipeline report construction, and how to diagnose posts that show zero attribution.

What does "attribute pipeline to a blog post" actually produce?

The end state is a CRM report with two columns: a blog post slug in column one and a pipeline or revenue number in column two. Sorted descending, it tells you which posts are producing deals. The report is not generated by AI or a third-party attribution tool. It reads a field on the Opportunity record that holds the slug of the first blog post that brought the account into your database.

The specific output: sourced pipeline and influenced pipeline

Two versions of the report matter. The sourced pipeline report counts only opportunities where the blog post was the account's first recorded marketing touch: the post appeared before any email, any ad, any other content asset. The influenced pipeline report counts all opportunities where the blog post appeared anywhere in the account's interaction history before the deal closed. A post that sources 2 opportunities and influences 14 more is worth very different budget decisions than a post that sources 2 opportunities and influences 2 more.

Why the opportunity record is the right anchor, not the contact record

Revenue aggregates at the Opportunity level in every CRM. You close deals, not contacts. A contact can belong to multiple opportunities over their lifetime as a customer, and the first-touch blog post that brought them into your database may have influenced a renewal two years after the original acquisition. Storing blog attribution only on the Contact means it is invisible to every revenue report your board sees. The report your CFO reads groups by Deal, sums ARR, and filters by Close Date. For post-level attribution to appear in that report, it must live on the Opportunity.

What does the full attribution chain look like from blog post to closed deal?

Three steps connect a blog post read to a closed-won deal in your CRM. Each step can be wired independently; the sibling spokes in this cluster cover each in detail. This post covers where they connect and the single step most teams skip.

Step 1: Tag the blog post CTA link with a unique campaign value

Every internal link in a blog post that points to a conversion destination (/free-ai-audit, /benchmark, /demo) must carry a utm_campaign value equal to the post slug. The reliable implementation puts the tagging in a shared template function rather than in each post individually. The withUtm() helper in src/templates/shared.ts handles this at line 1906: withUtm('/free-ai-audit', post.slug, 'blog') returns /free-ai-audit?utm_source=blog&utm_campaign=attribute-pipeline-to-specific-blog-post. Every post that renders through the shared template inherits its own unique campaign tag without per-post configuration.

Step 2: Capture the UTM at form submission and write it to the contact

When the visitor arrives at /free-ai-audit carrying the UTM, a JavaScript snippet reads utm_source and utm_campaign from the URL on page load and stores them in hidden form fields. When the form submits, those hidden fields travel with the payload. The server endpoint reads them and writes first_touch_source and first_touch_campaign to the CRM contact. The UTM form capture wiring guide covers this in detail. The specific CRM property schema is in the CRM attribution properties setup guide. Together, those two steps are usually what teams have already done when they come to this spoke.

Step 3: Copy the contact's first-touch campaign to the opportunity on creation

This is the step most teams skip. When a salesperson creates an Opportunity in the CRM, the Opportunity record starts empty. It does not inherit the contact's first_touch_campaign field automatically. No CRM platform does this by default because the same contact can belong to multiple opportunities and the platform does not know which attribution to carry forward. You define the rule explicitly, and it runs once.

Why CRMs do not solve this automatically

CRM platforms separate Contact and Opportunity schemas deliberately. The platform has no opinion about whether the opportunity that opened in February should inherit the attribution from the contact's first blog visit in November. That is a business decision. Only 26% of executives report that their data is sufficient to support AI-enabled revenue streams, according to the IBM Institute for Business Value 2025 study (n=2,500 executives, 18 industries, June 2025). The field copy rule is one of the specific data wiring decisions that closes the gap between having attribution data at the contact level and having it visible in revenue reports.

How do you set up the opportunity field that the pipeline report reads?

The report reads one field on every Opportunity: first_touch_blog_post. This field is a string that holds the utm_campaign value (the blog post slug) copied from the associated contact at opportunity creation. Setting it up requires two things: the custom field on the Opportunity record and the automation rule that writes to it.

Creating the custom Opportunity field

In CRM/email platform, go to Settings, Properties, Deals, and create a single-line text property named "First Touch Blog Post" with internal name first_touch_blog_post. In Salesforce, add a custom text field to the Opportunity object with the API name First_Touch_Blog_Post__c. The field should be read-only for users (it is written by automation, not by salespeople) and visible in the opportunity layout so the sales team can see which content sourced an account. That visibility matters: salespeople who can see the first-touch post often use it as context when they reach out.

The automation rule that copies from contact to opportunity

In CRM/email platform, create a Workflow with the enrollment trigger "Deal is created" and add an action to copy the value from the Associated Contact's first_touch_campaign property to the Deal's first_touch_blog_post property. Set the "copy if empty" condition so the action only fires when first_touch_blog_post has no value, preventing later enrollments from overwriting the original. In Salesforce, create a Record-Triggered Flow on the Opportunity object, triggered "before save" on the "create" event. The flow looks up the primary Contact Role, reads First_Touch_Campaign__c from the contact, and assigns it to First_Touch_Blog_Post__c on the opportunity. The "before save" trigger writes in the same transaction as the record creation, so the field is populated from the moment the opportunity exists.

Handling contacts that predate the implementation

Contacts created before you implemented UTM capture have no first_touch_campaign value. Any opportunity created from those contacts carries an empty first_touch_blog_post field. Accept the gap for historical data. The pipeline report will show a segment of opportunities with no blog attribution; that segment shrinks as new contacts with clean data enter the pipeline. Do not backfill historical records with guessed values. An empty field is honest. A guessed value corrupts the report permanently.

How do you build the per-blog-post pipeline report?

The report has four parameters: the grouping field (first_touch_blog_post), the measure (close value or ARR), the stage filter, and the date range. The stage filter is what separates the sourced report from the influenced report. To get your attribution chain audited and the report set up, an AI system audit maps exactly where in your funnel attribution data is being lost.

The sourced pipeline report

In CRM/email platform, create a Custom Report using the "Deals" data source. Group by first_touch_blog_post. Measure: sum of Deal Amount. Filters: Deal Stage = Closed Won, Close Date = within last 12 months. Sort descending by Deal Amount sum. This report shows how much closed revenue each blog post sourced as the first marketing touch. Twelve months is the right default window because it covers a typical annual content investment cycle. If your median sales cycle exceeds four months, extend to 18 months.

In Salesforce, the equivalent is a Summary Report on the Opportunity object, grouped by First_Touch_Blog_Post__c, with SUM(Amount) as the measure. Filters: Stage = Closed Won, Close Date = last 12 months. The same report with Stage removed and all stages included gives you influenced pipeline.

The influenced pipeline report and what it adds

The influenced pipeline report shows total open plus closed pipeline with any first-touch attribution to each post. It is a broader signal: a post that generated three closed-won deals and 20 open opportunities shows differently in the influenced report than in the sourced report. The two together map the full funnel impact per post. The first-touch vs. last-touch attribution guide covers the tradeoffs in detail; first-touch sourced attribution, the model used here, is the simplest and most actionable starting point.

Setting the lookback window

The lookback window should equal your median sales cycle plus 30 days. Pull the median days-to-close from your CRM: the median difference between Opportunity Create Date and Close Date, filtered to Closed Won over the last 12 months. If the median is 90 days, set the window to 120. A window shorter than your sales cycle systematically undercounts every post's impact because deals sourced in month one close in month four and fall outside the report. A window longer than 18 months is rarely meaningful for content investment decisions because the marketing landscape changes faster than that.

How do you interpret what the report tells you?

The report produces two types of posts worth different responses: posts with high sourced attribution that deserve more investment, and posts with zero attribution that need a diagnosis before conclusions are drawn.

High sourced pipeline: what to do next

A post that sourced significant closed revenue in the last 12 months is a signal worth doubling down on. Three follow-on actions: update the post with current data to extend its longevity, create a companion spoke that addresses a question the top-performing post leaves unanswered, and build a conversion asset (a checklist, a calculator, a comparison page) that captures buyers the post attracts before they complete their evaluation elsewhere. The pipeline report tells you which posts have validated demand signals. Act on the signal before a competitor occupies the same topic.

Zero sourced pipeline: what it means and does not mean

Zero sourced pipeline after 90 days means one of three things: the tagging chain is broken for that post, the post attracts an audience that does not match your buyer profile, or the post is genuinely not influencing pipeline yet. The order of investigation matters. Check the chain first. A broken tag looks identical to a post with no pipeline impact in the report, and a broken tag is a five-minute fix while retiring a post is a content decision with costs attached.

What should you do when a specific blog post shows zero pipeline?

Run the three-step tagging audit before any content decision. The audit takes 30 minutes and either surfaces a wiring problem or confirms that the zero is real.

The three-step tagging audit

Step one: open the post and click the primary CTA. Inspect the destination URL in the browser address bar. Does it contain utm_campaign equal to the post slug? If not, the template helper is not running on this post, or the CTA is hardcoded without the helper call. Fix the template and the tag appears on every future click; no other changes needed.

Step two: submit a test form using a unique test email address from the tagged URL. Open the resulting contact in your CRM. Does first_touch_campaign equal the post slug? If not, the form handler is not reading the UTM from the payload, or the property write is failing. Check the form handler logs and the CRM property configuration.

Step three: create a test opportunity from the test contact. Does first_touch_blog_post on the new opportunity equal the post slug? If not, the automation rule is not firing on opportunity creation. Check the workflow or flow configuration for enrollment conditions that may be filtering it out.

Self-reported attribution as a backup signal

For posts that pass the tagging audit and still show zero pipeline, add a text field to your lead capture form: "How did you find us?" Accept free text, not a dropdown. Buyers who arrived through organic search often name a specific post or a search phrase that maps to one. This self-reported signal cannot be aggregated automatically, but a monthly review of the field values surfaces posts that the UTM chain missed, typically because the buyer read the post on mobile and completed the form days later on desktop after the session UTM expired.

The content investment calendar the report produces

After two quarters of clean data, the per-post pipeline report is effectively a content investment calendar. Posts in the top quartile by sourced pipeline get refreshes on a quarterly schedule. Posts in the bottom quartile that also fail the tagging audit get the chain fixed and 60 more days of data. Posts in the bottom quartile with clean tagging and no self-reported attribution after 120 days are retirement candidates: redirect them to the cluster pillar and reallocate their publishing slot. The decisions are data-driven because the data exists at the asset level, not the channel level.

Methodology

The budget pressure statistic (59% of CMOs reporting insufficient budget) comes from the Gartner 2025 CMO Spend Survey, fielded February-March 2025 with 402 CMO respondents, published May 2025 by Business Wire at the URL cited in the lead paragraph. The 26% data confidence statistic is from the IBM Institute for Business Value 2025 study "AI Agents: Essential, Not Just Experimental," fielded with 2,500 executives across 18 industries and 19 regions, published June 2025 via IBM Newsroom at the URL cited in the body. The withUtm() function described in step one of the attribution chain is verified in this site's public source at src/templates/shared.ts, line 1906. CRM automation rule mechanics described for CRM/email platform and Salesforce reflect platform behavior as of 2026 and should be verified against current documentation before implementation. To attribute pipeline blog post by post slug, the three-step chain (tag links, capture UTM at form submission, copy contact UTM to opportunity) must all be running cleanly; the pipeline report is the output, not a replacement for the chain.