# Common Container Strategies 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 | `` | All pages | A/B-testing and personalization | | Body Container | `` | All pages or catalog pages | Analytics and tracking | | Funnel Container | `` | 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 | `` | All pages or catalog pages | Analytics and tracking | Using one `` 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 `` Container is recommended. --- # Agent Instructions: 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://doc.commandersact.com/features/sources/sources-catalog/web/containers/best-practices/common-container-strategies.md?ask= ``` 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.