The context graph is the core of inncivio. It is a live, client-specific picture of your platform, your knowledge and your users' behaviour, and every signal, decision and action inncivio produces is rooted in it.
What feeds the context graph
| Source | What it contains |
|---|---|
| Platform structure | Every relevant page of your platform and its structure, refreshed when your platform changes |
| Goals | The objective of each page or journey step |
| Your knowledge | Product documentation, FAQs and help content, connected from Notion, Google Drive or Slack, or uploaded |
| Business context | Constraints, product catalogue, segment priorities and compliance policies |
| Behaviour events | Anonymised footprints: clicks, views, hovers, help opens, order-ticket steps, idle time |
| External data | Market moves, scheduled events, products, services and partners |
What the context graph connects
Analytics tools record events. The context graph records how they relate. It links users (as anonymised footprints), products and instruments, journeys, intentions, decisions and outcomes, so inncivio can see a moment in full: who is acting, on what, with which goal, in which market context, and what happened next.
Why the context graph is important
Goals come first
You define the outcomes that matter on your platform, such as a funded account, a completed order, a submitted loan application or a first trade. Each page and journey step is tied to its goal, and every action is chosen to serve the goal of the current screen.
Your knowledge, scoped to you
Connect your knowledge from Notion, Google Drive or Slack, or upload your product documentation, FAQs and help content. inncivio retrieves the relevant passages when it writes an explanation, so content reflects your actual product, in your tone. Your knowledge is used only for your deployment.
Let us show you how our AI-driven, fintech-focused approach delivers more than just adoption - it drives measurable growth.