> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/sources/sources-catalog/web/containers/best-practices/common-container-strategies.md).

# Common Container Strategies

Container strategies for common setups.

A Container Strategy is the layout of the Web Container of a site. Following you will find recommended Container Strategies for common types of websites and businesses.

## Ecommerce

Ecommerce websites require a mix of personalization, analytics and conversion Tags. To optimise website performance it is recommended to use three Containers.

| Container        | Type     | Placement                  | Tags                            |
| ---------------- | -------- | -------------------------- | ------------------------------- |
| Head Container   | `<head>` | All pages                  | A/B-testing and personalization |
| Body Container   | `<body>` | All pages or catalog pages | Analytics and tracking          |
| Funnel Container | `<body>` | Funnel pages               | Conversion                      |

With this setup it is possible to avoid conversion Tag JavaScript snippets on catalog pages—this results in smaller Container file sizes and therefore quicker loading times for SEO relevant catalog pages.

## Publisher

Publisher websites primarily require analytics Tags. Therefore it is recommended to only use one Container.

| Container      | Type     | Placement                  | Tags                   |
| -------------- | -------- | -------------------------- | ---------------------- |
| Body Container | `<body>` | All pages or catalog pages | Analytics and tracking |

Using one `<body>` Container helps to have minimal impact on the page loading time, which is crucial for SEO of Content pages like news articles.

In case A/B-testing and personalization Tags are used, the additional implementation of a `<head>` Container is recommended.


---

# 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://doc.commandersact.com/features/sources/sources-catalog/web/containers/best-practices/common-container-strategies.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.