> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/integration/es/data-api/api-overview/timeouts-and-graceful-fallback-behaviour.md).

# Tiempos de espera y comportamiento de retransmisión suave

## Tiempos de espera

En el caso poco probable de latencia por parte del Epsilon Retail Media sistema, es una buena práctica asegurarse de haber implementado un tiempo de espera en su Epsilon Retail Media solicitud para garantizar que no haya un impacto negativo en la experiencia de su cliente.

Esto lo define el minorista; sin embargo, Epsilon Retail Media por lo general se aconseja implementar un tiempo de espera de 400-500 ms para garantizar que el tiempo de entrega al cliente no se vea afectado.

## Comportamiento de reanudación gradual

Epsilon Retail Media puede que no tenga anuncios para el contexto de la solicitud de anuncio en su sitio web. Debe asegurarse de que su sitio web no muestre un área grande vacía donde se espera el anuncio. Esto se aplica tanto a los anuncios de productos como a los de banner.

<figure><img src="/files/qxtA8xF4DBJSa9TSJWDJ" alt="Successfully displayed ad.png" width="100%"><figcaption><p>Imagen del anuncio de banner servido correctamente</p></figcaption></figure>

En el raro caso de que no se sirva el anuncio de banner anterior, debe estar preparado para ocultar el área del anuncio de banner y asegurarse de que no se sirva un espacio en blanco a su cliente.

<figure><img src="/files/Oqc7EyzzBn9fMeoT96tm" alt="Banner not served by Epsilon Retail Media.png" width="100%"><figcaption><p>Imagen del anuncio de banner no servido</p></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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.citrusad.com/retail-media-interface/integration/es/data-api/api-overview/timeouts-and-graceful-fallback-behaviour.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.