> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-elements/client-integration/element-display.md).

# Element Display

This page outlines how to get the XCE panel displayed on your web platform

Place a custom HTML element in the desired location in your HTML template. This is where the protection panel will be loaded by XCE.

<pre class="language-html"><code class="lang-html"><strong>&#x3C;!-- protection-offer example -->
</strong><strong>&#x3C;xce-protection-offer>&#x3C;/xce-protection-offer>
</strong></code></pre>

{% hint style="info" %}
The element name can change. The correct name will be provided to you during onboarding.
{% endhint %}

## Using custom attributes

XCE allows partners to use custom HTML attributes on the element to update the state such as UI, provide data for offer retrieval and more.\
\
**Custom attributes will be referenced in their specific integration guides.**

For example, in our protection-offer example we have the `selected` attribute that pre-selects one of the radio input options of the element.

{% hint style="warning" %}
The following custom attributes are just to showcase a scenario and might not be available on your integration.

Please refer to your CSE regarding the available custom attributes for your element.
{% endhint %}

<pre class="language-html"><code class="lang-html"><strong>&#x3C;!-- custom attributes example -->
</strong>&#x3C;!-- with 'yes protection' pre-selected -->
&#x3C;xce-protection-offer selected="option-1">&#x3C;/xce-protection-offer>

&#x3C;!-- with 'no protection' pre-selected -->
&#x3C;xce-protection-offer selected="reject">&#x3C;/xce-protection-offer>
</code></pre>


---

# 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://partner-docs.covergenius.com/xcover-elements/client-integration/element-display.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.