OutreachWebsite Form, HubSpot Chat, External System, Community, Inbound EmailWebinar, Product/Sales Led EventDashboard User CreationExternal System (post-overwrite-reversal)Path: ANNA Thread 019ddf54 joined RAW.STITCH_SALESFORCE + RAW.HOCKEYSTACK + HUBSPOT_DATASHARE + RAW.OUTREACH_DATA + RAW.CHILIPIPER_DATA + ANALYTICS.DBT.MART_PROSPECTS + SNAPSHOTS.SALESFORCE.LEAD (SCD2). 257,849 new-logo leads across FY20–FY26.
Stage taxonomy: Aligned to Sarah's MART_PROSPECTS HubSpot lifecycle (Subscriber 01 → Lead 02 → MQL 03 → Opp Opened 05 → Won 16 / Paid 17). Stage 04 (SQL) skipped — Sarah's data shows n=1 in 12 months. Web Visit dropped (HockeyStack methodology artifact — fires on Outreach email clicks, structurally misleading for outbound segments). Subscriber inverted to "New Logo" = 100 − Subscriber reach (% of segment that is not yet a HubSpot subscriber). Click any stage label in the heatmap for full definition.
Real-owner rule: USER.ISACTIVE=TRUE AND USERTYPE='Standard' AND TERMINATION_DATE__C IS NULL/future AND user is NOT SVC Integrations or any *Integrations service user. SVC Integrations is explicitly excluded (75% of all rows in MART_PROSPECTS — the dominant data-hygiene gap on prior cuts).
FY26 = corrected: The FY26 cohort applies strict LEADSOURCE overwrite reversal. The "Other" segment in FY26 (1,415 leads) is the visible attribution-corruption surface — most originated as External System and were clobbered to Outreach at sequence entry; not heuristically reclassified into Inbound.
HockeyStack coverage gap (resolved): data ended 2025-12-15, leaving Web Visit null for FY26 cohorts. Web Visit is now dropped from the funnel (the email-click contamination made it noise anyway), so the gap no longer affects the visualization.
ChiliPiper coverage gap: data starts 2025-09-16. For FY24 and FY25 Jan–Aug, stage 8 (Meeting Booked) uses an SFDC Task/Event heuristic. The `meeting_source_breakdown` field per cell distinguishes ChiliPiper vs heuristic counts.
Outreach attribution path: Outreach prospects don't carry SFDC IDs — joined to Lead via email only. Sequence enrollment within 90d before lead_created_at filtered out.
Owner-24h is a proxy: No LEADHISTORY raw table; LEAD.SYSTEMMODSTAMP within 24h of CREATEDDATE is used instead.
10x test: FY24 outbound actuals overlaid on FY26 base. Answers "if we restart cold outbound at FY24 volume on today's pipeline, what does it look like?"