> 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/analyze-with-dashboards/custom-explores/creating-custom-calculations.md). # Creating custom calculations ### Introduction This article will walk you through how to create custom metrics directly within an explore dataset. {% hint style="success" %} The default timezone in Chord Analytics for OMS timestamps is UTC, whereas the OMS UI displays EST. Within Chord Analytics, we've added additional timezone options for some of our timestamps but not for `Order Approved Date`. Custom time zones can be created with a custom field and can be submitted as a feature request. {% endhint %} ### Create a custom calculation While Chord's data engineers have built plenty of out-of-the-box metrics for you to explore, we understand that you may find yourself needing to create custom calculations. Navigate to your Chord Analytics account and choose the 'Explore' page with the data points that you are looking to include in your custom metric. On the right-hand panel, select the measures that will be part of your calculation. For example, Abandoned Cart = # of Customers That Added Product to Cart- # of Customers who Check out, both of these measures will need to be selected in order to create a calculation. You will see the measures pop up in the 'Data' field at the bottom of the screen.

Hit 'Add Calculation' on the right hand side of the 'Data' bar.

Create your custom calculation.

Click **Save** {% hint style="success" %} if you have any questions or need help, please reach out to us at {% 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/analyze-with-dashboards/custom-explores/creating-custom-calculations.md?ask=&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.