> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/implementation/headless/initialization/multiple-instances.md).

# Multiple instances

In some cases, you may need to run two different EdgeTag instances on the same shop. This requires initializing each EdgeTag with a unique EdgeTag URL. Below are some examples of how to manage this situation. We recommend including the destination in all your calls from the start if you anticipate this scenario.

{% code title="Initializing site A and B" %}

```javascript
import { init } from '@blotoutio/edgetag-sdk-js'

init({
    edgeURL: 'https://a.mysite.com',
    disableConsentCheck: true
})

init({
    edgeURL: 'https://b.mysite.com',
    disableConsentCheck: true
})
```

{% endcode %}

{% code title="Will send PageView to both instances" %}

```javascript
import { tag } from '@blotoutio/edgetag-sdk-js'

tag('PageView')
```

{% endcode %}

{% code title="Will send PageView only to instance A" %}

```javascript
import { tag } from '@blotoutio/edgetag-sdk-js'

tag('PageView', {}, {}, { destination: 'https://a.mysite.com' })
```

{% endcode %}


---

# 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:

```
GET https://docs.edgetag.io/implementation/headless/initialization/multiple-instances.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
