> For the complete documentation index, see [llms.txt](https://docs.ltvnumbers.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ltvnumbers.com/misc-instructions/uploading-data-into-ltv-numbers/creating-a-custom-data-format.md).

# Creating A Custom Data Format

1. In LTV Numbers' side menu, click "Upload" to get to the Data Uploader
2. Click the "Choose File" button and select your file(s with the same format)
3. Click "New" under Choose Format
4. Enter a clear and descriptive name for your data format by including relevant identifying information such as the platform name, data type (contact or payment), and the purpose of this custom format
5. Select the Data Type and click Add
6. For each relevant section, assign the data from your file to the field in LTV Numbers
   * E.g. assign the Date Created in your file to the CONTACT Created Datetime in LTV Numbers
7. Verify each field is assigned properly by checking the preview from your file. If the file preview is not enough, open your file.
8. Click Save and Next to save your custom data format and begin the upload process for your file 
   * Note: this process may take some time to complete


---

# 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.ltvnumbers.com/misc-instructions/uploading-data-into-ltv-numbers/creating-a-custom-data-format.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.