Skip to content

chore(revenue-analytics): add deprecation banner and hide promo surfaces#17016

Merged
rafaeelaudibert merged 1 commit into
masterfrom
posthog-code/deprecate-revenue-analytics
May 26, 2026
Merged

chore(revenue-analytics): add deprecation banner and hide promo surfaces#17016
rafaeelaudibert merged 1 commit into
masterfrom
posthog-code/deprecate-revenue-analytics

Conversation

@rafaeelaudibert
Copy link
Copy Markdown
Member

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

  • Replace the legacy "beta warning" snippet at contents/docs/revenue-analytics/_snippets/rev-analytics-beta-warning.mdx with a deprecation CalloutBox (type="caution"). The snippet is already included across all the Revenue analytics docs pages, so every page now shows the notice.
  • Add the same CalloutBox to the docs hub at src/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

  • Deleted src/pages/revenue-analytics/index.tsx (marketing landing page) and src/hooks/productData/revenue_analytics.tsx. Removed the corresponding entries from useProducts, the analytics category in productNavigation.ts, hero carousel slots and analyticsHandles, Home/Board, Home/Control, Home/Test/Demos, and ProductsTest.
  • Removed the <Link to="/revenue-analytics"> cell from src/hooks/competitorData/posthog.tsx (was rendered as the monetization_analytics value in product comparisons).
  • Dropped the Revenue Analytics topic mapping from Questions/TopicsTable.
  • Removed the revenue_analytics slides from product-managers.json / product-directors.json presentations.
  • Removed revenue-analytics from src/lib/productInterest.ts and the "Revenue Analytics is included with Data Warehouse" pricing note in gatsby/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-analytics from the data-warehouse paragraph.
  • posthog-ai/example-prompts.mdx: removed the Revenue analytics prompt section.
  • posthog-ai/tools.mdx: removed the filter_revenue_analytics tool row.
  • settings/access-control.mdx: removed Revenue analytics from the supported-resources list.

Internal link suggestions

  • Removed 21 Revenue Analytics rows from .claude/skills/InternalLinkData.csv.

Redirects

  • Added /revenue-analytics → /docs/revenue-analytics in vercel.json so the deleted marketing page (and any external inbound links to it, like the exa.md customer quote) keeps working.

Kept intentionally

  • Blog posts referencing Revenue Analytics (per the task brief).
  • The docs themselves (contents/docs/revenue-analytics/*) and their nav sidebar in src/navs/index.js, so users actively on the product can still read setup/troubleshooting docs until removal.
  • The revenueAnalyticsFeatures definition and the revenue_analytics rows in competitor data files — they're still wired through ProductComparisonTable, which contents/blog/posthog-vs-amplitude.mdx references directly.
  • useFeatureOwnership mapping (team ownership label, not a customer-facing link).
  • Vale linting exceptions for "Revenue Analytics" capitalization (docs still reference it).

Test plan

  • Build the site locally (pnpm start) and confirm:
    • /revenue-analytics redirects to /docs/revenue-analytics
    • /docs/revenue-analytics and every child page show the deprecation banner
    • Home page, hero carousel, and product menus no longer surface Revenue analytics
    • contents/blog/posthog-vs-amplitude.mdx still renders the Revenue analytics comparison row
  • pnpm test-redirects passes
  • pnpm check-links-post-build does not flag broken /revenue-analytics outbound links

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
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 25, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview May 25, 2026 07:35PM

@github-actions
Copy link
Copy Markdown
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.

Note: Too many findings to show inline. See the Job Summary linked above.

File Errors Warnings Suggestions
contents/docs/data-warehouse/start-here.mdx 0 11 0
contents/docs/new-to-posthog/revenue.mdx 0 15 0
contents/docs/posthog-ai/example-prompts.mdx 0 13 0
contents/docs/posthog-ai/tools.mdx 2 16 0
contents/docs/revenue-analytics/_snippets/rev-analytics-beta-warning.mdx 2 2 0
contents/docs/settings/access-control.mdx 4 12 0
contents/handbook/docs-and-wizard/onboarding-docs.mdx 0 6 0
contents/handbook/growth/cross-selling/cross-sell-motions.md 24 65 0
contents/handbook/growth/cross-selling/error-tracking-cross-sell.md 3 34 0
contents/handbook/growth/sales/grow-an-account.md 0 16 0
contents/handbook/growth/sales/product-enablement.md 6 31 0
contents/handbook/growth/sales/utilization-by-business-type.md 0 60 0
contents/handbook/growth/sales/why-buy-posthog.md 2 15 0
contents/handbook/growth/use-case-selling/data-infrastructure.md 9 30 0
contents/handbook/growth/use-case-selling/growth-and-marketing.md 34 67 0
contents/handbook/growth/use-case-selling/product-intelligence.md 13 49 0
contents/handbook/growth/use-case-selling/use-case-selling.md 0 1 0
contents/handbook/which-products.md 6 9 0
contents/teams/blitzscale/objectives.mdx 1 7 0

@rafaeelaudibert rafaeelaudibert merged commit 6216535 into master May 26, 2026
19 checks passed
@rafaeelaudibert rafaeelaudibert deleted the posthog-code/deprecate-revenue-analytics branch May 26, 2026 23:01
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.

2 participants