> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/data4sales.md).

# Data4Sales

## Cobertura

* :flag\_uy: Uruguay
* :flag\_ar: Argentina
* :flag\_br: Brasil
* :flag\_cl: Chile
* :flag\_co: Colombia
* :flag\_ec: Ecuador
* :flag\_mx: México
* :flag\_py: Paraguay
* :flag\_pe: Perú

## Integración

Conectamos tu eCommerce y tienda física para unificar datos transaccionales y crear identidades únicas de clientes. Nuestra tecnología combina comportamiento, predicción y contexto para generar audiencias y activar campañas multicanal personalizadas desde un solo lugar. Gracias a la inteligencia artificial, anticipamos necesidades, detectamos oportunidades y fortalecemos la lealtad del cliente.

Contacto comercial

* :flag\_uy: :flag\_py: Guzman Valdes - <guzman.valdes@data4sales.com>
* :flag\_cl: :flag\_pe: Gonzalo Zigaran - <gonzalo.zigaran@data4sales.com>
* :flag\_ar: Ariel Leiro - <ariel.leiro@data4sales.com>
* :flag\_mx: :flag\_co: Alejandra Delgado - <alejandra.delgado@data4sales.com> <br>

## Requerimientos y proceso para alta

El cliente debe contactar al equipo de Data4Sales para solicitar las IP de conexión con Fenicio. Luego, debe incluir esta información en un ticket dirigido al equipo de soporte de Fenicio y solicitar la habilitación de las mismas para API V1.

## Más información

[Sitio de Data4Sales](https://www.data4sales.com/)


---

# 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://guia.fenicio.help/integraciones-y-herramientas/marketing-automation-and-crm/data4sales.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.
