fix(pricing): show AI Observability on the pricing page#17328
Open
posthog[bot] wants to merge 2 commits into
Open
fix(pricing): show AI Observability on the pricing page#17328posthog[bot] wants to merge 2 commits into
posthog[bot] wants to merge 2 commits into
Conversation
After renaming "LLM analytics" to "AI Observability", the product's `handle` was changed to `ai_observability`, but the billing service still exposes it under its original type `llm_analytics`. `useProducts` joins static product data to live billing data on `billingProduct.type === product.handle`, so the join returned `undefined`, leaving the product with no `billingData`/`unit`. Both pricing surfaces filter those out (calculator requires `unit`, accordion requires `billingData`), so AI Observability silently disappeared from /pricing. Decouple the billing-API key from the display handle via a new optional `billingType` field (falling back to `handle` for every other product) and set `billingType: 'llm_analytics'` on AI Observability. Also fix a stale `llm_analytics` reference in a customer's `toolsUsed`. Verified locally: AI Observability now renders in the calculator tabs and the rates accordion with its billing tiers (From $0.00006/event, first 100k free). Generated-By: PostHog Code Task-Id: e5d5edce-1e9b-4f40-9a88-3f53b5ba945f
Contributor
Deploy preview
|
Use a precise structural assertion (`{ billingType?: string }`) instead of
`as any` when resolving the billing-data join key, and pull it into a named
`billingType` local for readability. No behavior change.
Generated-By: PostHog Code
Task-Id: e5d5edce-1e9b-4f40-9a88-3f53b5ba945f
13 tasks
smallbrownbike
approved these changes
Jun 7, 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
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.
Changes
The AI Observability product stopped appearing on /pricing after "LLM analytics" was renamed.
Root cause: the rename changed the product's
handletoai_observability, but the billing service still exposes this product under its original typellm_analytics.useProductsjoins static product data to live billing data onbillingProduct.type === product.handle, so the join returnedundefinedand the product was left with nobillingData/unit. Both pricing surfaces filter those out — the calculator requiresunit(Tabbed.tsx) and the rates accordion requiresbillingData(PricingAccordion.tsx) — so AI Observability silently disappeared.Fix: decouple the billing-API key from the display
handlewith a new optionalbillingTypefield (every other product falls back tohandle, so behavior is unchanged), and setbillingType: 'llm_analytics'on AI Observability. Also fixed a stalellm_analyticsreference in one customer'stoolsUsed.Verified locally: AI Observability now renders in the calculator tabs and the rates accordion with its billing tiers (
From $0.00006/event, first 100k free).Checklist
vercel.jsonCreated with PostHog Code