chore(revenue-analytics): add deprecation banner and hide promo surfaces#17016
Merged
Merged
Conversation
Mirrors PostHog/posthog#59917 on posthog.com. - Add deprecation banner to /docs/revenue-analytics hub and the rev-analytics-beta-warning snippet that's included across all Revenue analytics docs pages (removal on or after June 30th, 2026). - Remove the /revenue-analytics marketing landing page and add a vercel.json redirect to /docs/revenue-analytics so existing inbound links keep working. - Drop Revenue analytics from product listings, hero/board/control carousels, navigation, ProductsTest, competitor-data outbound link, product-managers/directors presentations, productInterest tracking, and the data-warehouse pricing note in gatsby/rawMarkdownUtils. - Remove Revenue analytics from internal handbook cross-sell and sales playbooks (use-case selling, cross-sell motions, sales enablement, why-buy, account growth). - Strip Revenue analytics rows from the InternalLinkData CSV used by the suggest-links skill. - Drop the "Revenue analytics" section from data-warehouse/start-here, new-to-posthog/revenue, posthog-ai/example-prompts and tools, and access-control settings docs. Keep the docs themselves and existing blog references intact so in-flight users still have a path to read the docs (with the deprecation banner) until removal. Generated-By: PostHog Code Task-Id: 6b2df717-0440-4f77-919e-37c229e4bb93
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 106 errors, 459 warnings, 0 suggestions in your markdown Full report → · Copy the Job Summary code block into an LLM to batch-fix issues.
|
arthurdedeus
approved these changes
May 26, 2026
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
Mirrors PostHog/posthog#59917 on posthog.com. Revenue analytics is being deprecated — the dashboard will be removed on or after June 30th, 2026. This PR adds the deprecation notice to our docs and hides Revenue analytics from product listings, navigation, cross-sell playbooks, and other promotional surfaces.
Docs deprecation banner
contents/docs/revenue-analytics/_snippets/rev-analytics-beta-warning.mdxwith a deprecationCalloutBox(type="caution"). The snippet is already included across all the Revenue analytics docs pages, so every page now shows the notice.CalloutBoxto the docs hub atsrc/pages/docs/revenue-analytics.tsx.The banner copy mirrors the language used in the in-product banner: we're not stepping away from revenue, we're refocusing on exposing revenue properties on persons and groups so any insight, SQL query, or PostHog AI / MCP agent can build the right dashboard per use case.
Removed from product/marketing surfaces
src/pages/revenue-analytics/index.tsx(marketing landing page) andsrc/hooks/productData/revenue_analytics.tsx. Removed the corresponding entries fromuseProducts, theanalyticscategory inproductNavigation.ts, hero carousel slots andanalyticsHandles,Home/Board,Home/Control,Home/Test/Demos, andProductsTest.<Link to="/revenue-analytics">cell fromsrc/hooks/competitorData/posthog.tsx(was rendered as themonetization_analyticsvalue in product comparisons).Questions/TopicsTable.revenue_analyticsslides fromproduct-managers.json/product-directors.jsonpresentations.revenue-analyticsfromsrc/lib/productInterest.tsand the "Revenue Analytics is included with Data Warehouse" pricing note ingatsby/rawMarkdownUtils.ts.Removed from internal handbook playbooks
which-products.md,use-case-selling.md,data-infrastructure.md,growth-and-marketing.md,product-intelligence.md,grow-an-account.md,product-enablement.md,utilization-by-business-type.md,why-buy-posthog.md,cross-sell-motions.md,error-tracking-cross-sell.md,onboarding-docs.mdx,teams/blitzscale/objectives.mdx.Other docs cleanup
data-warehouse/start-here.mdx: removed the Revenue analytics section in "Unify customer data".new-to-posthog/revenue.mdx: removed the "Revenue analytics dashboard" section and the cross-link to/docs/revenue-analyticsfrom the data-warehouse paragraph.posthog-ai/example-prompts.mdx: removed the Revenue analytics prompt section.posthog-ai/tools.mdx: removed thefilter_revenue_analyticstool row.settings/access-control.mdx: removed Revenue analytics from the supported-resources list.Internal link suggestions
.claude/skills/InternalLinkData.csv.Redirects
/revenue-analytics → /docs/revenue-analyticsinvercel.jsonso the deleted marketing page (and any external inbound links to it, like theexa.mdcustomer quote) keeps working.Kept intentionally
contents/docs/revenue-analytics/*) and their nav sidebar insrc/navs/index.js, so users actively on the product can still read setup/troubleshooting docs until removal.revenueAnalyticsFeaturesdefinition and therevenue_analyticsrows in competitor data files — they're still wired throughProductComparisonTable, whichcontents/blog/posthog-vs-amplitude.mdxreferences directly.useFeatureOwnershipmapping (team ownership label, not a customer-facing link).Test plan
pnpm start) and confirm:/revenue-analyticsredirects to/docs/revenue-analytics/docs/revenue-analyticsand every child page show the deprecation bannercontents/blog/posthog-vs-amplitude.mdxstill renders the Revenue analytics comparison rowpnpm test-redirectspassespnpm check-links-post-builddoes not flag broken/revenue-analyticsoutbound links