Fire Docs Visited Plausible event on every docs page view#308
Open
lencioni wants to merge 1 commit into
Open
Conversation
Adds an onRouteDidUpdate client lifecycle hook that fires the "Docs Visited" custom event whenever the user lands on or navigates to a page under docs.happo.io. This lets us use docs visits as a top-of-funnel goal in Plausible (HAP-852). The tracker library is still lazy-loaded once and initialized only once; subsequent route changes reuse the cached module. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Summary
Companion to happo/happo-view#3812 for HAP-852.
Fires a
Docs VisitedPlausible custom event whenever the user lands on or navigates to a page underdocs.happo.io. This lets us use docs visits as a top-of-funnel goal in Plausible (alongsidePricing Viewed,Trial Signup, etc.) so we can measure conversion rate by source rather than raw visits.Implementation
onRouteDidUpdateclient-module lifecycle hook so the event fires on both initial load and client-side route changes.pathnameas previous).pathas a Plausible custom prop so we can break the event down by section of the docs.init()is called only once; subsequent navigations reuse the cached module via a memoizedgetTracker()promise.Test plan
Made with Cursor