> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/smartwords.md).

# Smartwords

Smartwords are dynamic content that's **created from a variable or a calculation**.&#x20;

Some dynamic data can be created by you and some is maintained by Conducttr over the course of the exercise.

| Dynamic data created by YOU                                                                                                                                       | Dynamic data maintained by CONDUCTTR                                                                                                                      |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Strictly speaking these are Exercise Smartwords and are either uploaded to the Smartwords table by the designer or updated by Exercise Control during an exercise | This data relates to personas, players, calculations and other possible data variables that Conducttr maintains but which you can access in your exercise |

{% hint style="warning" %}
Note that some variables are only accessible only with Colibri.
{% endhint %}

## Naming conventions

Many variables can be accessed using curly brackets - e.g. `{ }`

Calculations and more advanced variables need to use pipes - e.g. `||`

The `{ }` are really just a shorthand to reduce some of the complexity of using the long form version with pipes `||`

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="/feature-documentation/designing-and-running/smartwords/exercise-smartwords.md">Exercise Smartwords</a></td><td>Variables you or exercise control set, so content can be updated live without editing every inject</td></tr><tr><td><a href="/feature-documentation/designing-and-running/smartwords/player-smartwords.md">Player Smartwords</a></td><td>Pull data from calculations and questions into content using <code>{variable}</code>, <code>{team.variable}</code>, and <code>{session.variable}</code></td></tr><tr><td><a href="/feature-documentation/designing-and-running/smartwords/conducttr-engine-smartwords.md">Conducttr Engine Smartwords</a></td><td>Advanced nested smartwords using pipe <code>||</code> syntax, for when a variable needs to reference another variable</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/feature-documentation/designing-and-running/smartwords.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
