> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/model-your-data/dbt-model-reference.md).

# dbt model reference

As a commerce data platform, we empower brands to not only boost revenue and lower customer acquisition cost (CAC), but also deepen their understanding of customers through our infrastructure that exposes predictive insights, revenue forecasting, and customer lifetime value (LTV).

With the always-expanding size of the ***Chord Data Attribute*** catalog, it is vital that users understand the fields getting used in your Chord reporting and the nuances that come with that.

The following documentation provides the definition(s) and methodology for all ***available Chord Data attributes***.

These attributes and their definitions can be accessed via the *Explore* view of any report, by clicking on the "i" icon for any field.

![](https://2938842758-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5Oy2IAsu7IvAGAlWgC36%2Fuploads%2Fgit-blob-f330740fa6d7920db82b1f80d6e703513fed93ec%2Fchord-oms-1.png?alt=media)

{% hint style="info" %}
💡 If you or your team have additional questions please reach out to **<help@chord.co>.**
{% 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.chord.co/model-your-data/dbt-model-reference.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.