Repository navigation
[feat] Post-signup survey v2 (Signup 3 - Agents) - #5085
Conversation
Repoint the EE post-signup questionnaire from the retired 'Signup 2' survey to 'Signup 3 - Agents'. Resolve questions by PostHog question id with a keyword fallback instead of by position, so reordering or rewording a question in PostHog no longer silently mis-maps answers. Write v2 person properties (company_size_v2, user_role_v2, agent_experience_v2, intent_* booleans, referral_source_v2, is_icp_v2) and drop the stale v1 interest mapping. Drop the transient fallback page: any not-ready outcome (PostHog blocked, survey missing, fetch error, watchdog) now silently redirects into onboarding. Shorten the readiness watchdog from 10s to 3s. Claude-Session: https://claude.ai/code/session_01AuS2c7XQhyECUGg3afeZQ9
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Context
The EE post-signup questionnaire was built for the old "Signup 2" PostHog survey, whose questions frame the pre-pivot product (prompt management, no-code building, LLM evaluation). It mapped answers to PostHog properties by question position and exact option strings, and that had already drifted: two interest options no longer matched their strings, so those flags were never set. When PostHog was blocked or slow, the user hit a "we couldn't load the questionnaire, click Continue" fallback page that dropped the answers anyway.
Changes
The form now targets a new survey, "Signup 3 - Agents", whose questions fit the post-pivot product: company size, role, agent-building experience, what they want to do with Agenta, and how they heard about us.
Questions resolve by PostHog question id with a keyword fallback, instead of by position. Reordering or rewording a question in PostHog no longer silently mis-maps answers. An unrecognized question just renders generically.
Person properties are now a v2 set:
company_size_v2,user_role_v2,agent_experience_v2, fiveintent_*booleans,referral_source_v2, andis_icp_v2(same ICP shape as before, computed on the new option strings). The old v1 interest mapping is removed.The fallback page is gone. Any not-ready outcome (no PostHog key, survey missing, SDK blocked, fetch error, or the readiness watchdog firing) now silently redirects the user into onboarding instead of showing a dead-end page. The watchdog dropped from 10s to 3s, so a new user never waits long on a questionnaire we can skip.
Scope / risk
EE only. Touches the
PostSignupForm/directory only. The survey content lives in PostHog, so question wording can change there without a deploy (the id-based mapping tolerates it). "Signup 2" is untouched in PostHog, so already-released code keeps working until this merges.Tests / notes
pnpm lint-fixgreen;types:checkshows no new errors.NEXT_PUBLIC_POSTHOG_API_KEYand recreate the web container.How to QA
Prerequisites: EE dev stack with
NEXT_PUBLIC_POSTHOG_API_KEYset. The "Signup 3 - Agents" survey is already live in PostHog.Steps:
/post-signup.Expected result: The new questions render (company size as buttons, role, agent experience, what you want to do, how you heard). Submitting sends a
survey sentevent carrying the v2 person properties and lands you on/apps.Edge cases: Block PostHog with an adblocker, or use an env with no key. You should be redirected straight into onboarding with no fallback page and no more than ~3s wait.
Automated tests: None for this flow (the survey is server-driven). Verified manually plus lint and types.
https://claude.ai/code/session_01AuS2c7XQhyECUGg3afeZQ9