> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/es/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/batch-file-upload-name-requirements.md).

# Requisitos de nombres para la carga de archivos por lotes

Cuando subas archivos a impact.com (por ejemplo, contenido de anuncios, archivos FTP, etc.), deberás asegurarte de que estén nombrados correctamente para que nuestro sistema los acepte y procese.

#### Requisitos del nombre del archivo

Los archivos no pueden tener un punto (`.`) en el nombre (por ejemplo, `My.Bulk.Upload.1.19.38.xlsx`). Usa un guion (`-`) o un guion bajo (`_`) entre las palabras en su lugar (por ejemplo, `My_Bulk_Upload_1_19_38.xlsx`).

#### Extensiones de archivo bloqueadas

Estas extensiones de archivo están bloqueadas por impact.com:

* `.php5`
* `.pht`
* `.phtml`
* `.shtml`
* `.asa`
* `.cer`
* `.asax`
* `.swf`
* `.xap`
* `.exe`
* `.zip`
* `.rar`
* `.iso`
* `.tar`


---

# 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://help.impact.com/brand/es/what-would-you-like-to-learn-about/platform-features/submit-and-modify-conversion-data/batch-file-upload-name-requirements.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.