> 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/installation/bigcommerce/installation.md).

# Installation

### Download template

For the codification step, you can use our BigCommerce template and configure the selectors according to your site.

<a href="https://app.edgetag.io/assets/script-templates/big-commerce/big-commerce.txt" class="button primary" data-icon="down-to-bracket">Download template</a>

{% hint style="warning" %}
BigCommerce templates work for most sites. If you have a custom theme/plugin, please make sure to change the code according to the website.
{% endhint %}

### Adding a template

Now that we have the code ready, let's add it to your BigCommerce.

Select "Storefront" in the BigCommerce dashboard.

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FGhu6tWXKsaXOO2Tckl2k%2Fimage.png?alt=media&amp;token=dbea0596-4ddd-4073-a891-470c6164d7fc" alt=""><figcaption></figcaption></figure>

Select “Script Manager” and Click on “Create a Script”

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2F0gGwqnkEyjaczeG4CFVT%2Fimage.png?alt=media&amp;token=1450c42d-0ed7-465d-8295-502aba6b825b" alt=""><figcaption></figcaption></figure>

We will now need to configure the script.

* Change “location on page” to “Head”; this will ensure that the script will be loaded inside the head tag.
* Change “Select pages where script will be added” to “All pages”; this will ensure that the script will be loaded on all pages
* Change “Script category” to “Analytics”
* Change “Script type” to “Script”
* Paste our template in "Script contents"

<figure><img src="https://1474399258-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZJWZKbUk0hRISkCIj2p4%2Fuploads%2FtppFvsHTT0zQC6ykmWkS%2Fimage.png?alt=media&amp;token=98ff4fdf-dc95-45d9-a5a6-88df03e7fbfc" alt=""><figcaption></figcaption></figure>

Finally, click on the Save button at the bottom.


---

# 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.edgetag.io/installation/bigcommerce/installation.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.