> 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/demo-hub.md).

# Demo Hub

We’re excited to introduce our **Demo Hub**, a collection of guided tours that make it easier to get the most out of the New UI.

## What is the Demo Hub?

The Demo Hub is a collection of **guided product tours** that bring our platform to life. Instead of reading pages of documentation, take a guided tour of the platform in a streamlined flow without making any changes to your account or campaigns.

Try it out:

{% embed url="<https://epsilon.storylane.io/hub/demo-hub?utm_source=knowledgebase&utm_medium=documentation&utm_campaign=source>" fullWidth="false" %}

## How to use the Demo Hub

Getting started is simple:

1. **Open the Demo Hub**
2. **Browse by platform area** — tours are grouped by relevant sections.
3. **Select a tour** — each one walks you through a specific feature or workflow.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2Fb5fibVFDq4LIwL3Fe4Zd%2FDemo%20Hub.gif?alt=media&amp;token=36d9a14e-6156-440e-a5ff-75bff4e047af" alt=""><figcaption></figcaption></figure>

New tours are added frequently, so check back often to see what’s new.


---

# 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/demo-hub.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.
