> For the complete documentation index, see [llms.txt](https://docs.verbdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verbdata.com/models/building-a-model/transformations.md).
# Transformations
Transformations allow you to manipulate and create data in your model. They can be created as columns on existing tables using calculated columns or aggregated measures. Transformations can also be created as data views, which will act like Tables.
Transformations must be published to be available in Models and Collections.
## Calculated Column (+)
A calculated column is a column added to every row in the host table. If data is not being ingested in a desired format or further manipulation is necessary, adding a calculated column in a variety of transformations enables filtering, sorting, and manipulation for ease of use.
Once a calculated column is created it can be found in the table list on the left panel.
To create a calculated column on a table, select the “Add Calculated Column” option from the table menu.
## Aggregated Measure 
A calculation that occurs **after** the returned data for a specific tile in a collection is segmented and filtered. This is most often used for calculating marketing related measures like “cost per click” as all filters and segmentations need to be applied in order to determine the relevant aggregated cost and the number of clicks.
Once an aggregated measure is created it can be found in the table list on the left panel.
To create an aggregated measure to a table, select the “Add Aggregated Measure” option from the table menu.
## Data Views
Data Views are Transformations that are stored as Tables in the model.
Once a Data View is created it can be found in the Data Views section on the left panel.
To create a Data View, select the “Add Data View ” button from the left panel.
---
# 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://docs.verbdata.com/models/building-a-model/transformations.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.