> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PostHog and Stripe

> Connect product usage and revenue signals to Custory so journey decisions can use live evidence instead of static reporting.

PostHog and Stripe bring live product and revenue evidence into Custory.

Use PostHog when customer behavior inside the product should shape the journey. Use Stripe when subscription movement, payment failures, or refunds should do the same.

## PostHog

| Field                | Value                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------ |
| Status               | Available                                                                                  |
| Connection method    | Manual credentials: base URL, project ID, and API key                                      |
| Custory reads        | Event data and project metadata from the connected PostHog project                         |
| Custory writes       | None                                                                                       |
| Automation support   | `event_volume_change`, `top_events`                                                        |
| Required permissions | Read/query access to the selected PostHog project                                          |
| Known limitations    | Event-volume-change needs at least one event name. Results are summaries, not raw exports. |

## Stripe

| Field                | Value                                                                                                                                   |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Status               | Available                                                                                                                               |
| Connection method    | Manual API key, with live/test mode stored on the integration                                                                           |
| Custory reads        | Subscription events, payment failures, refunds, and account mode metadata                                                               |
| Custory writes       | None                                                                                                                                    |
| Automation support   | `subscription_activity`, `new_subscriptions`, `canceled_subscriptions`, `net_subscription_delta`, `payment_failures`, `refund_activity` |
| Required permissions | Read access to the connected Stripe account                                                                                             |
| Known limitations    | Payment-failure and refund metrics do not support quarterly or yearly evaluation periods.                                               |

## What these integrations do

Both integrations feed structured summaries into Custory instead of dumping raw reporting into the journey.

That summary includes:

* What changed
* The comparison window
* A severity level
* A recommended journey item type
* Supporting metrics or event counts
* Links back to the source system

Custory uses that output in metrics, journey updates, and automations.

## When to use each one

Use PostHog when you want to answer questions like:

* Where is onboarding leaking?
* Which events changed after a release?
* Which steps need more evidence before the team acts?

Use Stripe when you want to answer questions like:

* Are new subscriptions rising or falling?
* Are payment failures pointing to checkout or trust problems?
* Are refunds telling you that the promise did not match the experience?

## How to set them up

1. Open **Manage Integrations** in your workspace.
2. Connect PostHog or Stripe with the right credentials.
3. Confirm the project, account, and mode you want Custory to use.
4. Start with one metric or one automation preset the team will actually review.
5. Keep the setup narrow until the signal proves useful.

## What Custory does with the data

### PostHog summaries

Custory can pull:

* Event volume change for named events
* Top events for discovery

The output is a structured snapshot with event counts, unique users, trend direction, severity, and evidence links.

### Stripe summaries

Custory can pull:

* Subscription activity
* New subscriptions
* Canceled subscriptions
* Net subscription delta
* Payment failures
* Refund activity

The output is a structured snapshot with counts or deltas, trend direction, severity, and evidence links back to Stripe.

## Limits

* Neither integration writes data back into PostHog or Stripe.
* PostHog event-volume-change needs at least one event name.
* Stripe payment-failure and refund summaries do not support quarterly or yearly evaluation periods.
* A connected workspace only sees the projects or account data it has been authorized to use.

## Next step

Read [Metrics](/metrics) if you want live metric cards tied to PostHog or Stripe. Read [Automations](/automations) if you want these signals to trigger follow-up.