> 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/getting-started/setup-adpage-container.md).

# Setup AdPage container

Go from sign-up to your first deploy in under five minutes.

This quickstart is about getting you to your first deploy fast. We're going to skip most of the setup for now, since you can always go back and tweak things once you've got something up and running.

{% hint style="success" %}
**Estimated time: 5 minutes.** All you need is access to a Google Tag Manager account, your site's DNS settings and the website's backend.
{% endhint %}

## Create your AdPage Container

{% stepper %}
{% step %}

### Register and create your account

Go to [AdPage](https://data.adpage.io/) and register or log in. Follow the steps to set up your account and fill in the info it asks for. You'll need to pick whether you're a client or an agency. The difference comes down to who you're setting up containers for. Go with **client** if it's for your own website or websites, and **agency** if you're setting them up for your clients.
{% endstep %}

{% step %}

### Create a container

Start by adding your first client, or just add a container right away. If you add a client's company first, you can then add a container under that company.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FTcfe8qnogXVh6sVWy9O7%2Fimage.png?alt=media&amp;token=0b1a66c0-0f16-47d5-8d33-af425ed9eddd" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Server container configuration

To get your AdPage server container going, you'll need to hook it up to a Google Tag Manager server container. After that, connect it to the root domain using CNAME cloaking. The last step is swapping out the standard Google Tag Manager script on the website for a Tagging Pixel.

{% stepper %}
{% step %}

### Connect your AdPage container with your Google Tag Manager server container

You can connect your AdPage server container to a Google Tag Manager server container with Google's base64 configuration code. That way you can set up your tracking rules on the Google Tag Manager server container.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2Fz6u01YatGCJSVz0D1eFs%2Fimage.png?alt=media&amp;token=a82092e3-4314-4354-aae2-3ee7c11ab3f6" alt=""><figcaption></figcaption></figure>

<details>

<summary>Manually retreive the base64 configuration code</summary>

If you'd rather set up the Google Tag Manager server container connection by hand, you'll need to grab the base64 code yourself.\
\
Go to [Google Tag Manager](https://tagmanager.google.com/) and open your server container, or make a new one if you don't have one yet.\
\
You'll find the configuration code in the **Container settings** inside the server container admin. It shows up once you click the **"Set up your tagging server"** button.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FuTr0ldchhskPWoXDEPi7%2Fimage.png?alt=media&amp;token=47de3d9c-2fae-49df-8dde-666c2a022fb6" alt=""><figcaption></figcaption></figure>

</details>
{% endstep %}

{% step %}

### Configure DNS records&#xD;

To use AdPage server-side tagging, you'll need to set up a custom domain. This is also called a custom tagging server URL, and it's what lets you set first-party cookies and use the AdPage Tagging Pixel. Make sure the URL uses the same root domain as your website.

Log in to wherever you manage your domain and create a new DNS record for the subdomain you want to use. It's a CNAME record, and you'll find the Host and Target values in the registration instructions.

{% hint style="info" %}
You can edit the Host of this CNAME record in your AdPage container settings. The Target is always `projects.trytagging.com`
{% endhint %}

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FFiKmY9B3E5e38uUn8wYs%2Fimage.png?alt=media&amp;token=9d938496-79f8-4060-96f8-2c96f1b32fca" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Tagging Pixel

Step 3 of the container registration is to replace the Google Tag Manager script on the website with an AdPage Tagging Pixel. This Tagging Pixel has the same functionality as a Google Tag Manager script, it sets up the connection between the website and your Google Tag Manager web container.

{% hint style="info" %}
The Tagging Pixel replaces the regular Google Tag Manager script in the site code. When adding the Tagging Pixel, make sure to delete the regular Google Tag Manager script.
{% endhint %}

Add your **Website URL**, add the **Google Tag Manager Web Container ID**. These two inputs are needed to generate the Tagging Pixel script and set up the Tagging Pixel verification.&#x20;

Once you've added those two, you can generate the Tagging Pixel instructions. You'll get different instructions depending on which Content Management System (CMS) you use. AdPage has an App for Shopify, a Plugin for Wordpress and WooCommerce, a Module for Magento, and its own set of instructions for Lightspeed, which also add an e-commerce dataLayer to the front end of the website. If all you need is the Tagging Pixel script, pick the custom CMS option to get the code for the `<head>` and `<body>`.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FisldcDbyxUjuP69lSKNR%2Fimage.png?alt=media&amp;token=7a889f16-5cd8-4172-a020-b5f7e5c2582f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you don't have access to the website's backend, you can also copy and share these instuctions by using the **Copy the installation link** at the top of these instructions.
{% endhint %}

{% endstep %}

{% step %}

### Finalizing the configuration

Once you've finished those three steps, you can go into the server container's dashboard. Your AdPage server container is ready to use. From here you can move on to setting up the tracking rules in your Google Tag Manager web and server containers.

{% hint style="info" %}
You can skip Step 2 and Step 3 during registration if you want. Both are things you can set up later from your server container's dashboard.
{% endhint %}
{% endstep %}
{% endstepper %}

## What's next?

Once you've added your first client or container, you can move on to setting up the tracking rules in your Google Tag Manager web and server containers. The next step goes over what you need to set up in your Google Tag Manager server container.

If you are setting up server-side tagging for a Shopify, WooCommerce, Magento or Lightspeed webshop. You can skip ahead to these steps: [Using AdPage Templates](/getting-started/using-adpage-templates.md).


---

# 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/getting-started/setup-adpage-container.md?ask=<question>&goal=<endgoal>
```

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