> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/vizzy-studio/use-in-tableau-and-analytics.md).

# Using Vizzy studio apps in Tableau and Analytics

Your visualization is ready. Time to put it in front of people! You can use it in Tableau as a viz extension, and in Trulyp Analytics.

### In Tableau

Studio visualizations are Tableau **viz extensions**: they live on the Marks card of a worksheet, just like a built-in chart type.

1. In the workspace, click **Download TREX** (or the download icon in the Studio overview). You get a `.trex` file.
2. In Tableau, open a worksheet and, in the mark type dropdown on the **Marks** card, choose **Viz Extensions** › **Add Extension**. Use the option for local extensions to open the `.trex` file.
3. Drag your fields onto the extension's encodings on the Marks card. A visualization has at most four encodings, for example a dimension and a measure.

You don't need to publish a visualization to use it in Tableau. The `.trex` points to your Trulyp environment, so later changes you **Save** show up in Tableau without downloading a new file, as long as the slug stays the same.

{% hint style="warning" %}
Changing a visualization's **Slug** changes its address and extension ID, so workbooks that already use it stop working. See [The Studio workspace](/trulyp/vizzy-studio/the-studio-workspace.md#settings).
{% endhint %}

### In Analytics

[**Publish**](/trulyp/vizzy-studio/the-studio-workspace.md#save-publish-download-and-delete) the visualization in the workspace. It then appears under **Studio visuals** in the Visuals tab of the Analytics editor, ready to add to your apps. See [Extensions in Analytics](/trulyp/analytics/visuals/extensions.md).

{% hint style="info" %}
To see **Studio visuals** in Analytics, you need the **Vizzy studio creator** role as well as **Analytics creator**.
{% endhint %}

#### Test before you share

Try the extension in a **non-production workbook** first, with representative data and normal user permissions. Check that:

* Each encoding is mapped to the field you intended.
* Dates, currencies, percentages and large numbers are formatted correctly.
* The visualization still makes sense when filters leave few or no marks.
* Selections and filters behave the way people expect in the dashboard.
* It works well at the size it will have on the dashboard.

{% hint style="info" %}
**Tip:** if a field is ambiguous, describe its business meaning in your prompt rather than relying on its name, for example "monthly recurring revenue" instead of "value".
{% endhint %}


---

# 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://docs.infotopics.com/trulyp/vizzy-studio/use-in-tableau-and-analytics.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.