7 Moments Where Your Platform Is Losing Revenue
Read the article
Technical Documentation

Integration Guide

You go live in four steps, without changing your core product. The only code you add is the inncivio capture script or SDK, and every step is tested on your staging environment before production.

Step 1 · Account setup (done by inncivio)

We provision your dedicated environment and database instance, with its own AWS KMS encryption key, issue your API keys, and give your operators and desks access to the Console.

Step 2 · Capture integration

You add the capture script or SDK and initialize it on page load. It sends anonymized footprints and journey events only, never identifiers, typed values, amounts or account numbers.

Step 3 · Configuration

Together we define your goals, constraints, business context, compliance policies and client rules. Optionally, you connect your product documentation from Notion, Google Drive or Slack so explanations reflect your product.

Step 4 · Delivery

You choose how actions are consumed: the inncivio in-app layer, your own UI, or the Client API. You name the desks that receive escalations, and we set up control groups and holdouts.

Requirements

  • A valid inncivio API key
  • An HTTPS website or application
  • A Content Security Policy that allows *.inncivio.com

Two ways to start

  • Signals first: the Console and Client API only, with no change to your UI.
  • Signals and Actions: in-product delivery from day one.

You can start with Signals and switch on Actions once the Signals have proven their value.

Ready to See inncivio in Action?

Let us show you how our AI-driven, fintech-focused approach delivers more than just adoption - it drives measurable growth.