> 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/tracking/set-up-tracking/configure-custom-uri-schemes.md).

# Configurar esquemas URI personalizados

**Esquemas de URI**, que aparecen en el protocolo de la URL, se usan para indicar a un *cliente*, como un navegador web, cómo interpretar todo lo que aparece después del protocolo de una URL (es decir, todo lo que viene después de `://`). Si usas la API Page Load de impact.com y quieres utilizar esquemas de URI personalizados, tendrás que especificar en la aplicación web de impact.com qué esquemas quieres incluir.

<div data-with-frame="true"><figure><img src="https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-50500e0c05347cae50075039e1c285bf18146af6%2F0d4703b4888e1b0b4ec339fe76c47848126a700c321274e9c50fc56f09221ea1.png?alt=media" alt=""><figcaption></figcaption></figure></div>

impact.com utiliza estos esquemas de URI para garantizar que el tráfico se vincule al programa correcto y para distinguir los clics internos entre páginas web del tráfico nuevo o referido. Sin embargo, si no especificas los esquemas que quieres utilizar, la API Page Load podría devolver errores para las URL que contengan esquemas de URI personalizados, o impact.com podría rechazarlas por completo.

También deberías considerar especificar los esquemas de URI personalizados si tienes la intención de usar [el seguimiento del tráfico directo](https://help.impact.com/brand/es/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/set-up-direct-traffic-tracking.md) en tu programa.

#### Especificar esquemas de URI

1. En la barra de navegación superior, selecciona ![](https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[Perfil de usuario] → Configuración**.
2. A la derecha, en *Seguimiento*, selecciona **General**.
3. En *Esquema de URI*, introduce los esquemas de URI personalizados que tienes previsto incluir. Separa los valores con comas.
4. Selecciona **Guardar**.

   <div data-with-frame="true"><figure><img src="https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FHbgAfZPbR0HnZhksGX7P%2FScreenshot%202026-05-06%20at%2012.03.17.png?alt=media&amp;token=f9cbe6f3-5feb-4fe1-bb9d-cc86ea6b762c" alt="" width="338"><figcaption></figcaption></figure></div>

Los sitios de pasarelas de pago, como PayPal, se consideran automáticamente tráfico interno y no es necesario añadirlos manualmente.

{% hint style="info" %}
**Nota**: impact.com no acepta esquemas de URI que no sean de tipo HTTP (por ejemplo, `file` o `mailto`).
{% 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://help.impact.com/brand/es/what-would-you-like-to-learn-about/platform-features/tracking/set-up-tracking/configure-custom-uri-schemes.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.
