> For the complete documentation index, see [llms.txt](https://ailyze.gitbook.io/ailyze-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ailyze.gitbook.io/ailyze-docs/reference/glossary.md). # Glossary This page explains, in plain language, the research terms you'll meet across Evidano. #### AI Accuracy (Calculate AI Accuracy) A Pro check of how reliably the codebook was applied to your data. #### Codebook The structured set of themes → sub-themes/codes (ideally each with a description) used to label your data. See [Build a codebook](/ailyze-docs/analyze-data/build-a-codebook.md). #### Coding / Labeling Tagging each excerpt or row with the codes it expresses. #### Co-occurrence When two themes or codes show up in the same response. Looking at co-occurrence shows how topics relate and where tensions sit. #### Co-occurrence network A visualization of which themes appear **together**, revealing relationships and tensions. #### CSAT A customer-satisfaction score. A short question that asks how satisfied someone was, usually on a rating scale. #### Deductive coding Starting from themes or codes you already have (a framework) and applying them to your data. The opposite of inductive coding. #### FGD (Focus Group Discussion) A transcript with multiple participants. Evidano can auto-detect FGDs and handle them appropriately. See [Analyze focus groups](/ailyze-docs/common-research-workflows/analyze-focus-groups.md). #### Frequency How often a theme or code appears. Used to prioritize; shown in the codebook table and frequency charts. #### Handoff A built-in button that moves data from one workflow to another (for example **Analyze transcripts**, **Analyze**, **Select Analysis**). #### Hierarchy graph A visualization of how sub-themes/codes nest under themes. #### Inductive coding Letting themes and codes emerge from the data itself, instead of starting from a fixed framework. The opposite of deductive coding. #### Insights / Synthesis / Summary AI-written narrative that interprets the data. **Insights** = project-level headlines; **Synthesis/Summary** = section- or theme-level narrative. #### Methodology A named qualitative approach (for example Reflexive Thematic Analysis, IPA, Grounded Theory) you can attach to a document analysis. #### NPS A customer-loyalty score (short for Net Promoter Score), based on how likely people are to recommend you, on a 0–10 scale. #### Overall analysis (spreadsheets) The survey-wide dashboard that summarizes **every** column. Different from the **per-column results page**, which is the deep dive for a single question. See [Analyze open-ended survey responses](/ailyze-docs/common-research-workflows/analyze-open-ended-survey-responses.md). #### PII Personal information that can identify someone, such as names, phone numbers, or addresses. Evidano can redact PII from transcripts. #### Quote A word-for-word excerpt that illustrates a code. Always verify quotes against the source document before using them in a report. #### Report structure For document analysis: how the report is organized — *Themes + linked questions*, *Questions only*, *Themes only*, or *Questions + themes*. #### Respondent Name/ID The column Evidano uses to attribute quotes to a respondent. #### Response language The language Evidano writes the **report** in (document analysis), independent of your data's language. #### Segment A group you compare results across — department, region, plan, cohort, rating band, or before/after. See [Compare groups](/ailyze-docs/analyze-data/compare-groups-segments.md). #### Segment comparison Comparing your results across segments (groups) to see how answers differ — for example by department, region, or rating band. See [Compare groups](/ailyze-docs/analyze-data/compare-groups-segments.md). #### Segments / Column types (spreadsheets) On **Configure Column Types**, columns are sorted into **Numerical**, **Categorical**, **Text**, **Segments**, **Respondent Name/ID**, or **Not Analyzed**, which decides how each is analyzed and visualized. #### Share as Webpage A Pro feature that creates a public, read-only link to an analysis. #### SRT A subtitle file format (`.srt`). Evidano can translate SRT files. #### Sub-theme A specific idea within a theme (e.g. *"Confusing first screen"*). Evidano uses **sub-theme** and **code** interchangeably. #### Test mode vs Active (AI avatar studies) **Test** records responses for free (for your own testing); **Active** collects real, charged responses. See [Create your first AI Avatar Interviewer](/ailyze-docs/getting-started/create-your-first-ai-avatar-interviewer.md). #### Theme A top-level pattern or topic in your data (e.g. *"Onboarding friction"*). The main unit of a qualitative report. #### Transcript The written text of an audio or video recording. Create one with the transcription workflow, then analyze it. See [Transcribe audio and video](/ailyze-docs/prepare-research-data/transcribe-audio-and-video.md). #### Wallet / Credits Your pay-as-you-go balance for add-ons (transcription, translation, web data, live avatar interviews). See [Plans, Limits & Credits](/ailyze-docs/reference/plans-limits-and-credits.md). #### XLIFF A file format used for translation (`.xliff`). Evidano can translate XLIFF files. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ailyze.gitbook.io/ailyze-docs/reference/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.