feat(surveys): create survey cross-sell opportunity logic

[adboio]

Problem

adding "opportunity detection" logic & button to support survey x insights cross sell.

user sees "Ask users why ->" on an insight, which prompts posthog AI to create a survey to help them improve conversion

Changes

new opportunity logic detects the "best" insight on a given dashboard to propose a survey, by this logic:

1. get all insights on a dashboard
2. filter only funnel insights
3. calculate overall conversion rate, filter only funnels with < 50%
4. return funnel with lowest conversion rate

SurveyOpportunityButton opens posthog AI, prompting to create a survey to understand/fix low conversion

How did you test this code?

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Changelog: (features only) Is this feature complete?

[adboio]

• feat(surveys): add cross-sell to funnel insights #41699
• feat(surveys): create survey cross-sell opportunity logic #41694 👈 (View in Graphite)
• feat(surveys): add cross-sell button to funnel insights #41703 : 1 other dependent PR (#41873 )
• feat(surveys): add FK for linked_insight_id #41708
• feat(surveys): add linked_insight_id field #41689
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[wiz-7ad640923b]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Total	-

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[github-actions]

Size Change: +38 B (0%)

Total Size: 3.41 MB

ℹ️ View Unchanged

Filename	Size	Change
frontend/dist/toolbar.js	3.41 MB	+38 B (0%)

_{compressed-size-action}

[github-actions]

🔍 Migration Risk Analysis

We've analyzed your migrations for potential risks.

Summary: 0 Safe | 0 Needs Review | 1 Blocked

❌ Blocked

Causes locks or breaks compatibility

posthog.0905_survey_add_linked_insight
  │  └─ #1 ✅ SeparateDatabaseAndState
  │     Wrapper operation - see nested operations for risk: RunSQL, RunSQL
  │     database_operations: RunSQL, RunSQL
  │     └─ #2 ⚠️ RunSQL: RunSQL with ALTER may cause locks
  │     └─ #3 ⚠️ RunSQL: CREATE INDEX CONCURRENTLY is safe (non-blocking)
  │
  └──> ⚠️  COMBINATION RISKS:
       ❌ BLOCKED: #2 RunSQL mixed with other operations    RunSQL with
       DDL (CREATE INDEX/ALTER TABLE) should be isolated in their own
       migration to avoid lock conflicts.
       ⚠️  INFO: Migration is marked atomic=False. Ensure data
       migrations handle failures correctly.

Last updated: 2025-11-18 17:57 UTC (80bde47)