AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

understanding-billing-usage

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.

Original source
posthog
License
MIT
Pinned revision
cac7c80a9e5b73484d18eda1bffb47297c938e0c

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read posthog--understanding-billing-usage at revision cac7c80a9e5b73484d18eda1bffb47297c938e0c, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

references/spike-alert-mechanics.md

Usage alert links

Usage spike, drop, and change alert emails open the organization usage dashboard with alert-relevant filters. The link usually has this shape:

/organization/billing/usage?usage_types=["event_count_in_period"]&date_from=2023-12-16&date_to=2024-01-14&interval=day
  • usage_types is a JSON array of billing usage type identifiers.
  • date_to is the alert day, shown at the right edge of the chart.
  • date_from is usually about 29 days before the alert day.
  • interval=day matches the daily Billing usage series.

Use these URL parameters to recreate the Billing view first. Then drill into the customer-visible product data for the affected usage type, project, and day.

When validating an alert day, compare it to prior days in the same day class:

  • weekday alert day: compare to prior weekdays in the visible range
  • weekend alert day: compare to prior weekend days in the visible range

This avoids treating normal weekday/weekend traffic shape as a root cause. Keep the answer grounded in what the Billing usage tools return, and call it a reconstruction when you do not have the exact alert row.