> 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-signals.md).

# Element Signals

XCE provides a custom Javascript API called `signal layer` that gets added to the global namespace when our script is loaded. This is used as an abstraction layer for us to scale a performant integration.

There are three signal types available: `set` , `listen` and `update`

These are objects pushed to the signal layer by calling `signalLayer.push()` . Before calling the signal layer we first must initialize it like so:

```javascript
window.signalLayer = window.signalLayer || [];
```

Each signal object will be conformed by two main properties:

* `signal` - Type of signal(`set` , `listen` or `update`)
* `element` - The element tag name we want to publish to(`xce-protection-offer`)

Any additional properties will be depending on the signal we are working with, so please see the following guidelines on how to use set, listen and update signals and what their specific attributes are.

{% hint style="warning" %}
Each variable declared within the signal layer object will persist only as long as the visitor remains on the current page.
{% endhint %}

{% hint style="info" %}
See Element manipulation for instructions on passing state between pages to the element
{% endhint %}


---

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