fix(dashboard): unblock the install step and point Home at it

Merged
IZ
8d ago
+205-156

Release of three staging commits (cherry-picked with -x from 83618f128, f7e356c78, 979eff4b2).

Why: across the last 30 days of signups (153 users, Postgres joined to ClickHouse), users whose site received data came back 24h–8 days after signup 60% of the time; users with a site but no data, or no site, came back 9% of the time. Samples are small and this is correlation. Since the current onboarding shipped on Oct 5, 40 users created a site and 21 went live. Most installs happened outside the onboarding Connect step.

  • fix(dashboard): let new users connect their app while Databunny reads the site. The checklist kept "Connect your app" pending, with the text "Ready once the brief is", for as long as the optional AI site read ran. Connect is now active as soon as the site exists and sits above the read row, so focus goes straight to it. ConnectApp already explains that the prompt improves once the brief lands. Until a site exists, the card only shows the website form, with no list of pending rows.
  • fix(dashboard): name the manual install option in Connect. "Or install it yourself" becomes "Or add the script tag or SDK yourself". The agent-first layout stays: the agent prompt is the path most people pick (18 users vs 6 for the script tag over 30 days). The E2E selector is updated.
  • feat(dashboard): prompt Home to install tracking until a site has data. Users with no site most often ended on Home (median 20s), where every stat read zero. Home now shows a single prompt above the stats until any site has page views: "Install tracking on {domain}" linking to the site's install gate, or "Add your website" opening the existing dialog.

Verification: dashboard tsc clean, dashboard unit tests 207 pass, Biome clean, commit hooks pass. These have not been rendered in a browser locally; I didn't start the dev server. The Dashboard Playwright CI jobs cover onboarding and website setup.

Summary by cubic

Unblocks the onboarding Connect step so new users can install tracking while the AI site read runs, and prompts Home to steer users without data toward the install step. This targets retention: over the last 30 days, users whose site received data returned 60% of the time vs 9% for those without (small samples, correlation only).

Changes

  • Connect is active as soon as a site exists and is listed above the site-read row; until a site exists, the checklist shows only the website form.
  • The manual install option is renamed to "Or add the script tag or SDK yourself", and the E2E selector is updated.
  • Home shows a single prompt — "Install tracking on {domain}" or "Add your website" — above the stats until any site has ever had data.