Integrations · PostHog
PostHog + Stripe: find who pays and stopped using.
PostHog knows who uses your product. Stripe knows who pays. Keep joins the two and tells you which paying customers are slipping away — before the cancellation shows up in Stripe.
Why usage predicts churn
Most churn dashboards measure what already happened: the cancellation. By then the customer decided weeks ago. The earlier signal is behaviour — a team that logged in daily and now logs in once a week, or an account that paid for three months and never finished onboarding.
That signal lives in your product analytics, not in your billing. Keep reads it from PostHog and puts a dollar amount next to it.
What Keep flags
| — | What it means |
|---|---|
| Usage drop | Activity in the last 7 days fell sharply against the 7 days before. |
| Silent | A paying customer with no activity for a number of days. |
| Never active | A paying customer who never showed up in the product. |
| Forgotten | No visible usage and no recorded contact in HubSpot for a number of days — nobody is watching the account from either side. |
| Dropped a key feature | Stopped using the feature it used most. Needs feature names sent through Keep's activity API. |
How to connect
Connect Stripe first
Stripe gives Keep the list of paying customers and their MRR.
Authorize PostHog
OAuth with read-only scopes (project:read, query:read). US and EU PostHog regions are supported.
Check the match rate
Keep matches PostHog persons to Stripe customers by email and shows how many it could match, so you see the gap instead of trusting a partial number.
Where matching by email falls short
Matching by email works well for products where each paying customer signs in with the same address they pay with. It is weaker in B2B, where one company pays and several people sign in with different addresses.
For those cases, Keep's activity API accepts the Stripe customer id directly from your backend, which removes the guesswork.
Questions
- Does Keep read the content of my PostHog events?
- No. It reads aggregated counts per person — how many actions in the period and when each person was last seen — plus the person's email for the match.
- Do I need PostHog to use Keep?
- No. Stripe alone gives revenue, cancellations, downgrades, and failed payments. PostHog, or Keep's activity API, is what adds the paying-but-inactive signal.
- Does it work with PostHog EU Cloud?
- Yes. Keep supports both the US and EU PostHog regions.
- I use Mixpanel, Amplitude, or Segment. Can I still use Keep?
- Not natively today. You can send usage from your own backend through Keep's activity API, keyed by Stripe customer id or email.
Other integrations
See who is paying and gone quiet.
Connect Stripe and PostHog and get the first list of at-risk accounts, ordered by MRR.