Quarterly Attribution Plan

This attribution plan checklist covers the four systems most likely to produce wrong numbers in your QBR deck: the UTM capture layer, the CRM data model, the BI report definitions, and the executive summary format. Only 30% of marketing teams report readiness to scale AI capabilities, according to the Gartner 2026 CMO Spend Survey (n=401). The gap is rarely a strategy problem. It is almost always a data problem: UTM fields not captured, CRM properties not populated, reports built on assumptions that were never verified. The per-post attribution pillar covers the full architecture; this spoke turns that architecture into a repeatable quarterly check that produces a scored health report and a ranked gap list before your next board deck.

What is a quarterly attribution plan and why should you run one?

An attribution plan is a structured check of the four systems that convert marketing activity into pipeline evidence: the UTM capture layer, the CRM data model, the BI report definitions, and the summary format you bring to leadership. Running it quarterly catches drift before it becomes a crisis.

The most common drift pattern looks like this. A developer updates the site's form handler, and the hidden UTM fields that populate on page load stop firing. Attribution data stops flowing into CRM. Three months later, the head of marketing presents a channel mix to the CFO using data that covers only 40% of actual leads. Nobody flagged it because nobody ran the check.

A quarterly plan prevents that. It also gives you a repeatable baseline. When you can show attribution health was 92% in Q1 and 89% in Q2, you have a trend, not just a snapshot. Boards trust trends more than single-point claims.

The four layers a quarterly attribution plan covers

Each layer sits on top of the previous one. A failure at the capture layer corrupts everything above it.

• Capture layer: Are UTM parameters being read from the URL and written to CRM on form submission?
• Data model: Are CRM field definitions consistent with what the capture layer writes?
• Reporting layer: Are your BI reports joining on the right identifiers and applying consistent date logic?
• Summary layer: Does the executive summary reflect verified data, not estimates?

The checklist below runs through each layer in order. Work top-down. If the capture layer fails, fix it before touching the reporting layer.

How do you verify your UTM capture layer is still working?

Open your CRM and pull the last 30 form submissions. Count how many have a populated utm_source field. If the number is below 85%, your capture layer has a gap.

Common causes, in order of frequency: the form handler was updated and the hidden field JavaScript no longer fires; a new landing page was built without the hidden field markup; a tracking parameter changed name in the ad platform and the legacy utm_source mapping no longer matches.

The fastest verification tool is a test submission from a URL you control. Append utm_source=plan-test&utm_medium=qa&utm_campaign=plan-2026-q3 to any live form page. Submit. Open the CRM record. If utm_source reads "plan-test," the capture layer is working for that page. If it reads blank or "(none)," you have a capture failure.

Where UTM capture breaks quietly

The most dangerous capture failures are partial: the form submits but only half the UTM fields populate. This happens when the hidden field JavaScript fires after the form submission event rather than before. The CRM record gets a contact but no attribution data.

The Conversion System codebase handles this via the withUtm() helper in src/templates/shared.ts, which reads UTM parameters from sessionStorage on page load and writes them before form submit fires. Any implementation that reads from the URL at submit time instead of page load will fail on forms where the user navigated from the landing page to a different page before submitting. Check your implementation against this pattern if you see inconsistent UTM population.

Exit criteria for the capture layer check

The capture layer passes when: (1) a test submission from a UTM-parameterized URL produces a CRM record with all five UTM fields populated (source, medium, campaign, content, term); (2) the last 30 real submissions show at least 85% utm_source coverage; and (3) the most recent ad spend report shows that the utm_source values in CRM match the source labels your ad platform uses.

How do you check your CRM data model for consistency?

Pull a sample of 50 CRM contacts who submitted a form in the last 90 days. Export: utm_source, utm_medium, lead_source (picklist field), and date_created. Look for three failure modes.

First: utm_source is "google" but lead_source reads "Other." This means the UTM-to-picklist mapping logic was not updated when a new source was added to the capture layer. The contact has raw UTM data but the CRM picklist that feeds your pipeline reports is wrong.

Second: utm_source is blank but lead_source has a value. This means the picklist was set manually, probably by a sales rep or import. The contact will appear in pipeline reports under a source that may have nothing to do with the actual acquisition channel.

Third: both fields are populated but they disagree. utm_source says "linkedin-ads" but lead_source says "Inbound." This is the most common pattern after a CRM migration or a workflow rule change that overwrote the picklist retroactively.

Replacing the lead source picklist with a campaign tag field resolves the second and third failure modes at the data model layer without requiring a workflow plan.

How do you plan your first-touch vs. last-touch balance?

Most B2B marketing teams use last-touch attribution by default because it is what CRM calculates automatically: the most recent utm_source before the form submission. That is useful for measuring conversion efficiency. It is not useful for measuring content that educates buyers early in the evaluation period.

Pull two numbers from your CRM for the last 90 days: the top utm_source by contact volume (that is your last-touch leader) and the top utm_source among contacts who later progressed to Opportunity stage (that is your quality signal). If the same source ranks first on both lists, your attribution is working. If different sources rank first, you are optimizing the wrong thing.

The two-report BI model gives you both the path report (retrospective: which content appeared in closed deals) and the influence report (forward-looking: which content appears in current-stage pipeline). First-touch data feeds the path report. Last-touch data feeds conversion-rate calculations. Both are necessary. The plan confirms you have both, not just one.

How do you validate your AI-influenced pipeline claims?

AI-influenced pipeline is the category most likely to produce a number your CFO challenges. The typical claim is structured like this: "AI-assisted sequences generated 34% of Q2 pipeline." The CFO's question is: how do you know which contacts were actually influenced by AI rather than by the rep who picked up the phone?

The IBM Institute for Business Value study (n=2,500) found only 26% of executives are confident their data supports AI-generated revenue claims. The confidence gap is a methodology gap. Teams that can answer three questions about their AI influence data close it: (1) which specific CRM field captures AI tool first-touch; (2) what event triggers that field to populate; and (3) what is the population rate across all contacts, not just converted ones.

What makes an AI influence claim CFO-defensible

Three requirements. First, a specific CRM field (not a tag, not a campaign label) that records when a contact first encountered an AI-driven touchpoint. Second, the same field is checked in a sample plan: pull 20 contacts labeled AI-influenced, confirm each one has an event log showing the AI touchpoint. Third, the claim includes a denominator: "34% of pipeline" is weaker than "34% of 142 opportunities that entered Q2 with an AI-influenced contact." The denominator makes the number auditable.

If your team cannot answer these three questions about its AI pipeline claim, the claim is not ready for the board deck. Fix the measurement before making the claim.

What does the QBR-ready attribution summary contain?

The attribution summary you bring to a QBR does not need to show every metric. It needs to show three numbers that survive a challenge.

The first is coverage rate: the percentage of form submissions in the quarter with a verified utm_source. This proves the capture layer was healthy. A coverage rate below 85% means the numbers on every other slide are estimates, not measurements.

The second is source-to-pipeline accuracy: the percentage of opportunities in the quarter with a CRM lead_source that matches the utm_source captured at first contact. This proves the data model did not corrupt what the capture layer collected. According to McKinsey's "Connecting for Growth" study (n=104), only 41% of marketing leaders report mature performance measurement. The source-to-pipeline accuracy check is what separates mature from immature.

The third is influenced pipeline by asset: the dollar value of pipeline that has touched each specific content asset, using the per-post attribution model. This connects content production decisions to revenue. Without it, content strategy is opinion.

Present all three with the methodology note: coverage rate from CRM export, source accuracy from a 50-contact sample, influenced pipeline from the BI path report. Named methodology survives a CFO challenge. "Our platform says so" does not.

How do you prioritize which attribution gaps to fix first?

Not every attribution gap has the same business impact. A missing utm_content field on one landing page costs you content-level granularity for a handful of contacts. A broken utm_source capture on your primary webinar registration form costs you channel attribution for hundreds of contacts per quarter. Fix by impact, not by recency.

Score each gap on two axes: volume (how many contacts are affected per month) and reversibility (can historical data be recovered, or is the window closed). High volume and low reversibility is a critical gap: fix it in the next sprint and accept that past data is lost. High volume and high reversibility means you can recover historical records by re-running the mapping logic once the field is fixed. Low volume and low reversibility is a low priority: note it in the plan log and revisit next quarter.

Setting up CRM properties for asset-level attribution covers the field-by-field configuration for the CRM layer. Once those fields exist, gaps become visible in the coverage rate check rather than hidden in aggregate numbers.

The final output of every quarterly plan is a written gap log: date, field affected, volume estimate, reversibility, and assigned owner. Without a written log, the same gaps surface in the next plan. With a log, you have a 90-day remediation record to present alongside the coverage rate.

Methodology

This attribution plan checklist is built from the four-layer architecture described in the per-post content attribution pillar and the operational patterns from the C4 spoke series published at Conversion System in 2026. The statistics cited are drawn from primary research: the Gartner 2026 CMO Spend Survey (n=401, conducted by Gartner Research), the IBM Institute for Business Value study on AI agents (n=2,500, published June 2025), and McKinsey's "Connecting for Growth" study (n=104 marketing leaders, published October 2024).

The capture-layer test protocol (test submission with plan-specific UTMs, 85% coverage threshold, five-field verification) is a reproducible procedure any marketing ops team can run without purchasing additional tooling. The CRM consistency check (50-contact export, three failure mode lookup) requires only spreadsheet access to CRM data. Neither requires vendor-specific features.

The 85% coverage threshold is a practical floor, not an industry standard. Teams with clean UTM infrastructure typically see 92-97% coverage. Teams that have not audited in over six months often see 60-75%. The threshold gives you an actionable target; the gap log gives you the path to close it.

Run this attribution plan checklist at the start of each quarter before building the QBR deck. The plan takes two to four hours for a team that has never run it. After the first pass, subsequent quarters run faster because the gap log carries forward the known issues and their remediation status. Treat the first plan as the calibration run. If you want help building the data model that makes this check repeatable, start with the free AI plan.