Forecasting Playbook
How to Forecast Pipeline From Content Programs
This guide shows you exactly how to connect content to pipeline and revenue. You will set definitions, clean data, build a bottom-up model, run scenarios, align with sales commit, and track actuals. No leaps. Only steps you can audit.
What a content pipeline forecast is
A content pipeline forecast estimates opportunities and revenue that will be created or assisted by your content within a time window. It is not a guess. It is a model that multiplies traffic, engagement, and conversion rates by content type and buyer intent. The model is bottom-up, uses your historical data, and reconciles to sales capacity.
Data hygiene and prerequisites
Events and tracking
- In GA4 mark outcome events as conversions (demo, trial, calculator complete, template download). See GA4 help center.
- Use consistent UTM tags for outbound distribution. See campaign tagging.
- Connect Google Search Console for query trends. See performance report.
CRM fields
- Create a campaign for each pillar or theme.
- Add fields: Content Touch (checkbox), Last Content Touch (lookup), Pillar (picklist), Asset URL (text).
- Define “content-assisted opportunity” clearly: at least one content touch within a set lookback window before opp create.
Definitions and windows
- Pick a lookback window (often 30 to 90 days) for assistance.
- Separate new business vs expansion. Separate inbound vs partner.
- Use one time zone and one currency for the model.
Metrics dictionary
Agree on names first. This table is the contract. If a metric is unclear here, it will be unclear in your forecast.
| Metric | Definition | Source |
|---|---|---|
| Session | Visit to a page in a given period | GA4 |
| Engaged session | Session with time threshold or key event | GA4 |
| Content action | Download, calculator run, newsletter opt-in, click to product page | GA4 |
| Lead | Contact captured from content path | GA4 to CRM |
| SQL or SQO | Sales accepted opportunity | CRM |
| Opportunity | Record with dollar value and stage | CRM |
| Content-assisted opportunity | Opp with at least one content touch within the lookback window before create date | CRM |
| Win | Closed won opportunity | CRM |
| ACV | Average contract value for new business | CRM or finance |
For clarity on GA4 events and conversions see GA4 help. For Search Console definitions see Google.
Build a bottom-up model
You will forecast by content family and intent. Forecast sessions and actions first, then translate to opportunities and revenue using your historical conversion rates and ACV. Follow these steps exactly.
Step 1 — choose scope
- Include only public content that can be tied to events and UTMs.
- Decide whether to include email and social distribution in the same model. If you include them, tag them consistently.
Step 2 — group content by family
- TOFU: definitions, explainers, benchmarks.
- MOFU: comparisons, templates, ROI calculators.
- BOFU: pricing, implementation, security, case narratives.
Step 3 — calculate baselines
Pull last 3 to 6 months of data. For each family compute averages and medians. Use medians when outliers are large.
Traffic rates
- Sessions per page per month
- Share of new vs returning
Engagement rates
- Engaged session rate
- Content action rate per session
Conversion rates
- Lead rate from content actions
- SQO rate (lead to opp)
- Win rate and ACV
Step 4 — forecast sessions and actions
Use Search Console trends and publishing plan to estimate sessions by family. Respect seasonality and ramp times. New assets rarely hit full traffic in month one.
Step 5 — translate to pipeline
Multiply through the funnel using your baselines. Do it per family so you can see which pages actually drive opportunities.
Copyable forecast formulas
Input sheet spec
Worked example
| Family | Sessions (S) | Engaged (S*ER) | Actions | Leads | Opps | Wins | ARR |
|---|---|---|---|---|---|---|---|
| TOFU | 18,000 | 9,900 | 792 | 143 | 29 | 9 | $162k |
| MOFU | 9,000 | 5,580 | 558 | 123 | 37 | 10 | $220k |
| BOFU | 4,000 | 2,800 | 336 | 94 | 42 | 13 | $416k |
| Total | 31,000 | 18,280 | 1,686 | 360 | 108 | 32 | $798k |
Forecast workflow (explained)
Acceptance criteria for the model
Scenario planning and sensitivity
Do not present a single number. Present a range with the drivers that push the number up or down. This turns a forecast into a decision tool.
Base case
- Traffic follows last quarter trend and seasonality
- Conversion rates equal trailing medians
- Publishing velocity as planned
Upside case
- MOFU CTR lifts from better internal links
- New BOFU pages increase SQO rate
- Two posts rank faster due to internal links
Downside case
- Traffic dips due to seasonality
- Consent or tracking gaps reduce measured events
- Publishing slippage or delays
Sensitivity grid
| Driver | -10 percent | Base | +10 percent |
|---|---|---|---|
| Sessions | – pipeline accordingly | baseline pipeline | + pipeline accordingly |
| Engaged rate | – actions and leads | baseline | + actions and leads |
| SQO rate | – opportunities | baseline | + opportunities |
| ACV | – revenue | baseline | + revenue |
Align with sales commit
Sales capacity caps how much pipeline can convert. Reconcile your forecast to headcount, territory coverage, and working days.
- Capacity: opps per rep per month by stage. Remove holidays and offsites.
- Coverage: ensure forecasted opps match industry and region focus.
- Rules: define when a content opp becomes a sales commit. Example: when it reaches stage 2 with budget and timeline confirmed.
Blend GA4 and CRM attribution
Do not pick a single model. Use GA4 for sessions and actions. Use CRM for opportunities and revenue. Blend them with rules you can explain.
GA4 rules
- Track conversions on content pages (mark them in GA4).
- Use UTMs for newsletter and social distribution. See Google campaign tagging.
- Connect Search Console for query coverage and click-through.
CRM rules
- For assistance, require at least one content touch within the lookback window before opportunity create.
- Log the asset URL on the contact or opportunity.
- Report “opportunities that touched content” by pillar and stage.
UTM spec (copy this)
Leading indicators to watch
These move before pipeline. Use them to adjust forecasts early and avoid surprises.
Search Console
- Impressions and average position for target clusters
- Click-through rate by query pattern
Engagement
- Engaged session rate and scroll depth
- Action completion rates on MOFU and BOFU pages
Enablement
- Sales usage of pricing, ROI, and procurement links
- Support deflection from FAQ hubs
Dashboards and cadence
Report the path in English and numbers. Update monthly. Keep a changelog of rates and assumptions.
| Card | Definition | Target | Owner |
|---|---|---|---|
| Content-assisted pipeline | Opps with content touch in window | Improving trend | RevOps |
| SQO rate | Lead to opportunity for content paths | Improving trend | Sales Ops |
| Stage velocity | Days between stages on content paths | Downward trend | Sales Ops |
| ACV and win rate | Deal quality on content paths | Stable or up | Finance |
| Forecast vs actual | Monthly variance and reasons | Low variance | Marketing |
FAQ
How long until a new page contributes to pipeline
Assume a ramp. TOFU pages can take 60 to 120 days to reach stable traffic. BOFU pages can influence faster through enablement links. Reflect this in session forecasts.
Can we attribute a deal to one post
Use assistance, not single-touch. Attribute at the pillar or family level and focus on the route that produced confidence and speed.
What if our tracking is incomplete
Document known gaps, apply conservative rates, and improve tracking. When in doubt, rely on CRM stage data for the revenue parts of the model.
How do we avoid double counting
De-duplicate by opportunity ID. A content touch can assist only once per opportunity within the selected window. Avoid summing page-level pipeline without this rule.