ProlyticsConnect Your Data
Connect the product, billing, and reliability source needed for the first question you want Prolytics OS to answer.
Start with the evidence you need
You do not need every source connected before Prolytics becomes useful. Begin with the system that holds the evidence for your first question, then add another source when the investigation crosses between them.
- Connect PostHog to understand activation, engagement, product paths, and where users stop progressing.
- Connect Stripe to understand recurring revenue, subscriptions, failed payments, expansion, contraction, and churn.
- Connect Sentry to understand errors, issue pressure, affected users when available, and application performance.
Each source powers its own Health domain and can support Engine questions on its own. More sources create a wider evidence set. They do not turn timing into causation or make unrelated users the same person.
See what each source unlocks across OS ->
Connect for the question in front of you
If checkout conversion fell, start with PostHog. Add Sentry when reliability may be involved and Stripe when payment completion matters. If MRR changed, begin with Stripe and add product or reliability evidence only when the explanation depends on what happened earlier.
This keeps setup proportional to the decision. Connect enough evidence to answer the question well, not every source simply because it exists.
Understand what multiple sources add
Multiple sources let OS compare supported movement across product behaviour, reliability, and billing. This can help answer whether checkout abandonment moved with application errors, whether failed payments contributed to revenue pressure, or whether activation changed before contraction increased.
Aligned movement can strengthen or weaken a hypothesis. It does not prove that one event caused another. User-level or account-level claims also require enough identity coverage to link records safely.
More sources provide more evidence. They do not make an unsupported conclusion trustworthy.
Connected does not mean every metric is ready
A connection may be healthy while a specific metric still needs history, a confirmed event definition, or stronger identity coverage. Health shows how that limitation affects the metric instead of hiding it behind zero.
If credentials expire, permissions change, or a provider cannot be reached, Connections marks the affected source as requiring attention. Other connected sources remain available. Reconnect or update permissions, then allow the affected metrics to refresh before using them in a decision.
Read-only by design
OS uses read-only access to connected providers. It cannot change product events, modify subscriptions in your Stripe account, issue refunds, delete provider records, or resolve incidents inside those systems.
Read how Prolytics stores and protects service data ->