chore(home): retire the orphaned hero CTA and its flag - #65
Merged
Conversation
HeroCTA rendered a Get Started / Learn more pair gated on the hero-cta-copy multivariate flag. Nothing imported it - the landing page renders components/home/hero.tsx, whose CTAs moved to plan framing in 736c4fa. The flag sat at 100% rollout across four 25% variants, so it looked like a live landing-page test in every flag listing while deciding nothing. That appearance is what led a funnel baseline to record it as running. - delete components/home/hero-cta.tsx - drop the `hero` entry source: the deleted component was its only emitter, so it never recorded anything and no historical volume is affected. A stray ?from=hero now resolves to `direct` like any other unknown value - archive the PostHog flag (id 145657, active false, archived true)
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the flag inventory recorded in #64.
What this removes
components/home/hero-cta.tsx(HeroCTA) rendered a "Get Started" / "Learn more" button pairplus an "or open the full dashboard" link, with the two labels gated on the
hero-cta-copyPostHog multivariate flag.
Nothing imported it. The landing page renders
components/home/hero.tsx, whose CTAs wererewritten to plan framing in 736c4fa ("Create my personalized post plan").
HeroCTAwas anorphan from an earlier version of the hero.
The flag was configured at 100% rollout across four 25% variants, so it presented as a live
landing-page A/B test in every flag listing while deciding nothing (~11
$feature_flag_calledevents per 14 days of residual noise, vs 510 for
onb-welcome-heroand 165 foronb-modal-exit). That appearance is exactly what led a funnel baseline to record it as arunning experiment.
Changes
components/home/hero-cta.tsx.heroentry source fromconfig/entry-sources.ts. The deleted component was itsonly emitter, so it never recorded anything and no historical volume is affected. A stray
?from=heronow resolves todirectlike any other unknown value, via the existingparseEntrySourcefallback.docs/analytics/onboarding-funnel.md(the legacy-heronote now records theretirement),
docs/experiments/log.md(flag inventory marked RETIRED with the flag id),docs/CHANGELOG.md.PostHog
Flag
hero-cta-copy(id 145657) archived:active: false,archived: true,status: ARCHIVED.Last called 2026-08-04. Done before this PR so the flag list is already clean.
A future hero test should be written fresh rather than revived from this one - the retired
variants ("Get Started", "Use Free Tool") predate the plan-framing rewrite.
Checks
pnpm type-checkexit 0.pnpm lint0 errors (2 pre-existing warnings incomponents/shadcn-demo/).No remaining
HeroCTA/hero-ctareferences in code.