BSP Lead Source Performance

💎

Implications (per memory rule 1)

🎯 Bucket touched	ALL — but ST 'Existing Customer' (4,024) skews everything
⚠️ Problem	ST shows 'Existing Customer' as 48.3% of customer base — that's the migrated HCP bucket masquerading as repeat. True attribution lives in HCP where 52% of leads have BLANK lead source.
💰 $ at stake	$35K/mo Google Ads spend optimizing against a 11% slice of customer base (Smart Bidding starvation) — see BSP_HCP_Intelligence_Report 🤖 Smart Bidding card.
✅ Action unlocked	Backfill 'Original Lead Source' custom field in ST from HCP where available. Don't trust the 'Existing Customer' bucket as a source — it's HCP migration overflow.

📊 Full bucket diagram + 4 data-integrity findings: BSP HCP Intelligence Report (📊 The Buckets · 📅 Timeline · 💸 LTV · 🔍 Why this matters · 🎯 The 4 Findings)

ST Completed Revenue

...

ST Completed Jobs

...

Unique Lead Sources (ST)

...

HCP Blank Lead Source

...

Loading data quality analysis...

ST Performance by Lead Source (completed jobs only)

Lead Source	Customers	Completed Jobs	Revenue	Avg Ticket	Flag
Loading...

HCP Customers by Lead Source

Lead Source	Customers	Total LTV	Avg LTV
Loading...

ST Customer Count by Source (titan.customers)

Lead Source	Customers
Loading...

What this tells us: Smart Bidding and marketing attribution depend on clean lead source capture. Blank sources mean the call/web intake never captured where the lead came from. Imported Default Campaign is legacy HCP migration placeholder and should not be used for attribution decisions.