Skip to content

feat(outro): nudge users to run locally, confirm events, then deploy - #1065

Draft
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-self-driving/featoutro-add-test-locally-and-deploy-ceda10
Draft

feat(outro): nudge users to run locally, confirm events, then deploy#1065
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-self-driving/featoutro-add-test-locally-and-deploy-ceda10

Conversation

@posthog

@posthog posthog Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Problem

  • Every successful wizard run — 15,874 completions across 11,400 distinct users in the last 30 days — ends on the same outro, which links docs, a dashboard, and a notebook but never asks the user to do the one thing that makes the install real: run the app, confirm events arrive, then ship.
  • The steps after the outro (mcp → slack-connect → keep-skills) are all housekeeping. No run-locally / first-event / deploy nudge exists anywhere in the default flow.
  • The gap is also a telemetry blind spot: the success path fires no wizardCapture event of its own, so the drop-off between "wizard finished" and "live events flowing" can't be measured.

Changes

  • Activation CTA added to the integration success outro's nextSteps: run locally and trigger the events you instrumented → confirm they land → commit and deploy. Tone modelled on the existing SourceMapsOutroScreen.
  • Project-scoped live-events link surfaced as the outro's primaryLink, so the user lands on their own event stream. primaryLink renders on its own triple-click-selectable line in scrollback via getExitLine, so the URL survives the alt-screen teardown on exit; the checklist bullets stay clean prose.
  • New wizard: activation cta shown event fired when the success outro is built, making the activation moment measurable for the first time.
  • Warehouse-source suggestions (previously the only nextSteps content) are folded in as additive bullets — unchanged behaviour when no source is detected.

No new screens or steps: both OutroScreen and getExitLine already render nextSteps/primaryLink generically, so this is content, not architecture.

Test plan

  • Updated warehouse-suggestion.test.ts: activation CTA is unconditional, warehouse bullet is additive, and the live-events primaryLink is project-scoped.
  • pnpm build && pnpm test (programs + TUI suites) green; pnpm fix clean.

Created with PostHog Desktop from this inbox report, addressing #79165.

The default integration outro handed users a docs/dashboard/notebook link
but never asked them to do the one thing that makes the install real: run
the app, confirm events arrive, then ship. Add a two-beat activation CTA to
the success outro's nextSteps plus a project-scoped live-events primaryLink,
and fire a `wizard: activation cta shown` event so the previously
unmeasurable post-install activation moment becomes a signal.

Both surfaces (OutroScreen + getExitLine scrollback) render nextSteps and
primaryLink generically, so the CTA survives the alt-screen teardown on exit.
Warehouse-source bullets are folded in as additive items.

Generated-By: PostHog Code
Task-Id: 1c06ec7d-6c58-4046-83a2-aad9ca219c26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants