> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/accountmanagement/container-management/setting-up-a-new-container.md).
# Setting up a new container
Use this guide after completing the initial AdPage setup. It covers creating and configuring one additional container.
{% stepper %}
{% step %}
### Create the container
Open AdPage and add a new container. Agency accounts can first select the client's company, then add the container there.
{% endstep %}
{% step %}
### Connect the Google Tag Manager server container
Connect the AdPage container using your Google Tag Manager server container's base64 configuration code. This lets you configure tracking rules in that server container.
Retrieve the base64 configuration code manually
In Google Tag Manager, open the server container. Go to **Admin** → **Container settings**.
Click **Set up your tagging server**. Copy the displayed configuration code.
{% endstep %}
{% step %}
### Configure the tracking domain
Create a custom tagging server URL for this container. Use a subdomain of the website's root domain.
In your DNS provider, create the CNAME record shown during registration. Copy the displayed **Host** value. Set the record target to `projects.trytagging.com`.
{% hint style="info" %}
You can change the CNAME **Host** in the container settings. The target always remains `projects.trytagging.com`.
{% endhint %}
{% endstep %}
{% step %}
### Install the Tagging Pixel
Replace the website's standard Google Tag Manager snippet with the AdPage Tagging Pixel. The pixel connects the website to its Google Tag Manager web container.
{% hint style="warning" %}
Remove the standard Google Tag Manager snippet. Do not run it alongside the Tagging Pixel.
{% endhint %}
Enter the **Website URL** and **Google Tag Manager Web Container ID**. Generate the installation instructions for your platform.
AdPage provides installations for Shopify, WordPress, WooCommerce, Magento, and Lightspeed. Select **Custom CMS** to get the `` and `` snippets.
{% hint style="info" %}
Use **Copy the installation link** to share instructions with a website developer.
{% endhint %}
{% endstep %}
{% step %}
### Finish the setup
Open the server container dashboard after completing these steps. The container is ready for tracking-rule configuration.
You can defer the tracking domain and Tagging Pixel steps. Complete them later from the server container dashboard.
{% endstep %}
{% endstepper %}
### Next steps
Configure the tracking rules in the connected Google Tag Manager web and server containers.
---
# 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, and the optional `goal` query parameter:
```
GET https://docs.adpage.io/accountmanagement/container-management/setting-up-a-new-container.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.