The terms used in Henkan Chat and in this documentation, from A to Z.
| Term | Meaning |
|---|---|
| Active context | The GA4 property, test site, Contentsquare project or similar that Henkan remembers for the rest of a conversation, shown as a chip in the message box. |
| Approval card | The Henkan needs your OK card shown before a tool runs that changes data or is set to Ask before running. |
| Connection | One account in one tool, for example one Google account for GA4. You can have several connections per tool. |
| Connector | The built-in or custom integration that creates connections to a tool. Managed on the Tools page. |
| Confidence interval (95% CI) | The range in which the true uplift lies with 95% confidence. If it includes 0, the result is not significant. |
| Flow | An automated investigation: a trigger, steps on the canvas and outputs. |
| Henkan agent block | A flow block where Henkan analyses earlier results as a given role, optionally calling tools. |
| Key event | GA4's name for a conversion. Henkan uses keyEvents and sessionKeyEventRate (conversion rate per session). |
| MCP (Model Context Protocol) | An open standard that lets AI assistants call tools. Henkan Chat uses MCP servers as connectors, and is itself an MCP server for Claude, ChatGPT and Cursor. |
| Member / Owner | Roles in an organisation, decided by Henkan in Henkan Account. Members use its connectors; owners also add, change and remove them. |
| Merge block | A flow block that waits for several branches before continuing. |
| Organisation | The company space you work in: it owns the connectors and the request limit, while conversations and flows stay private to each person until they share them. See Organisations. |
| Parameter | A named value such as {client} or {ga4_property} used in a flow's blocks, so one flow can serve several sites or clients. |
| p-value | The probability of seeing a difference at least this large if there were no real difference. Below 0.05 means significant at 95%. |
| Run | One execution of a flow, with its trigger, block outputs and report. |
| SRM (sample ratio mismatch) | When the traffic split between variations differs significantly from the planned split. Results of a test with an SRM can't be trusted; Henkan reports them as "inconclusive (SRM)". |
| Tool | One action a connection offers, for example ga4_run_report or kameleoon_get_experiment_results. |
| Tool call | One use of a tool by Henkan while answering, listed under Used N tools. |
| Trigger | What starts a flow: Manual, Schedule or When… an event happens. |
| Uplift | The relative change of a variation's conversion rate compared with the reference. |
| Voice of customer (VoC) | Customer feedback from surveys, such as NPS, CSAT and CES scores and open-text answers. |