Attribution When the CRM Owns the Truth
A company runs 60 programs across email, paid social, webinars, and field events. Deals close in the CRM, and revenue is booked there. Marketing has historically reported 'first-touch' pipeline from a single lead-source field. The CFO notes that webinar-sourced pipeline looks tiny while sales keeps crediting webinars in call notes, and that multi-touch deals are invisible. Two marketers maintain hand-built spreadsheets that disagree with the platform. There is no agreed definition of 'marketing-sourced' vs 'marketing-influenced'. Attribution windows are undefined. The CRM sync runs every 15 minutes but only syncs a subset of opportunity fields.
1. Design an attribution approach that the CFO will trust, given the CRM owns revenue and the platform only sees a subset of fields.
Read the worked answer
The core problem is a definitional gap, not a tooling gap. Fix definitions before models.
- Write down the rules. Define marketing-sourced (marketing created/qualified the opportunity or the originating contact) vs marketing-influenced (any marketing touch inside the window on any contact role). Define the attribution window (e.g. 90 days touch, 180 days for events) and the credit split (e.g. even or position-based). Get CFO sign-off on paper.
- Fix the data feed. The 15-minute sync with partial opportunity fields is the real constraint. Expand synced opportunity fields (amount, stage, close date, source) and ensure all contact roles on an opportunity are associated, not just the primary. Without contact roles you cannot see multi-touch deals at all.
- Use native multi-touch where possible. Configure first-touch, lead-creation, and multi-touch models on the same opportunity set so the CFO can compare. Keep one canonical model and label the others as diagnostic.
- Reconcile to CRM revenue. Attribution totals must tie back to closed-won amount in the CRM for the same period. Publish a reconciliation line showing unattributed and marketing-sourced sums equal CRM totals.
- Kill the spreadsheets. One source of truth, documented, refreshed on a schedule.
The judgement: you cannot out-report bad definitions, and you cannot attribute revenue you cannot see. Fix the sync scope and the definitions first; the model choice is secondary.
2. Webinar pipeline looks understated. Where would you look first, and what would you change?
Read the worked answer
Understated event pipeline almost always has a data-capture cause before a modeling cause. Check in order:
- Program membership vs lead source. If webinar attendance only sets a program status and never writes an acquisition or attribution field, first-touch models will never see it. Ensure attendance writes a touchpoint the model reads.
- Contact roles. If the webinar attendee is a secondary contact on the opportunity and only the primary is synced, the touch is invisible. Sync all contact roles.
- Window. Events have long consideration cycles. A 90-day first-touch window may expire before the deal closes. Use an event-appropriate window.
- Deduplication. If attendees were created as net-new leads that later merged into existing contacts, the touch history may have been lost in the merge. Audit merge behavior.
- Model choice. First-touch structurally undervalues mid-funnel events. Compare against multi-touch to confirm the gap is model-driven, not data-driven.
Then change: capture attendance as an attributable touchpoint, sync all contact roles, set an event window, and report webinar influence alongside sourcing so sales credit and marketing credit reconcile.