> 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.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FPIPEAy6v9qGYqvQINqgh%2Fcontainer-nieuw-stap1-volledig-en.webp?alt=media" alt="Step 1 of 3 of the New container wizard with website domain field"><figcaption><p>Add an extra container.</p></figcaption></figure>

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FzAxTyb5kAQIv5h2H8nk9%2Fnew-container-step2-plan-en.webp?alt=media" alt="Step 2 of 3 of the New container wizard with the plan choice"><figcaption><p>Choose a plan for the new container. Free needs no credit card.</p></figcaption></figure>
{% 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.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FqDMvtCV0koJkpt0XAOYG%2Fcontainer-instellingen-servercontainer-detail-en.webp?alt=media" alt="Server container (sGTM) section in the container settings"><figcaption><p>Paste the provisioning code of your Google Tag Manager server container.</p></figcaption></figure>

<details>

<summary>Retrieve the base64 configuration code manually</summary>

In Google Tag Manager, open the server container. Go to **Admin** → **Container settings**.

Click **Set up your tagging server**. Copy the displayed configuration code.

<figure><img src="broken://spaces/vuyv7mcuSvQb9yTkzfeA/files/mVGrEDTl84MBAbQBS5W9" alt="Google Tag Manager server container configuration code."><figcaption></figcaption></figure>

</details>
{% 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 %}

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FZIdBd7RnEs1JuKYXh8fS%2Fcontainer-instellingen-domeinen-detail-en.webp?alt=media" alt="Domains and SSL section with DNS and SSL status"><figcaption><p>Domains and SSL: your subdomain with its DNS and SSL status.</p></figcaption></figure>
{% 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 `<head>` and `<body>` snippets.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2F0HC556aonftq6IVVjARD%2Fcontainer-instellingen-taggingpixel-detail-en.webp?alt=media" alt="Tagging pixel section with platform choice and installation code"><figcaption><p>Choose your platform and copy the Tagging Pixel installation code.</p></figcaption></figure>

{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.adpage.io/accountmanagement/container-management/setting-up-a-new-container.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.
