docs: Emphasize importance of tracking signup events in onboarding and custom event docs#15386
Merged
willwearing merged 5 commits intomasterfrom Mar 2, 2026
Conversation
Adds an action callout before the custom events section emphasizing the importance of explicitly tracking signup events. Many customers (even large companies) fail to instrument proper signup events, which are critical for measuring activation, retention, and revenue.
… sections Adds a new first section encouraging teams to instrument growth events (especially user signups) before optimizing other analytics setup. This addresses a common gap observed across customer calls where even large companies miss capturing proper signup events, making it difficult to measure activation, retention, and LTV.
…ection Adds an action callout in the Getting HogPilled guide emphasizing that signup events should be the first custom event instrumented. Based on TAM feedback that many customers — even large companies — fail to properly capture signup events, relying on autocapture alone.
…version goals intro
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 14 warnings, 5 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 3:28 | warning | Use 'MDX' instead of 'mdx'. | Vale.Terms |
| 5:53 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 23:19 | warning | 'pageleaves' is a possible misspelling. | PostHogBase.Spelling |
| 65:135 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 90:158 | warning | 'unecessary' is a possible misspelling. | PostHogBase.Spelling |
| 98:74 | warning | 'autocapure' is a possible misspelling. | PostHogBase.Spelling |
| 128:4 | warning | 'When should I send events from the server vs. the client?' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 138:141 | warning | Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. | PostHogBase.ProductNames |
contents/docs/new-to-posthog/getting-hogpilled.mdx — 0 errors, 3 warnings, 3 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 3:24 | warning | Use 'MDX' instead of 'mdx'. | Vale.Terms |
| 17:22 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 29:4 | warning | 'Choosing your North Star metric' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 43:85 | warning | Avoid trivializing words. 'easy to' can sound dismissive to the reader. | PostHogDocs.Trivializers |
| 60:1 | suggestion | Address the reader directly. Use 'you' instead of 'the user'. | PostHogDocs.DirectAddress |
| 145:13 | suggestion | Address the reader directly. Use 'you can' instead of 'users can'. | PostHogDocs.DirectAddress |
contents/docs/product-analytics/best-practices.mdx — 0 errors, 4 warnings, 1 suggestions
| Line | Severity | Message | Rule |
|---|---|---|---|
| 2:8 | warning | Capitalize 'Product Analytics' for PostHog's product. Use 'Product analytics' for the general industry concept. | PostHogBase.ProductNames |
| 87:110 | warning | Avoid trivializing words. 'easily' can sound dismissive to the reader. | PostHogDocs.Trivializers |
| 89:288 | warning | Avoid trivializing words. 'easy to' can sound dismissive to the reader. | PostHogDocs.Trivializers |
| 112:15 | suggestion | Address the reader directly. Use 'you can' instead of 'users can'. | PostHogDocs.DirectAddress |
| 117:20 | warning | 'IPs' is a possible misspelling. | PostHogBase.Spelling |
willwearing
approved these changes
Mar 2, 2026
willwearing
deleted the
docs-writer-ai-update-2026-02-27T22-37-27-813Z-ydcabm
branch
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.
Summary
This PR adds guidance across multiple docs pages to highlight the importance of explicitly instrumenting signup/growth events. This addresses feedback from customer calls where even large companies were found to be missing proper signup event tracking, which impacts their ability to measure activation, retention, and revenue.
Changes
1.
contents/docs/getting-started/send-events.mdxuser_signed_up) should be instrumented first2.
contents/docs/product-analytics/best-practices.mdx3.
contents/docs/new-to-posthog/getting-hogpilled.mdx4.
contents/docs/web-analytics/conversion-goals.mdxWhy this matters
user_signed_upevent, it's difficult to measure activation rates, build retention cohorts, and calculate customer lifetime valueThis PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.