Integrations Overview
Connect the tools that already capture your product behavior.
Integrations bring events, sessions, revenue, and product context into Oriyn so personas and experiments are grounded in real behavior.
What To Connect
Oriyn works best when it can see the behavior that matters to a product decision: events, session paths, activation markers, billing outcomes, and enough product context to understand the experience.
| Data | Why it matters |
|---|---|
| Product events | Reveal actions, funnels, activation, and repeated behaviors. |
| Session evidence | Shows friction, navigation paths, and confusing surfaces. |
| Revenue signals | Connects product behavior to account value and conversion. |
| Product context | Tells agents what the product does and what a proposed change affects. |
Sync Model
After a data source is connected, Oriyn ingests source data, resolves identity, updates the behavioral graph, and refreshes derived intelligence. The CLI exposes this as a single idempotent command.
oriyn sync
oriyn statusPrivacy Boundary
Connect only data you are allowed to process. Oriyn is designed for product intelligence inside your organization; outputs should be treated as customer data and handled according to your data policies.