signals-scout-revenue-analytics

Monitors PostHog revenue analytics for upstream sync failures, capture regressions, and config drift.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-revenue-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signals-scout-revenue-analytics
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-revenue-analytics
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-revenue-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Revenue analytics in PostHog is a derived product with no event stream of its own, so when a Stripe sync stalls or a revenue event stops firing, dashboards silently show wrong numbers and finance teams act on stale data. This Skill acts as an upstream watchdog that detects those failures and files validated, high-confidence reports.

Core Features & Use Cases

  • Upstream sync monitoring: Detects failed, stuck, or cancelled Stripe and payment-platform warehouse sources before stale MRR and gross revenue reach finance dashboards.
  • Capture regression detection: Validates revenue event volume against 14-day trends and checks whether revenue, currency, or subscription properties stopped flowing.
  • Config and data-quality checks: Flags missing subscription properties, currency mix anomalies, broken Stripe-customer-to-person joins, missing deferred revenue periods, and test-account contamination.
  • Report authoring with dedupe: Authors or edits inbox reports via the report channel, routes them to resolved reviewers, and maintains a scratchpad memory so future runs avoid duplicates.
  • Use Case: A Stripe source silently fails overnight; the scout detects the stalled sync, quantifies which revenue dashboards are reading stale, appends the revenue-specific impact to the existing warehouse report, and records a scratchpad pointer for the next run.

Quick Start

Run the revenue analytics scout against this project to check Stripe source health, revenue event capture, and goal progress, then report any validated findings.

Frequently Asked Questions about signals-scout-revenue-analytics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor PostHog revenue analytics for stale data?

Run this scout to check Stripe source status via external-data-sources-retrieve, review sync logs for recurring failures, and query revenue_analytics managed views. It files an inbox report only for validated findings with quantified impact.

How to detect a revenue event capture regression in PostHog?

The scout compares the configured revenue event against top_events and validates drops with a 14-day query-trends window. It also checks event_properties to distinguish a missing event from a revenue property that stopped flowing.

What MCP scopes does the revenue analytics scout need?

It requires read-only analytics scopes plus signal_scout_internal:write for the scratchpad and signal_scout_report:write for emit-report and edit-report. It uses the signals-scout MCP tool family along with warehouse and analytics query tools.

Why is my PostHog MRR chart empty while gross revenue works?

This usually means the revenue event configuration lacks a subscriptionProperty, so PostHog cannot group charges into subscriptions. The scout detects this pattern and reports it when the team has been live long enough to notice.

When does the scout skip reporting a revenue finding?

It skips sandbox Stripe sources, intentional event renames, expired goals, reporting currency changes, and anything already covered by a live inbox report or a noise/addressed scratchpad entry. Low-confidence observations become scratchpad memories instead.