> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/sources/sources-catalog/import-conversions/conversions-files-importer.md).

# Conversions files importer

If you wish to share your data via flat file feed integration, please use a CSV feed format, following the structure below.

{% hint style="info" %}
The CSV format is based on the comma-separated value. The header must be declared in the first row of the file, it is recommended that headers are provided in the lower case and don't contain spaces.
{% endhint %}

Files can be uploaded to the Commandersact FTP or downloaded from your own FTP by CommandersAct. Get in touch with your Account Manager to agree the integration method that is best for you.

Use our CSV conversion importer connector to configure the FTP import.

### Structure of the file:

#### 1 file with 1 line per product (conversion item)

Each line in the file should be a distinct product (conversion item) with their unit price and quantity. Transactions that include several products should be split into multiple lines, sharing the same conversion\_id.

Example:\
conversion\_ID\_1, conversion\_item\_1,\
conversion\_ID\_1, conversion\_item\_2,\
conversion\_ID\_1, conversion\_item\_3,

{% hint style="danger" %}
Be sure you are using exactly the same headers as in this example CSV file:
{% endhint %}

{% file src="/files/JMXtuX8WTy3m525v70Dh" %}
Template CSV conversions import
{% endfile %}

{% hint style="danger" %}
Some columns are **required**, please check this [link](/features/sources/sources-catalog/import-conversions/api-conversions-and-product-catalog.md) to see which fields are required or not.
{% endhint %}

{% hint style="warning" %}
Please sort your file and group it by conversion ID (all conversion items related to conversion\_ID\_1 then all conversion items related to conversion\_ID\_2 etc...)
{% 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://doc.commandersact.com/features/sources/sources-catalog/import-conversions/conversions-files-importer.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.