> 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/elements/guides/multiple-placements.md).

# Multiple Placements

Show more than one offer panel on a page and address each one.

### Name each placement

Add the `data-presentation-ref` attribute to each `<cg-elements>` element. Use the value of `presentation.ref` from the offer response.

```html
<cg-elements data-presentation-ref="checkout-primary"></cg-elements>
<cg-elements data-presentation-ref="checkout-secondary"></cg-elements>
```

### Address each placement

Pass the same value to `getElement()`.

```js
const primary = getElement('checkout-primary');
const secondary = getElement('checkout-secondary');

primary.render(primaryOfferResponse);
secondary.render(secondaryOfferResponse);
```

Each placement has its own handlers, selection, and state. A call on one placement never changes another.

### Single placement

If the page has one panel, omit the attribute and omit the argument.

```html
<cg-elements></cg-elements>
```

```js
const cgElement = getElement();
```

{% hint style="warning" %}
Do not put two `<cg-elements>` elements without `data-presentation-ref` on one page. Both claim the default placement. The last element wins.
{% endhint %}

### Register once

Call `registerElements()` one time for the whole page. All placements share its settings.


---

# 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/elements/guides/multiple-placements.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.
