Analytics & Revenue Signals | Custory Changelog

We've added PostHog and Stripe as automation-ready signal sources so your team can respond to real product usage and revenue movement without monitoring those tools separately. Instead of checking dashboards, spotting changes, and manually translating them into journey work, Custory can now pull those signals into automations and help your team act faster. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Analytics & Revenue**, then use them inside [Automations](https://app.usecustory.com/automations).

## What's New

**PostHog snapshots.** Custory can now pull structured analytics snapshots from PostHog — event volume changes for a specific product event, and top events in a selected window. This helps you spot shifts in usage that may signal onboarding friction, stronger activation, feature adoption changes, or unexpected drop-offs.

**Stripe monitoring.** Custory can now pull structured Stripe snapshots for subscription activity, payment failures, and refund activity — giving teams a clearer view of the commercial side of the customer journey, especially where churn risk or refund patterns point to deeper product or experience problems.

**Structured summaries with severity.** Each analytics action returns more than raw numbers. Custory creates a summary with a headline, plain-language explanation of what changed, comparison windows, key metrics, a severity signal, and a recommended item type for follow-up. Instead of asking "did something change?", your team gets a clearer answer to "what changed, how serious is it, and what should we do next?"

These signals are designed to work with the rest of your automation steps. After fetching a PostHog or Stripe snapshot, you can create a new insight in Custory, open a Jira, Linear, or GitHub task, or send a Slack message to the team — so the signal immediately becomes tracked follow-up work inside the same workflow.

## Why it matters

Good teams don't just map customer experience — they watch for evidence that the experience is changing. With PostHog and Stripe connected to automations, Custory helps you move from passive reporting to active response. Important usage and revenue signals can shape the journey while there's still time to do something about them.

We've added PostHog and Stripe as automation-ready signal sources so your team can respond to real product usage and revenue movement without monitoring those tools separately. Instead of checking dashboards, spotting changes, and manually translating them into journey work, Custory can now pull those signals into automations and help your team act faster. Connect from [Manage Integrations](https://app.usecustory.com/manage-integrations) under **Analytics & Revenue**, then use them inside [Automations](https://app.usecustory.com/automations).

## What's New

**PostHog snapshots.** Custory can now pull structured analytics snapshots from PostHog — event volume changes for a specific product event, and top events in a selected window. This helps you spot shifts in usage that may signal onboarding friction, stronger activation, feature adoption changes, or unexpected drop-offs.

**Stripe monitoring.** Custory can now pull structured Stripe snapshots for subscription activity, payment failures, and refund activity — giving teams a clearer view of the commercial side of the customer journey, especially where churn risk or refund patterns point to deeper product or experience problems.

**Structured summaries with severity.** Each analytics action returns more than raw numbers. Custory creates a summary with a headline, plain-language explanation of what changed, comparison windows, key metrics, a severity signal, and a recommended item type for follow-up. Instead of asking "did something change?", your team gets a clearer answer to "what changed, how serious is it, and what should we do next?"

These signals are designed to work with the rest of your automation steps. After fetching a PostHog or Stripe snapshot, you can create a new insight in Custory, open a Jira, Linear, or GitHub task, or send a Slack message to the team — so the signal immediately becomes tracked follow-up work inside the same workflow.

## Why it matters

Good teams don't just map customer experience — they watch for evidence that the experience is changing. With PostHog and Stripe connected to automations, Custory helps you move from passive reporting to active response. Important usage and revenue signals can shape the journey while there's still time to do something about them.