> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/advertisers/es/preguntas-frecuentes-para-anunciantes/problemas-comunes/discrepancias-en-el-trafico-de-operadores-moviles.md).

# Discrepancias en el tráfico de operadores móviles

La identificación de usuarios de operadores móviles (3G/4G) es una función compleja.

Utilizamos tanto nuestras propias bases de datos de direcciones IP como las de terceros para identificar operadores, y requiere un mantenimiento constante. Dependiendo de la herramienta que estés usando y de cómo esa herramienta esté identificando a los usuarios (direcciones IP, nombre del ISP…), es posible que veas diferencias. Por esta razón, no podemos garantizar la precisión de esta identificación.

Si necesitas una precisión del 100%, te sugerimos en su lugar que uses tus propios rangos de direcciones IP, con la [segmentación por rangos de IP](/advertisers/es/campanas/creacion-de-una-campana/create-campaign-step3.md#ip-ranges) opción que se encuentra en el paso 6 “Configuración avanzada” al crear/editar tu campaña.


---

# 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.exoclick.com/advertisers/es/preguntas-frecuentes-para-anunciantes/problemas-comunes/discrepancias-en-el-trafico-de-operadores-moviles.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.