> 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/campanas/iframe-events.md).

# Eventos de iframe

Los anunciantes pueden rastrear eventos en sus anuncios. Estos eventos se gestionan programáticamente directamente en el navegador del cliente con la ayuda de JavaScript.

## Eventos

### creativeDisplayed

{% hint style="info" %}
Esto solo está disponible para **Interstitial de página completa para escritorio** y **Interstitial de página completa para móvil** (*DFPI/MFPI*) campañas de formato de anuncio con **URL del iframe** variación.
{% endhint %}

Cuando el anuncio se muestra al usuario, se envía un mensaje al iframe llamado `creativeDisplayed`.

Puedes rastrear este evento dentro de tu iframe usando el siguiente script, que agrega un detector de eventos para capturar el mensaje enviado una vez que el anuncio se muestra al usuario.

```html
<script>
        function readMessage(event) {
            console.log("evento readMessage");
            console.log("origen: " + event.origin);
            console.log("datos: " + event.data);
        }

        if (window.addEventListener) {
            // Para navegadores web compatibles con los estándares
            window.addEventListener("message", readMessage, false);
        } else {
            window.attachEvent("onmessage", readMessage);
        }
</script>
```

## Ejemplo - Interstitial de página completa

```html
<!DOCTYPE html>
<html>
<head>
    <!-- PARTE DEL EVENTO -->
    <script>
        function readMessage(event) {
            console.log("evento readMessage");
            console.log("origen: " + event.origin);
            console.log("datos: " + event.data);
            var message = "Recibimos el mensaje: '" + event.data + "' de '" + event.origin + "' (ahora estamos en el iframe del anunciante)";
            console.log(message);
            document.getElementById("received-message").innerHTML = message;
            // el anunciante de ie quiere actualizar algún elemento
        }
        if (window.addEventListener) {
            // Para navegadores web compatibles con los estándares
            window.addEventListener("message", readMessage, false);
        } else {
            window.attachEvent("onmessage", readMessage);
        }
    </script>
    <!-- FIN DE LA PARTE DEL EVENTO -->
</head>
<body>
    <h1>Mi encabezado de prueba del iframe</h1>
    <p>Mi párrafo de prueba del iframe</p>
    <p id="received-message">Esperando el mensaje</p>
</body>
</html>
```

<figure><img src="https://1161515667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi4Is92LUeIhwL8XSbGLq%2Fuploads%2Fi5JLh6QPqPkUvOLOHp8C%2Fexoclick_interstitial_iframe_creativeDisplayed.gif?alt=media&amp;token=d6f5f9a9-5944-4365-a1eb-3e6bfdca2520" alt=""><figcaption></figcaption></figure>


---

# 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/campanas/iframe-events.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.
