> For the complete documentation index, see [llms.txt](https://docs.horizon.ipaper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.horizon.ipaper.io/horizon-experience/embedding-horizon.md).

# Embedding Horizon

How to embed a Horizon experience into your webpage

To embed a Horizon experience into your webpage, first make sure it's published. You'll need the following unique identifiers:

* Account name
* [Alias](https://help.horizon.ipaper.io/en/articles/11330925-aliases-how-to-set-up-and-best-practices)

[Use an alias set up in the admin site for the Horizon experience to be embedded.](https://help.horizon.ipaper.io/en/articles/11330925-aliases-how-to-set-up-and-best-practices)

Then, add the Horizon web component into your webpage:

```html
<ip-embed-leaflet alias="[ACCOUNT_NAME]/[ALIAS]"></ip-embed-leaflet>
```

In order for the web component to load, you need to add the Horizon embed script at the bottom of the `body` tag:

```html
<script defer="" src="https://embed.ipaper.io/web.js" type="module"></script>
```

The web component will request the experience through our API and it will be displayed on your webpage.

{% hint style="warning" %}
If you have previously embedded Horizon on your page(s), the custom tag used on the page may be `<ip-embed>` instead of `<ip-embed-leaflet>`.&#x20;

`<ip-embed>` is still supported, but we recommend updating to `<ip-embed-leaflet>` at your earliest convenience.&#x20;
{% endhint %}

#### Content-Security-Policy <a href="#content-security-policy" id="content-security-policy"></a>

If Horizon is embedded on a page that has Content-Security-Policy rules configured, you will need to ensure that you accept all requests going to `*.ipaper.io`. Doing this ensures that all content within the embedded Horizon will load and get rendered.


---

# 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.horizon.ipaper.io/horizon-experience/embedding-horizon.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.
