> 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/data-api/api-overview/timeouts-and-graceful-fallback-behaviour.md).

# Timeouts and graceful fallback behaviour

## Timeouts

In the unlikely event of latency by the Epsilon Retail Media system, it is best practice to ensure that you have implemented a timeout on your Epsilon Retail Media request to ensure there is no negative impact to your customer experience.

This is defined by the retailer, however, Epsilon Retail Media typically advises a timeout of 400-500ms to be implemented to ensure your time to customer is not impacted.

## Graceful fallback behaviour

Epsilon Retail Media may not have ads for the context of the ad request on your website. You should ensure that your website does not display a large empty area where the ad is expected. This applies to both product and banner ads.

<figure><img src="https://3425731255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBL8KNnR5myWfc4R7Zbbq%2Fuploads%2Fgit-blob-5e49bc1b1f4a6f39a1c99ab2035cfc4d7dce67db%2FSuccessfully_displayed_ad.png?alt=media" alt="Successfully displayed ad.png" width="100%"><figcaption><p>Successfully served banner ad image</p></figcaption></figure>

In the rare event the above banner ad is not served, you should be prepared to hide the banner ad area, and ensure a blank space isn't served to your customer.

<figure><img src="https://3425731255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBL8KNnR5myWfc4R7Zbbq%2Fuploads%2Fgit-blob-dcc2860e50caa7f819ac2ca7129038f2baf2937f%2Fbanner-not-served.png?alt=media" alt="Banner not served by Epsilon Retail Media.png" width="100%"><figcaption><p>Banner ad not served image</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.citrusad.com/retail-media-interface/integration/data-api/api-overview/timeouts-and-graceful-fallback-behaviour.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.