> For the complete documentation index, see [llms.txt](https://docs.roadwayai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadwayai.com/getting-started/how-roadway-works.md).

# How Roadway Works

## Modeling

The following diagram provides a high-level overview of the work Roadway conducts under the hood.

<img src="/files/G7cMwZD8EOmk22MAkqQl" alt="10,000 ft view of Roadway&#x27;s Data Modeling " class="gitbook-drawing">

The "Roadway Data Modeling" arrow above does a lot of heavy lifting, so what's going on there? Among other things, this means:

* cleaning and validating raw data&#x20;
* sessionizing page views and calculating your attribution model
* constructing historical revenue snapshots
* linking attribution to elements of your growth funnel

The above architecture drives Roadway's default metrics definitions, but if you have existing metric logic already modeled, you can share those definition with Roadway to be mirrored with the data available.


---

# 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.roadwayai.com/getting-started/how-roadway-works.md?ask=<question>&goal=<endgoal>
```

`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.
