> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zelinqa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Information to collect

> Define the structured data your application needs.

**A dimension describes a topic; success information describes a value to obtain.** For example, Budget is a dimension and Available amount is a numeric information item.

| Information | Example value | Use |
| - | - | - |
| Available budget | `2500` | Check whether an offer is suitable. |
| Start date | `"2026-11-01"` | Prepare a schedule. |
| Email address | `"person@example.com"` | Send the requested follow-up. |

<Frame caption="Fictional French-language demo domain in Zelinqa Studio.">
  <img src="https://mintcdn.com/zelinqa-d77427f3/uhQGSGvivNOeuPJJ/images/studio-demo-objective-en.png?fit=max&auto=format&n=uhQGSGvivNOeuPJJ&q=85&s=25123e7dbe624749d3a45f80c86860a6" alt="Home-decoration demo domain configuration" width="1235" height="550" data-path="images/studio-demo-objective-en.png" />
</Frame>

## Configure an information item

On the Studio's **Objective** page, add a **business expectation**: its label, value type, and active primary question. The Studio generates the identifier used by your integration. For a choice question, a choice can map to the value to record.

An exploratory question helps understand a topic without necessarily producing a structured value. **You do not need a success information item for every question.**

## Where does the value come from?

It may come from an analyzed answer, a choice mapped to a value, or already-known data supplied by your integration. Only declare data confirmed when it is actually known.

| Status | Effect |
| - | - |
| `confirmed` | The value is known. |
| `not_applicable` | The information does not apply in this case. |
| `tentative` | The value is provisional and does not satisfy overall success. |
| `conflicted` | A contradiction needs to be resolved. |

<Warning>Declaring an item as success information makes it a condition of overall success, unless excluded or explicitly overridden by your integration. Do not declare every interesting piece of data indispensable.</Warning>

See [Progress and qualification](/en/concepts/qualification) and [SDK examples for known data](/en/guides/answers-context).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.